My IP Help
REMOTE · WWW.MYIPHELP.COM
IP geolocation, ASN and a 0-100 risk score (VPN, proxy, Tor, datacenter) for any IP address.
Available components
Last scanned (15 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 747 tokens (~149/item across 5 items; 5 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 Management37
- Stability observed for 11 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 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 Nov 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 Nov 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 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.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 0
- Tool “bulk_lookup” rewrote its description, which is the text the model reads security
- Tool “lookup_ip” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 79
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 21 Nov 2026 · Probed https://www.myiphelp.com/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=myiphelp.com | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f822e34281c04c400ef62d203f0b87cc |
| SANs: myiphelp.com, *.myiphelp.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.myiphelp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| myiphelp.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://www.myiphelp.com/.well-known/oauth-protected-resource/mcp/v1"
Bearer realm="mcp", resource_metadata="https://www.myiphelp.com/.well-known/oauth-protected-resource/mcp/v1" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=() |
Protected resource metadata
| Document | https://www.myiphelp.com/.well-known/oauth-protected-resource/mcp/v1 |
|---|---|
| Retrieved | Yes |
| Resource | https://www.myiphelp.com/mcp/v1 |
| Authorisation server | https://www.myiphelp.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.myiphelp.com/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://www.myiphelp.com/mcp/v1 | HTTPS enforced | 301 | https://www.myiphelp.com/mcp/v1 |
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 →
bulk_lookup Look up several IP addresses ~111
Geolocation, network and risk data (the score with its main reason on every plan; the full breakdown and security flags from Pro) for SEVERAL IP addresses in one call. Sends them in batches of the plan's bulk size (Free: 20 per request). Each address that returns data counts one lookup against the monthly quota; private, reserved, unknown and duplicate addresses are not counted.
| Name | Type | Req | Description |
|---|---|---|---|
| ips | array | yes | The IPv4 or IPv6 addresses to look up (at most 1000). |
No output schema declared.
No examples provided.
check_ip_risk Check an IP address's risk ~104
Risk verdict for ONE public IP address: a 0-100 risk score, its band and label and the main reason behind it (risk_reason, every plan), and (Pro plan and up) the full breakdown: every signal with its points and source, plus VPN, proxy, Tor, datacenter, hijacked-network and verified-bot flags. Counts one lookup against the monthly quota.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | A public IPv4 or IPv6 address. |
No output schema declared.
No examples provided.
get_my_usage Show my API usage ~50
The API key's plan, the lookups used and left this lookup month (single lookups plus bulk IPs), when the month resets, and the rate limit. Does not count as a lookup.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_asn Look up a network (ASN) by IP or AS number ~186
The autonomous system (ASN) behind ONE public IP address, or ONE network by its AS number ("AS13335" or "13335"). For an IP: the ASN, its name, the ISP and organization, and (by plan) its registry, allocation date, cloud provider, datacenter flag. For an AS number: its name, how many IPv4 and IPv6 ranges it announces, its IPv4 address count and largest prefixes, and (by plan) the datacenter flag. Both link to the network's page on myiphelp.com and count one lookup against the monthly quota.
| Name | Type | Req | Description |
|---|---|---|---|
| asn | string | – | An AS number, e.g. AS13335 or 13335, instead of an IP. |
| ip | string | – | A public IPv4 or IPv6 address whose network you want (or an AS number, as in "asn"). |
No output schema declared.
No examples provided.
lookup_ip Look up an IP address ~107
Geolocation, network (ISP, ASN), risk score with its main reason (risk_reason) and, from Pro, the full breakdown of the score (risk_signals) and the security flags for ONE public IPv4 or IPv6 address. Counts one lookup against the key's monthly quota.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | A public IPv4 or IPv6 address, e.g. 8.8.8.8 or 2001:4860:4860::8888. |
No output schema declared.
No examples provided.
How do I install the My IP Help MCP server?
My IP Help is a hosted endpoint at https://www.myiphelp.com/mcp/v1, 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 · www.myiphelp.com
claude mcp add --transport http com-myiphelp-myiphelp 'https://www.myiphelp.com/mcp/v1'
What is the My IP Help MCP server?
My IP Help is an MCP server listed in the public MCP registry as com.myiphelp/myiphelp. IP geolocation, ASN and a 0-100 risk score (VPN, proxy, Tor, datacenter) for any IP address. This page covers its hosted endpoint (https://www.myiphelp.com/mcp/v1).
Is the My IP Help MCP server safe to use?
My IP Help scores 84 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 My IP Help MCP server expose?
My IP Help exposes 5 tools: lookup_ip, bulk_lookup, check_ip_risk, lookup_asn, get_my_usage. Their descriptions and schemas cost roughly 558 tokens of context every time the server is loaded.
Does the My IP Help MCP server require authentication?
Yes. My IP Help asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the My IP Help MCP server still maintained?
My IP Help is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the My IP Help MCP server?
VerifyMCP ran 13 checks on My IP Help, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.