ipdata.co MCP integration for AI agents.
Connect AI agents to ipdata.co through 30 structured actions, including bulk lookup, get calling code, and get carrier by ip. Review authentication, inputs…
- ACTION CONTRACTS
- 30
- 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 ipdata.co integration exposes
The ipdata.co Agent App exposes 30 provider-backed actions for location, security, and data work. Its current contract lets an authorized agent look up up to 100 ip addresses in a single ipdata bulk api request, look up the calling_code field for a specific ip address or the caller's current ip address, and look up carrier data for a specific ip address or the caller's current 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 ipdata.co account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ipdata.co capabilities.
Showing 12 of 30 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
bulk_lookupREADLook up up to 100 IP addresses in a single ipdata bulk API request.
INPUTS: ips
get_calling_codeREADLook up the calling_code field for a specific IP address or the caller's current IP address.
INPUTS: ip
get_carrier_by_ipREADLook up carrier data for a specific IP address or the caller's current IP address.
INPUTS: ip
get_cityREADLook up the city field for a specific IP address or the caller's current IP address.
INPUTS: ip
get_company_by_ipREADLook up company data for a specific IP address or the caller's current IP address.
INPUTS: ip
get_continent_codeREADLook up the continent_code field for a specific IP address or the caller's current IP address.
INPUTS: ip
get_continent_nameREADLook up the continent_name field for a specific IP address or the caller's current IP address.
INPUTS: ip
get_countREADLook up the count field for a specific IP address or the caller's current IP address.
INPUTS: ip
get_country_codeREADLook up the country_code field for a specific IP address or the caller's current IP address.
INPUTS: ip
get_country_nameREADLook up the country_name field for a specific IP address or the caller's current IP address.
INPUTS: ip
get_currency_by_ipREADLook up currency data for a specific IP address or the caller's current IP address.
INPUTS: ip
get_emoji_flagREADLook up the emoji_flag field for a specific IP address or the caller's current IP address.
INPUTS: ip
INPUT CONTRACTS
Know what the action needs before it runs.
bulk_lookup
ipsOPTIONAL- The list of IP addresses to submit to the ipdata bulk lookup endpoint.
get_calling_code
ipOPTIONAL- The IPv4 or IPv6 address to look up. Omit this field to use the caller's current IP.
get_carrier_by_ip
ipOPTIONAL- The IPv4 or IPv6 address to look up. Omit this field to use the caller's current IP.
get_city
ipOPTIONAL- The IPv4 or IPv6 address to look up. Omit this field to use the caller's current IP.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Bulk Lookup
Look up up to 100 IP addresses in a single ipdata bulk API request. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
bulk_lookupVerify with Get Calling Code
Look up the calling_code field for a specific IP address or the caller's current IP address. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_calling_codeSAFETY BOUNDARY
Operate ipdata.co with explicit limits
- Authorize ipdata.co with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned ipdata.co 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 ipdata.co rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ipdata.co task completed successfully.
CONNECTION MODEL
API key
ipdata API key passed as the api-key query parameter. Sign up for a free key or view authentication examples in the docs: https://docs.ipdata.co/reference/authentication.
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
- 30
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 ipdata.co.