ipbase ships a hosted Model Context Protocol (MCP) server. AI agents and assistants — Claude, Cursor, VS Code and any other MCP-capable client — can call the API as native tools, no SDK or glue code required.
https://api.ipbase.com/mcp
Using Claude Code:
claude mcp add --transport http ipbase https://api.ipbase.com/mcp --header "apikey: YOUR_API_KEY"
Or add it to any MCP client configuration:
{
"mcpServers": {
"ipbase": {
"url": "https://api.ipbase.com/mcp",
"headers": { "apikey": "YOUR_API_KEY" }
}
}
}
Without a key, the server answers up to 10 requests per IP address and hour: the MCP handshake, listing the tools, and the getInfo and getStatus tools, so you can try a lookup right away. The other tools need a key: sign up for a free API key and send it as the apikey header.
MCP clients that support sign-in (OAuth), such as Claude’s custom connectors, can sign in instead of sending a key. In Claude, open Settings → Connectors → Add custom connector and enter https://api.ipbase.com/mcp. The lookups that work without a key run right away; the first time your agent calls a tool that needs a key, the client opens a sign-in page on app.ipbase.com: sign in or sign up, and approve the connection (as the team’s owner or an admin). The client then holds a key of your team that lasts an hour and renews itself; its tool calls count against your plan like any other request. You can disconnect it at any time under API keys → Connected apps in the dashboard. For your own code, use an API key.
| Tool | Endpoint | Description |
|---|---|---|
getInfo | GET /v2/info | Look up an IP address |
batchInfo | POST /v2/batch | Look up many IP addresses at once |
getAsn | GET /v2/asns | Look up an ASN |
getDomains | GET /v2/domains | Domains hosted on an IP |
getStatus | GET /v2/status | Account quota status |
Tool calls are metered like regular API requests and return the same machine-readable errors, so your agent always knows how to proceed. Full details in the MCP documentation.