Ip2Proxy for AI agents
IP2Proxy detects anonymous proxies, VPNs, and TOR exit nodes by IP address, helping flag suspicious traffic. Security teams fold it into their existing checks rather than relying on it alone. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Ip2Proxy.
Check if an IP is a proxy
Check whether a sign-up's IP address is a known proxy or VPN before approving the account.
Screen traffic for fraud signals
Screen a batch of recent visitor IPs for proxy usage as part of a fraud review.
Flag a suspicious session
Flag a session for manual review, read-only, rather than automatically blocking the user.
1 Ip2Proxy actions, graded by risk.
Every Ip2Proxy action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- ip2proxy.check_proxyCheck Proxy Status of an IP
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Ip2Proxy in three steps.
- 01Your users connect Ip2ProxyThey add their Ip2Proxy api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Ip2Proxy through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ip2proxy', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Ip2Proxy connects.
Users add their Ip2Proxy api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Ip2Proxy connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Ip2Proxy from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore security and identity apps.
Ip2Proxy and Arc0, answered.
Can I use Ip2Proxy with Claude, ChatGPT or Cursor?
Yes. Connect Ip2Proxy to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Ip2Proxy actions you allow.
How do users connect Ip2Proxy?
Users add their Ip2Proxy api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Ip2Proxy actions can my agent take?
1 in total: 1 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Ip2Proxy?
Yes. Allow read actions and deny writes in the Ip2Proxy policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Ip2Proxy too?
Yes. The same Ip2Proxy connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Ip2Proxy into your agent.
Your users connect Ip2Proxy once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan