Ipregistry MCP integration for AI agents.
Connect AI agents to Ipregistry through 5 structured actions, including batch lookup asns, parse user agents, and batch lookup ips. Review authentication, in…
- 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 Ipregistry integration exposes
The Ipregistry Agent App exposes 5 provider-backed actions for location, security, and data work. Its current contract lets an authorized agent look up data for multiple autonomous system numbers with ipregistry, parse one or more user-agent strings with ipregistry, and look up ipregistry data for multiple ipv4 or ipv6 addresses in one request. 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 Ipregistry account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Ipregistry capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
batch_lookup_asnsREADLook up data for multiple Autonomous System Numbers with Ipregistry.
INPUTS: asns / fields
parse_user_agentsREVIEWParse one or more user-agent strings with Ipregistry.
INPUTS: userAgents / fields
batch_lookup_ipsREADLook up Ipregistry data for multiple IPv4 or IPv6 addresses in one request.
INPUTS: ipAddresses / includeHostname / fields
lookup_asnREADLook up data for one Autonomous System Number with Ipregistry.
INPUTS: asn / fields
lookup_ipREADLook up geolocation, connection, company, currency, time zone, and security data for one IP address.
INPUTS: ipAddress / includeHostname / fields
INPUT CONTRACTS
Know what the action needs before it runs.
batch_lookup_asns
asnsREQUIRED- The Autonomous System Numbers to look up.
fieldsOPTIONAL- Optional Ipregistry field selection expression used to limit the returned payload.
parse_user_agents
userAgentsREQUIRED- The user-agent strings to parse.
fieldsOPTIONAL- Optional Ipregistry field selection expression used to limit the returned payload.
batch_lookup_ips
ipAddressesREQUIRED- The IPv4 or IPv6 addresses to look up.
includeHostnameOPTIONAL- Whether Ipregistry should resolve and include hostname data.
fieldsOPTIONAL- Optional Ipregistry field selection expression used to limit the returned payload.
lookup_asn
asnREQUIRED- The Autonomous System Number to look up, such as AS15169 or 15169.
fieldsOPTIONAL- Optional Ipregistry field selection expression used to limit the returned payload.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Batch Lookup Asns
Look up data for multiple Autonomous System Numbers with Ipregistry. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
batch_lookup_asnsVerify with Batch Lookup Ips
Look up Ipregistry data for multiple IPv4 or IPv6 addresses in one request. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
batch_lookup_ipsSAFETY BOUNDARY
Operate Ipregistry with explicit limits
- Authorize Ipregistry with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Ipregistry 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 Ipregistry rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Ipregistry task completed successfully.
CONNECTION MODEL
API key
Ipregistry API key used in the Authorization: ApiKey header. View and manage keys at https://dashboard.ipregistry.co/signin?redirect=/keys.
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
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 Ipregistry.