IP99 IP risk & geolocation
REMOTE · IP99.COM · SCANNED SEP 26
Free IP risk and geolocation lookup: proxy, VPN and datacenter detection. No API key.
Available components
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 272 tokens (~272/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the IP99 IP risk & geolocation MCP server?
IP99 IP risk & geolocation is a hosted endpoint at https://ip99.com/mcp, 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 · ip99.com
claude mcp add --transport http com-ip99-ip99 'https://ip99.com/mcp'
{
"mcpServers": {
"com-ip99-ip99": {
"url": "https://ip99.com/mcp"
}
}
} {
"servers": {
"com-ip99-ip99": {
"type": "http",
"url": "https://ip99.com/mcp"
}
}
} [mcp_servers.com-ip99-ip99] url = "https://ip99.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ip99-ip99": {
"type": "remote",
"url": "https://ip99.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-ip99-ip99 --url 'https://ip99.com/mcp' --transport streamable-http
mcp_servers:
com-ip99-ip99:
url: "https://ip99.com/mcp" {
"McpServers": {
"com-ip99-ip99": {
"Transport": "http",
"Url": "https://ip99.com/mcp"
}
}
} assistant mcp add com-ip99-ip99 -t streamable-http -u 'https://ip99.com/mcp'
{
"mcpServers": {
"com-ip99-ip99": {
"type": "http",
"url": "https://ip99.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 13 Sept 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.
- 12 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ip_risk_lookup” rewrote its description, which is the text the model reads security
- Schema quality: 203 → 286 ▼ functional
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 26 Sept 2026 · Probed https://ip99.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ip99.com | CN=TrustAsia DV TLS RSA CA 2024,O=TrustAsia Technologies\, Inc.,C=CN | 9 Sept 2026 | 8 Dec 2026 | RSA 2048 | SHA256-RSA | 29b7f17b6b2d8e140f917b63841f2aff6771c327 |
| SANs: ip99.com, www.ip99.com | ||||||
| CN=TrustAsia DV TLS RSA CA 2024,O=TrustAsia Technologies\, Inc.,C=CN (CA) | CN=TrustAsia TLS RSA Root CA,O=TrustAsia Technologies\, Inc.,C=CN | 15 May 2024 | 15 May 2034 | RSA 4096 | SHA384-RSA | 1c9e6b412deb0a85461de03dbe30984d0573888b |
| CN=TrustAsia TLS RSA Root CA,O=TrustAsia Technologies\, Inc.,C=CN (CA) | CN=Certum Trusted Network CA,OU=Certum Certification Authority,O=Unizeto Technologies S.A.,C=PL | 7 Oct 2025 | 14 Jan 2029 | RSA 4096 | SHA384-RSA | b2dc4c34932d709cd4bf0b099401695c |
| CN=Certum Trusted Network CA,OU=Certum Certification Authority,O=Unizeto Technologies S.A.,C=PL (CA) | CN=Certum Trusted Network CA,OU=Certum Certification Authority,O=Unizeto Technologies S.A.,C=PL | 22 Oct 2008 | 31 Dec 2029 | RSA 2048 | SHA1-RSA | 444c0 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ip99.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ip99.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 |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; frame-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'; object-src 'none' |
| 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://ip99.com/mcp | Verified | 200 | |
| http (plaintext) | http://ip99.com/mcp | 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 →
ip_risk_lookup IP risk & geolocation lookup ~173
Look up the risk profile and geolocation of an IPv4 or IPv6 address. Returns a 0-100 risk score measuring the freshness and strength of verifiable risk evidence (proxy, VPN, dial-up pool, cloud phone, datacenter), the evidence state, network (ASN, usage type) and geographic attribution. The score is NOT a probability that the address is an attacker. Free tier: 1000 lookups per day per client IP and 60 per minute; higher limits with an API key sent as the X-API-Key header (https://ip99.com/en/pricing).
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | The IPv4 or IPv6 address to look up, e.g. 8.8.8.8 or 2001:4860:4860::8888. |
No output schema declared.
No examples provided.
What is the IP99 IP risk & geolocation MCP server?
IP99 IP risk & geolocation is an MCP server listed in the public MCP registry as com.ip99/ip99. Free IP risk and geolocation lookup: proxy, VPN and datacenter detection. No API key. This page covers its hosted endpoint (https://ip99.com/mcp).
Is the IP99 IP risk & geolocation MCP server safe to use?
IP99 IP risk & geolocation scores 74 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 IP99 IP risk & geolocation MCP server expose?
IP99 IP risk & geolocation exposes 1 tool: ip_risk_lookup. Their descriptions and schemas cost roughly 173 tokens of context every time the server is loaded.
Does the IP99 IP risk & geolocation MCP server require authentication?
No. We connected to IP99 IP risk & geolocation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the IP99 IP risk & geolocation MCP server still maintained?
IP99 IP risk & geolocation is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.