IP lookup API and MCP for agents
One key, one quota: call the nested lookup response over REST or expose lookup_ip, check_privacy, and check_fraud through @traceexit/mcp.
REST contract
GET /v1/ip/{address} returns location, network, privacy, risk, fraud, and meta. Use Authorization: Bearer te_live_… or te_test_…. Documentation IPs and test keys return sample responses.
MCP tools
Agents in Cursor or Claude Desktop can run the same lookups without custom HTTP glue. Usage meters with REST under the same org.
What not to expect in public fields
Vendor source lists are not exposed in the public response. Confidence and partial flags tell you when coverage is limited or stale.
API keys stay private
Create keys in the console. Keys never appear on marketing pages. Customers use published plans and quotas.
FAQ
Do MCP calls cost extra?
No separate MCP meter — REST and MCP share monthly quota with cache-hit weights.
Is there a batch tool?
REST supports POST /v1/ip/batch (up to 100). MCP exposes lookup_ip_batch with the same cap.
Where is OpenAPI?
Swagger UI is served by the API host. See Docs for cURL and Node examples.