IPIPAI MCP Server
warningsipipai.com
IP intelligence, network diagnostics, and AI service availability tools for AI agents.
https://ipipai.com/mcp-9f3k7xNo authMCP 2025-06-18v2.0.0last checked 31 Oct 2026spoke MCP on 1 of 1 check (30 days)initialize in 460 msLast checked 31 Oct 2026
- ✓Answered the MCP handshake (MCP 2025-06-18)
- ✓Auth detected: No auth
- ✓Lists 12 tools
- !1 warning
- ✓Spoke MCP on 1 of 1 check (30 days)
Will my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
✓Claude CodeConnects
The endpoint answers an anonymous handshake, so no credential is needed.
claude mcp add --transport http ipipai-mcp-server https://ipipai.com/mcp-9f3k7xClaude Code docs · read on 2026-08-30
✓Claude (claude.ai & Desktop)Connects
The endpoint answers an anonymous handshake, so no credential is needed.
Settings → Connectors → Add custom connector, then paste https://ipipai.com/mcp-9f3k7x.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✓ChatGPTConnects
The endpoint answers an anonymous handshake, so no credential is needed.
Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://ipipai.com/mcp-9f3k7x.
ChatGPT docs · read on 2026-08-30
✓CursorConnects
The endpoint answers an anonymous handshake, so no credential is needed.
{
"mcpServers": {
"ipipai-mcp-server": {
"url": "https://ipipai.com/mcp-9f3k7x"
}
}
}Cursor docs · read on 2026-08-30
✓VS Code (Copilot)Connects
The endpoint answers an anonymous handshake, so no credential is needed.
{
"servers": {
"ipipai-mcp-server": {
"type": "http",
"url": "https://ipipai.com/mcp-9f3k7x"
}
}
}VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 31 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | No auth |
|---|---|
| Protected-resource metadata | ✕Not found Without it a client has to guess where the authorization server lives. |
| Anonymous access | Handshake succeeds; 12 tools listable |
| Credentials demanded in prose | ✕lookup_ip_location These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
What the probe found
1 of the 12 tools listed anonymously say in their own descriptions that they need an account or a key (lookup_ip_location), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.
Tools
Contract history
Watch this server
Save its public contract as a baseline and manage breaking-change email alerts.
Set up a watchRoute it through the gateway
Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.
Add to my gatewayOwn this server?
Sign in to claim this listing by proving control of its host.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/ipipai-mcp-server)