Ip2Whois for AI agents
IP2WHOIS returns domain registration details like creation date, registrant, and nameservers from a WHOIS lookup. 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 Ip2Whois.
Check a domain's registration details
Look up a domain's creation date and registrant before a security or vendor review.
Check domain age
Check how old a domain is as a signal when assessing a new inbound partner.
List hosted domains for an IP
List domains hosted on the same IP to investigate a shared-hosting phishing pattern.
2 Ip2Whois actions, graded by risk.
Every Ip2Whois action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
2Create and change things. Allow, or ask the user first.
- ip2whois.domain_lookupIP2WHOIS Domain Lookup
- ip2whois.hosted_domains_lookupHosted Domains Lookup
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Ip2Whois in three steps.
- 01Your users connect Ip2WhoisThey add their Ip2Whois api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “iP2WHOIS Domain Lookup” can wait for the user to approve.
- 03Any agent can actYour agent calls Ip2Whois through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ip2whois', { read: 'allow', write: 'ask', // domain_lookup destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Ip2Whois connects.
Users add their Ip2Whois 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 Ip2Whois 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 Ip2Whois from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore security and identity apps.
Ip2Whois and Arc0, answered.
Can I use Ip2Whois with Claude, ChatGPT or Cursor?
Yes. Connect Ip2Whois 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 Ip2Whois actions you allow.
How do users connect Ip2Whois?
Users add their Ip2Whois 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 Ip2Whois actions can my agent take?
2 in total: 0 read, 2 write and 0 destructive, such as “iP2WHOIS Domain Lookup”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Ip2Whois?
Yes. Allow read actions and deny writes in the Ip2Whois policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Ip2Whois too?
Yes. The same Ip2Whois connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Ip2Whois into your agent.
Your users connect Ip2Whois once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan