IPRegistry for AI agents
IPRegistry provides IP geolocation, network, carrier, and threat intelligence for identifying and assessing IP addresses. Analysts and operators pull this data into reports and dashboards instead of collecting it by hand. 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 IPRegistry.
Look up an IP's network info
Look up the network and carrier details behind an IP address for a fraud check.
Batch look up a list of IPs
Batch geolocate a list of IPs from server logs to summarize where traffic is coming from.
Parse a user agent string
Parse a visitor's user agent string to identify their browser and device type.
5 IPRegistry actions, graded by risk.
Every IPRegistry action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- ipregistry.lookup_ipLook Up IP Address
- ipregistry.lookup_asnLook Up ASN
- ipregistry.parse_user_agentsParse User Agents
write
2Create and change things. Allow, or ask the user first.
- ipregistry.batch_lookup_ipsBatch Look Up IP Addresses
- ipregistry.batch_lookup_asnsBatch Look Up ASNs
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
IPRegistry in three steps.
- 01Your users connect IPRegistryThey add their IPRegistry api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “batch Look Up IP Addresses” can wait for the user to approve.
- 03Any agent can actYour agent calls IPRegistry through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ipregistry', { read: 'allow', write: 'ask', // batch_lookup_ips destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How IPRegistry connects.
Users add their IPRegistry 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 IPRegistry 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 IPRegistry from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
IPRegistry and Arc0, answered.
Can I use IPRegistry with Claude, ChatGPT or Cursor?
Yes. Connect IPRegistry 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 IPRegistry actions you allow.
How do users connect IPRegistry?
Users add their IPRegistry 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 IPRegistry actions can my agent take?
5 in total: 3 read, 2 write and 0 destructive, such as “batch Look Up IP Addresses”. Your policies decide which of them each agent may call.
Can I make my agent read-only in IPRegistry?
Yes. Allow read actions and deny writes in the IPRegistry policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call IPRegistry too?
Yes. The same IPRegistry connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug IPRegistry into your agent.
Your users connect IPRegistry once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan