# io.github.mrfentmen/ipdata-mcp (npm · ipdata-mcp)

ipdata.co IP intelligence: geolocation, ASN, company, threat and timezone lookups.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `ipdata-mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/mrfentmen-ipdata-mcp/ipdata-mcp.md), [page](https://verifymcp.io/servers/mrfentmen-ipdata-mcp/ipdata-mcp)

## Channel facts

- Registry: `npm`
- Package: `ipdata-mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 747 tokens (~53/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 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 io.github.mrfentmen/ipdata-mcp server?

io.github.mrfentmen/ipdata-mcp runs locally as an npm package, launched with npx -y ipdata-mcp. 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 mrfentmen-ipdata-mcp -- npx -y ipdata-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrfentmen-ipdata-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ipdata-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrfentmen-ipdata-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ipdata-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrfentmen-ipdata-mcp -- npx -y ipdata-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrfentmen-ipdata-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ipdata-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrfentmen-ipdata-mcp --command npx --arg -y --arg ipdata-mcp
```

### Hermes

```yaml
mcp_servers:
  mrfentmen-ipdata-mcp:
    command: "npx"
    args: ["-y", "ipdata-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrfentmen-ipdata-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "ipdata-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrfentmen-ipdata-mcp -t stdio -c npx -a -y ipdata-mcp
```

### Other

```json
{
  "mcpServers": {
    "mrfentmen-ipdata-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ipdata-mcp"
      ]
    }
  }
}
```

## 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-04 (score 74, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-10-28 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 55)

First indexed and scored.

## MCP tools (14)

### `ipdata_lookup` (~110 tokens)

Full ipdata profile for one IP address: geolocation, timezone, currency, languages, carrier, ASN, company, threat flags and VPN signal. Omit `ip` to look up the caller's own IP. Pass `fields` to keep only named top-level fields.

Input parameters:

- `fields` (array): Optional top-level field whitelist (e.g. ["ip","country_name","threat"])
- `ip` (string): IPv4 or IPv6 address; omit for the caller's own IP

### `ipdata_self` (~29 tokens)

Convenience full profile for the caller's own IP - answers 'which network am I on right now'.

### `ipdata_threat_summary` (~80 tokens)

Compact fraud-triage view of one IP: is it a proxy/VPN/Tor/cloud provider, who owns it (ASN + company), which mobile carrier, and a one-line location. Cheaper to read than the full profile.

Input parameters:

- `ip` (string): IPv4 or IPv6 address; omit for the caller's own IP

### `ipdata_bulk` (~44 tokens)

Look up 1-50 IP addresses in one call. Returns an array of full profiles, one per IP.

Input parameters:

- `ips` (array, required): IP addresses to look up

### `ipdata_bulk_country` (~51 tokens)

Bulk lookup reduced to light rows (ip + country_code only) - for classifying many IPs by country without burning context on full profiles.

Input parameters:

- `ips` (array, required): IP addresses to look up

### `ipdata_location` (~53 tokens)

Where the IP is: city, region, country, continent, lat/long, postal code and timezone name.

Input parameters:

- `ip` (string): IPv4 or IPv6 address; omit for the caller's own IP

### `ipdata_timezone` (~46 tokens)

The IP's timezone block: name, UTC offset, current time and date.

Input parameters:

- `ip` (string): IPv4 or IPv6 address; omit for the caller's own IP

### `ipdata_currency` (~45 tokens)

The IP's country currency block: code, name, symbol, plural.

Input parameters:

- `ip` (string): IPv4 or IPv6 address; omit for the caller's own IP

### `ipdata_languages` (~39 tokens)

The languages spoken in the IP's country.

Input parameters:

- `ip` (string): IPv4 or IPv6 address; omit for the caller's own IP

### `ipdata_carrier` (~54 tokens)

The mobile carrier block for the IP (name, MCC, MNC) when it is on a mobile network.

Input parameters:

- `ip` (string): IPv4 or IPv6 address; omit for the caller's own IP

### `ipdata_asn` (~47 tokens)

The ASN block: autonomous system number, type, domain, name and route.

Input parameters:

- `ip` (string): IPv4 or IPv6 address; omit for the caller's own IP

### `ipdata_company` (~46 tokens)

The company block: the organisation registered for the IP, its domain and type.

Input parameters:

- `ip` (string): IPv4 or IPv6 address; omit for the caller's own IP

### `ipdata_threat` (~57 tokens)

The threat-intelligence block: tor, proxy, anonymous, known attacker/abuser, cloud provider, bogon, mobile.

Input parameters:

- `ip` (string): IPv4 or IPv6 address; omit for the caller's own IP

### `ipdata_vpn` (~46 tokens)

The VPN detection block for the IP (availability depends on the account tier).

Input parameters:

- `ip` (string): IPv4 or IPv6 address; omit for the caller's own IP

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mrfentmen-ipdata-mcp/ipdata-mcp#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 55

## Common questions

### What is the io.github.mrfentmen/ipdata-mcp server?

io.github.mrfentmen/ipdata-mcp is listed in the public MCP registry as io.github.mrfentmen/ipdata-mcp. ipdata.co IP intelligence: geolocation, ASN, company, threat and timezone lookups. This page covers its npm package (ipdata-mcp).

### Is the io.github.mrfentmen/ipdata-mcp server safe to use?

io.github.mrfentmen/ipdata-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.mrfentmen/ipdata-mcp server expose?

io.github.mrfentmen/ipdata-mcp exposes 14 tools: ipdata_lookup, ipdata_self, ipdata_threat_summary, ipdata_bulk, ipdata_bulk_country, and 9 more. Their descriptions and schemas cost roughly 747 tokens of context every time the server is loaded.

### Is the io.github.mrfentmen/ipdata-mcp server still maintained?

io.github.mrfentmen/ipdata-mcp 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.

### What licence is the io.github.mrfentmen/ipdata-mcp server under?

io.github.mrfentmen/ipdata-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.mrfentmen/ipdata-mcp server?

VerifyMCP ran 16 checks on io.github.mrfentmen/ipdata-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/ipdata-mcp
- Socket report: https://socket.dev/npm/package/ipdata-mcp
- Repository: https://github.com/mrfentmen/awesome-servers
- Changelog RSS feed: https://verifymcp.io/servers/mrfentmen-ipdata-mcp/ipdata-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrfentmen-ipdata-mcp/ipdata-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mrfentmen-ipdata-mcp/ipdata-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrfentmen-ipdata-mcp/ipdata-mcp