IP2Proxy MCP integration for AI agents.
Connect AI agents to IP2Proxy through 1 structured actions, including lookup ip. Review authentication, inputs, workflows, and safety guidance.
- ACTION CONTRACTS
- 1
- 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 IP2Proxy integration exposes
The IP2Proxy Agent App exposes 1 provider-backed actions for security, location, and data work. Its current contract lets an authorized agent detect whether one ipv4 or ipv6 address is a proxy and return the official ip2proxy lookup payload. 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 IP2Proxy account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real IP2Proxy capabilities.
Showing 1 of 1 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
lookup_ipREADDetect whether one IPv4 or IPv6 address is a proxy and return the official IP2Proxy lookup payload.
INPUTS: ip / package
INPUT CONTRACTS
Know what the action needs before it runs.
lookup_ip
ipOPTIONAL- The IPv4 or IPv6 address to look up.
packageOPTIONAL- The IP2Proxy package code to query. The official API defaults to PX1 when omitted.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Lookup Ip
Detect whether one IPv4 or IPv6 address is a proxy and return the official IP2Proxy lookup payload. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
lookup_ipVerify with Lookup Ip
Detect whether one IPv4 or IPv6 address is a proxy and return the official IP2Proxy lookup payload. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
lookup_ipSAFETY BOUNDARY
Operate IP2Proxy with explicit limits
- Authorize IP2Proxy with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned IP2Proxy 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 IP2Proxy rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the IP2Proxy task completed successfully.
CONNECTION MODEL
API key
IP2Proxy Web Service API key passed with the key query parameter. Existing customers can sign in through the IP2Location client area to view it: https://www.ip2location.com/client-area. The official product page documents the current signup status: https://www.ip2location.com/web-service/ip2proxy
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
- 1
- 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 IP2Proxy.