IPLocate MCP integration for AI agents.
Connect AI agents to IPLocate through 3 structured actions, including batch lookup, lookup ip, and lookup self. Review authentication, inputs, workflows, and…
- 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 IPLocate integration exposes
The IPLocate Agent App exposes 3 provider-backed actions for location, security, and data work. Its current contract lets an authorized agent look up iplocate data for multiple ip addresses in one json request and preserve per-ip inline errors, look up iplocate geolocation, asn, privacy, hosting, company, and abuse data for one ip address, and look up iplocate geolocation and threat intelligence data for the connector server's outgoing 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 IPLocate account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real IPLocate capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
batch_lookupREADLook up IPLocate data for multiple IP addresses in one JSON request and preserve per-IP inline errors.
INPUTS: ipAddresses
lookup_ipREADLook up IPLocate geolocation, ASN, privacy, hosting, company, and abuse data for one IP address.
INPUTS: ip / include
lookup_selfREADLook up IPLocate geolocation and threat intelligence data for the connector server's outgoing IP address.
INPUTS: include
INPUT CONTRACTS
Know what the action needs before it runs.
batch_lookup
ipAddressesREQUIRED- The IPv4 or IPv6 addresses to look up. IPLocate allows up to 1,000 IPs per batch request.
lookup_ip
ipREQUIRED- The IPv4 or IPv6 address to look up.
includeOPTIONAL- The IPLocate response fields to include, such as country_code, asn, or privacy.is_vpn.
lookup_self
includeOPTIONAL- The IPLocate response fields to include, such as country_code, asn, or privacy.is_vpn.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Batch Lookup
Look up IPLocate data for multiple IP addresses in one JSON request and preserve per-IP inline errors. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
batch_lookupVerify with Lookup Ip
Look up IPLocate geolocation, ASN, privacy, hosting, company, and abuse data for one IP address. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
lookup_ipSAFETY BOUNDARY
Operate IPLocate with explicit limits
- Authorize IPLocate with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned IPLocate 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 IPLocate rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the IPLocate task completed successfully.
CONNECTION MODEL
API key
IPLocate API key sent with the X-API-Key request header. Create a free account and get your key at https://www.iplocate.io/signup.
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 IPLocate.