IPIPAI MCP Server
REMOTE · IPIPAI.COM
IP intelligence, network diagnostics, and AI service availability tools for AI agents.
Available components
Last scanned (8 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 825 tokens (~68/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ping_host" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 57
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://ipipai.com/mcp-9f3k7x
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ipipai.com | CN=YE1,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 53d573c4a91260b1830d87102399d1ee57b |
| SANs: *.ipipai.com, ipipai.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ipipai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ipipai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ipipai.com/mcp-9f3k7x | Verified | 200 | |
| http (plaintext) | http://ipipai.com/mcp-9f3k7x | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_ip_reputation IP Reputation Check ~63
Check IP reputation: proxy/VPN detection, Tor exit node, blacklist status, hosting/datacenter classification. Returns a verdict (Safe / Low / Medium / High / Critical Risk) with pass/fail checks.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IP address to check |
No output schema declared.
No examples provided.
check_service_access Service Accessibility Check ~69
Check if a specific service (ChatGPT, Claude, Netflix, Disney+, etc.) is accessible from a given IP location. Useful for diagnosing "why can't I access X?" questions.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IP address to check from |
| service | string | yes | Service ID to check |
No output schema declared.
No examples provided.
check_website_availability Website Availability Check ~43
Check if major websites (Google, GitHub, YouTube, Wikipedia, etc.) are accessible from the server location. Useful for censorship and network restriction detection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_domain_whois WHOIS Lookup ~59
Query WHOIS registration info for a domain name or IP address. Returns registrar, creation date, expiry date, nameservers, and registrant info (if public).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Domain name or IP address to look up |
No output schema declared.
No examples provided.
lookup_ip IP Intelligence Lookup ~138
Query complete IP intelligence: geolocation, ISP, ASN, IP type (residential/datacenter/mobile/VPN/proxy/Tor), risk score, and IPIPAI composite score (0-100 with grade A+ to D). This is the primary tool for IP analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| check_services | boolean | – | If true, also check AI service accessibility (ChatGPT, Claude, Gemini, Copilot) |
| ip | string | yes | IPv4 or IPv6 address (e.g. "8.8.8.8" or "2606:4700:4700::1111") |
| lang | string | – | Response language |
No output schema declared.
No examples provided.
lookup_ip_location IP Geolocation (OpenIPAPI) ~50
Quick IP geolocation lookup via OpenIPAPI. Returns country and city for an IP address. Lightweight and fast — no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IP address to geolocate |
No output schema declared.
No examples provided.
lookup_mac_vendor MAC Address Vendor Lookup ~69
Identify the manufacturer of a network device by its MAC address using the OUI database.
| Name | Type | Req | Description |
|---|---|---|---|
| mac | string | yes | MAC address (e.g. "00:1A:2B:3C:4D:5E" or "001A2B3C4D5E") |
No output schema declared.
No examples provided.
ping_host Ping Test ~57
Send ICMP ping packets to a host and measure latency. Returns min/avg/max latency and packet loss percentage.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of ping packets to send |
| target | string | yes | IP address or hostname to ping |
No output schema declared.
No examples provided.
rate_ip_node IP Node Rating ~70
Comprehensive rating for VPS, proxy nodes, and datacenter IPs. Returns overall score (0-100), grade (A+ to D), 5-star ratings for AI/streaming/stability/security/network, recommended use cases, and warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IP address to rate |
No output schema declared.
No examples provided.
resolve_dns DNS Resolution ~47
Resolve a domain name to its A (IPv4) and AAAA (IPv6) DNS records.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to resolve (e.g. "example.com") |
No output schema declared.
No examples provided.
score_ip_node IP Node Quality Score ~100
Score the quality and reliability of an IP/node using IP intelligence and network signals. Returns overall score (0-100), grade (A+ to D), 5-star ratings for AI/streaming/stability/security/network, recommended use cases, and warnings. Use this tool when the user asks whether an IP/node is high quality, clean, stable, or suitable for a specific network use case.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IP address to score |
No output schema declared.
No examples provided.
trace_route Traceroute ~60
Trace the network path from the server to a target host. Returns hop-by-hop IP, hostname, and latency for each hop.
| Name | Type | Req | Description |
|---|---|---|---|
| max_hops | number | – | Maximum number of hops |
| target | string | yes | IP address or hostname to trace |
No output schema declared.
No examples provided.
How do I install the IPIPAI MCP Server server?
IPIPAI MCP Server is a hosted endpoint at https://ipipai.com/mcp-9f3k7x, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ipipai.com
claude mcp add --transport http com-ipipai-ipipai-mcp 'https://ipipai.com/mcp-9f3k7x'
What is the IPIPAI MCP Server server?
IPIPAI MCP Server is listed in the public MCP registry as com.ipipai/ipipai-mcp. IP intelligence, network diagnostics, and AI service availability tools for AI agents. This page covers its hosted endpoint (https://ipipai.com/mcp-9f3k7x).
Is the IPIPAI MCP Server server safe to use?
IPIPAI MCP Server scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the IPIPAI MCP Server server expose?
IPIPAI MCP Server exposes 12 tools: lookup_ip, check_ip_reputation, check_service_access, rate_ip_node, score_ip_node, and 7 more. Their descriptions and schemas cost roughly 825 tokens of context every time the server is loaded.
Does the IPIPAI MCP Server server require authentication?
No. We connected to IPIPAI MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the IPIPAI MCP Server server still maintained?
IPIPAI MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.