Neutrino API MCP integration for AI agents.
Connect AI agents to Neutrino API through 5 structured actions, including check ip blocklist, validate email, and get ip info. Review authentication, inputs…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Neutrino API integration exposes
The Neutrino API Agent App exposes 5 provider-backed actions for data, location, and security work. Its current contract lets an authorized agent check whether an ip address is listed on neutrino security blocklists, parse, validate, and clean an email address with neutrino, and get neutrino geolocation and reverse-dns details for an ip address. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Neutrino API account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Neutrino API capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
check_ip_blocklistREADCheck whether an IP address is listed on Neutrino security blocklists.
INPUTS: ip / vpn-lookup
validate_emailREVIEWParse, validate, and clean an email address with Neutrino.
INPUTS: email / fix-typos
get_ip_infoREADGet Neutrino geolocation and reverse-DNS details for an IP address.
INPUTS: ip / reverse-lookup
lookup_domainREADGet Neutrino domain registration, DNS, mail, website, and blocklist details.
INPUTS: host / live
validate_phoneREVIEWParse, validate, format, and locate a phone number with Neutrino.
INPUTS: number / country-code / ip
INPUT CONTRACTS
Know what the action needs before it runs.
check_ip_blocklist
ipREQUIRED- An IPv4 or IPv6 address. CIDR notation, port numbers, and comma-separated IPs are also accepted by Neutrino.
vpn-lookupOPTIONAL- Whether to include public VPN provider IP addresses.
validate_email
emailREQUIRED- The email address to parse, validate, and clean.
fix-typosOPTIONAL- Whether to automatically attempt to fix typos in the address.
get_ip_info
ipREQUIRED- An IPv4 or IPv6 address. CIDR notation is also accepted by Neutrino.
reverse-lookupOPTIONAL- Whether to run a reverse DNS PTR lookup.
lookup_domain
hostREQUIRED- A domain name, hostname, FQDN, URL, HTML link, or email address.
liveOPTIONAL- Whether to perform live checks for domains Neutrino has not seen before.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Check Ip Blocklist
Check whether an IP address is listed on Neutrino security blocklists. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
check_ip_blocklistVerify with Get Ip Info
Get Neutrino geolocation and reverse-DNS details for an IP address. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_ip_infoSAFETY BOUNDARY
Operate Neutrino API with explicit limits
- Authorize Neutrino API with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Neutrino API data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Neutrino API rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Neutrino API task completed successfully.
CONNECTION MODEL
API key
Neutrino API key sent with the API-Key header. View your API key in the Neutrino API dashboard: https://www.neutrinoapi.com/account/dashboard/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Neutrino API.