ipstack MCP integration for AI agents.
Connect AI agents to ipstack through 3 structured actions, including bulk lookup, lookup current ip, and lookup ip. Review authentication, inputs, workflows…
- 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 ipstack integration exposes
The ipstack Agent App exposes 3 provider-backed actions for location and data work. Its current contract lets an authorized agent look up multiple ipv4 or ipv6 addresses in one ipstack request, look up the requester ip address and return ipstack geolocation data, and look up a single ipv4 or ipv6 address and return ipstack geolocation data. 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 ipstack account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ipstack capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
bulk_lookupREADLook up multiple IPv4 or IPv6 addresses in one ipstack request.
INPUTS: ips / fields
lookup_current_ipREADLook up the requester IP address and return ipstack geolocation data.
INPUTS: fields
lookup_ipREADLook up a single IPv4 or IPv6 address and return ipstack geolocation data.
INPUTS: ip / fields
INPUT CONTRACTS
Know what the action needs before it runs.
bulk_lookup
ipsREQUIRED- The IPv4 or IPv6 addresses to look up.
fieldsOPTIONAL- Optional ipstack response fields to include, such as country_code or location.country_flag.
lookup_current_ip
fieldsOPTIONAL- Optional ipstack response fields to include, such as country_code or location.country_flag.
lookup_ip
ipREQUIRED- The IPv4 or IPv6 address to look up.
fieldsOPTIONAL- Optional ipstack response fields to include, such as country_code or location.country_flag.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Bulk Lookup
Look up multiple IPv4 or IPv6 addresses in one ipstack 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 Lookup Current Ip
Look up the requester IP address and return ipstack geolocation data. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
lookup_current_ipSAFETY BOUNDARY
Operate ipstack with explicit limits
- Authorize ipstack with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned ipstack 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 ipstack rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ipstack task completed successfully.
CONNECTION MODEL
API key
ipstack API key sent as the access_key query parameter. Find it in your APILayer account API keys page: https://apilayer.com/docs/article/managing-api-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
- 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 ipstack.