# IP Location MCP (remote · mcp.pianam.cn)

MCP server for IPv4 geolocation with Chinese output: country/region/city, ISP and ASN.

- Trust score: 0/100 (low)
- Change this week: −62
- Registry status: active
- Liveness: dead
- Owner verified: no
- Last scored: 2026-09-24

> **Dead**: every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically.

## Components

- remote · `mcp.pianam.cn`: 0/100 (this document), [markdown](https://verifymcp.io/servers/cn-pianam-mcp-ip-location-mcp/ip-mcp-mcp.md), [page](https://verifymcp.io/servers/cn-pianam-mcp-ip-location-mcp/ip-mcp-mcp)

## Channel facts

- Endpoint: `https://mcp.pianam.cn/ip-mcp/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-24.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC not yet verified: we couldn't validate it against a resolver.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the IP Location MCP server?

IP Location MCP is a hosted endpoint at https://mcp.pianam.cn/ip-mcp/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.

### Claude

```bash
claude mcp add --transport http cn-pianam-mcp-ip-location-mcp 'https://mcp.pianam.cn/ip-mcp/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cn-pianam-mcp-ip-location-mcp": {
      "url": "https://mcp.pianam.cn/ip-mcp/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cn-pianam-mcp-ip-location-mcp": {
      "type": "http",
      "url": "https://mcp.pianam.cn/ip-mcp/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cn-pianam-mcp-ip-location-mcp]
url = "https://mcp.pianam.cn/ip-mcp/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cn-pianam-mcp-ip-location-mcp": {
      "type": "remote",
      "url": "https://mcp.pianam.cn/ip-mcp/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cn-pianam-mcp-ip-location-mcp --url 'https://mcp.pianam.cn/ip-mcp/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cn-pianam-mcp-ip-location-mcp:
    url: "https://mcp.pianam.cn/ip-mcp/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cn-pianam-mcp-ip-location-mcp": {
      "Transport": "http",
      "Url": "https://mcp.pianam.cn/ip-mcp/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cn-pianam-mcp-ip-location-mcp -t streamable-http -u 'https://mcp.pianam.cn/ip-mcp/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cn-pianam-mcp-ip-location-mcp": {
      "type": "http",
      "url": "https://mcp.pianam.cn/ip-mcp/mcp"
    }
  }
}
```

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-09-24 (score 0, −12)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-23 (score 12, −13)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-21 (score 25, −12)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-20 (score 37, −13)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-19 (score 50, −12)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-17 (score 62, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] DNSSEC: fail → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.43 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [security improvement] HTTPS: unverified → pass
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-15 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `query_ip_location` (~76 tokens)

查询 IPv4 地址的归属地和运营商信息。ip为空时尝试取调用方IP。返回归属地(国家/省份/城市)、经纬度、时区、运营商、AS编号。主源ip-api.com，备源ipwho.is。

Input parameters:

- `ip` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cn-pianam-mcp-ip-location-mcp/ip-mcp-mcp#diagnostics

## Score history

- 2026-09-24: 0
- 2026-09-23: 12
- 2026-09-22: 25
- 2026-09-21: 25
- 2026-09-20: 37
- 2026-09-19: 50
- 2026-09-18: 62
- 2026-09-17: 62
- 2026-09-16: 62
- 2026-09-15: 62
- 2026-09-14: 61
- 2026-09-13: 61
- 2026-09-12: 60
- 2026-09-11: 60
- 2026-09-10: 59
- 2026-09-09: 59
- 2026-09-08: 59
- 2026-09-07: 58
- 2026-09-06: 60
- 2026-09-05: 59
- 2026-09-04: 59
- 2026-09-03: 58

## Common questions

### What is the IP Location MCP server?

IP Location MCP is listed in the public MCP registry as cn.pianam.mcp/ip-location-mcp. MCP server for IPv4 geolocation with Chinese output: country/region/city, ISP and ASN. This page covers its hosted endpoint (https://mcp.pianam.cn/ip-mcp/mcp).

### Is the IP Location MCP server safe to use?

IP Location MCP scores 0 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 IP Location MCP server expose?

IP Location MCP exposes 1 tool: query_ip_location. Their descriptions and schemas cost roughly 76 tokens of context every time the server is loaded.

### Does the IP Location MCP server require authentication?

Its publisher declares no required credentials for IP Location MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the IP Location MCP server still maintained?

IP Location MCP has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 16 September 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 IP Location MCP server?

VerifyMCP ran 2 checks on IP Location MCP, covering HTTPS and Transport. 9 items could not be completed, a gap on our side rather than a finding about IP Location MCP: TLS certificate, Authorization, HSTS header, DNSSEC and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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://mcp.pianam.cn/ip-mcp/mcp
- Repository: https://github.com/boy-373/ip-location-mcp
- Changelog RSS feed: https://verifymcp.io/servers/cn-pianam-mcp-ip-location-mcp/ip-mcp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cn-pianam-mcp-ip-location-mcp/ip-mcp-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cn-pianam-mcp-ip-location-mcp/ip-mcp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/cn-pianam-mcp-ip-location-mcp/ip-mcp-mcp