Endpoint
- Transport: MCP Streamable HTTP
- MCP API URL:
https://ip-api.io/mcp - Authentication: pass
api_keyin each customer-facing tool call - Public health tool:
api_status
Configure your MCP client
Add the hosted Streamable HTTP MCP endpoint to any MCP client that supports remote HTTP servers. Keep your API key in a secret store and provide it only as a tool argument.
{
"mcpServers": {
"ip-api-io": {
"url": "https://ip-api.io/mcp",
"transport": "streamable-http"
}
}
} Call a tool with your API key
Tool calls use the same quota pools and response fields as the REST API. This example returns geolocation and security flags for an IP address.
{
"name": "ip_lookup",
"arguments": {
"api_key": "YOUR_API_KEY",
"ip": "8.8.8.8"
}
} For batch tools, send arrays. Batch IP and advanced-email tools accept up to 100 items and charge one quota unit per unique processed item.
Use self lookup carefully
Tools ending in _self use the MCP HTTP request peer IP. For hosted
or cloud MCP clients, that may be the client service egress IP rather than an
end user's browser or device IP. Use explicit IP tools when you need to analyze
an application user.
ip_lookup or
risk_score with the IP address collected by your own backend when
making fraud or compliance decisions.