# My IP Help (remote · www.myiphelp.com)

IP geolocation, ASN and a 0-100 risk score (VPN, proxy, Tor, datacenter) for any IP address.

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.myiphelp.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-myiphelp-myiphelp/mcp-v1.md), [page](https://verifymcp.io/servers/com-myiphelp-myiphelp/mcp-v1)

## Channel facts

- Endpoint: `https://www.myiphelp.com/mcp/v1`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-myiphelp-myiphelp 'https://www.myiphelp.com/mcp/v1'
```

### Cursor

```json
{
  "mcpServers": {
    "com-myiphelp-myiphelp": {
      "url": "https://www.myiphelp.com/mcp/v1"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-myiphelp-myiphelp": {
      "type": "http",
      "url": "https://www.myiphelp.com/mcp/v1"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-myiphelp-myiphelp]
url = "https://www.myiphelp.com/mcp/v1"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-myiphelp-myiphelp": {
      "type": "remote",
      "url": "https://www.myiphelp.com/mcp/v1",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-myiphelp-myiphelp --url 'https://www.myiphelp.com/mcp/v1' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-myiphelp-myiphelp:
    url: "https://www.myiphelp.com/mcp/v1"
```

### Netclaw

```json
{
  "McpServers": {
    "com-myiphelp-myiphelp": {
      "Transport": "http",
      "Url": "https://www.myiphelp.com/mcp/v1"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-myiphelp-myiphelp -t streamable-http -u 'https://www.myiphelp.com/mcp/v1'
```

### Other

```json
{
  "mcpServers": {
    "com-myiphelp-myiphelp": {
      "type": "http",
      "url": "https://www.myiphelp.com/mcp/v1"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 84, +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.

### 2026-11-19 (score 83, +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.

### 2026-11-17 (score 82, +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.

### 2026-11-15 (score 81, +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.

### 2026-11-12 (score 80, +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.

### 2026-11-11 (score 79, 0)

- [security] 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
- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 79)

First indexed and scored.

## MCP tools (5)

### `lookup_ip` (~107 tokens)

Look up an IP address

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.

Input parameters:

- `ip` (string, required): A public IPv4 or IPv6 address, e.g. 8.8.8.8 or 2001:4860:4860::8888.

### `bulk_lookup` (~111 tokens)

Look up several IP addresses

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.

Input parameters:

- `ips` (array, required): The IPv4 or IPv6 addresses to look up (at most 1000).

### `check_ip_risk` (~104 tokens)

Check an IP address's risk

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.

Input parameters:

- `ip` (string, required): A public IPv4 or IPv6 address.

### `lookup_asn` (~186 tokens)

Look up a network (ASN) by IP or AS number

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.

Input parameters:

- `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").

### `get_my_usage` (~50 tokens)

Show my API usage

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-myiphelp-myiphelp/mcp-v1#diagnostics

## Score history

- 2026-11-21: 84
- 2026-11-20: 83
- 2026-11-19: 83
- 2026-11-18: 82
- 2026-11-17: 82
- 2026-11-16: 81
- 2026-11-15: 81
- 2026-11-14: 80
- 2026-11-13: 80
- 2026-11-12: 80
- 2026-11-11: 79
- 2026-11-10: 79

## Common questions

### 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.

## Links

- Remote endpoint: https://www.myiphelp.com/mcp/v1
- Website: https://www.myiphelp.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-myiphelp-myiphelp/mcp-v1.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-myiphelp-myiphelp/mcp-v1/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-myiphelp-myiphelp/mcp-v1.json
- HTML version of this page: https://verifymcp.io/servers/com-myiphelp-myiphelp/mcp-v1
