IP2Location.io MCP integration for AI agents.
Connect AI agents to IP2Location.io through 3 structured actions, including get domain whois, get ip geolocation, and list hosted domains. Review authenticat…
- ACTION CONTRACTS
- 3
- 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 IP2Location.io integration exposes
The IP2Location.io Agent App exposes 3 provider-backed actions for location, security, and data work. Its current contract lets an authorized agent retrieve whois registration details for one domain, retrieve geolocation and network metadata for one ipv4 or ipv6 address, and list the hosted domains associated with one ipv4 or ipv6 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 IP2Location.io account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real IP2Location.io capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_domain_whoisREADRetrieve WHOIS registration details for one domain.
INPUTS: domain
get_ip_geolocationREADRetrieve geolocation and network metadata for one IPv4 or IPv6 address.
INPUTS: ip / lang
list_hosted_domainsREADList the hosted domains associated with one IPv4 or IPv6 address.
INPUTS: ip / page
INPUT CONTRACTS
Know what the action needs before it runs.
get_domain_whois
domainOPTIONAL- The domain name to query.
get_ip_geolocation
ipREQUIRED- The IPv4 or IPv6 address to query.
langOPTIONAL- The IP2Location-supported language code for translated place names, including regional variants such as zh-cn and zh-tw.
list_hosted_domains
ipREQUIRED- The IPv4 or IPv6 address to query.
pageOPTIONAL- The 1-based result page to fetch.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Domain Whois
Retrieve WHOIS registration details for one domain. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_domain_whoisVerify with Get Ip Geolocation
Retrieve geolocation and network metadata for one IPv4 or IPv6 address. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_ip_geolocationSAFETY BOUNDARY
Operate IP2Location.io with explicit limits
- Authorize IP2Location.io with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned IP2Location.io 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 IP2Location.io rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the IP2Location.io task completed successfully.
CONNECTION MODEL
API key
IP2Location.io API key passed with the key query parameter. Sign up for the Free Plan to get one: https://www.ip2location.io/ip2location-documentation
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
- 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 IP2Location.io.