# Ripe Stat (npm · @pipeworx/mcp-ripe-stat)

RIPE Stat MCP — IP/ASN/BGP data

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

## Components

- remote · `gateway.pipeworx.io`: 71/100, [markdown](https://verifymcp.io/servers/pipeworx-io-ripe-stat/ripe-stat-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ripe-stat/ripe-stat-mcp)
- npm · `@pipeworx/mcp-ripe-stat`: 85/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ripe-stat/pipeworx-mcp-ripe-stat.md), [page](https://verifymcp.io/servers/pipeworx-io-ripe-stat/pipeworx-mcp-ripe-stat)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ripe-stat`
- Version: `0.2.1`
- 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**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ripe-stat).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1148 tokens (~114/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 Ripe Stat MCP server?

Ripe Stat runs locally as an npm package, launched with npx -y @pipeworx/mcp-ripe-stat. 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 pipeworx-io-ripe-stat -- npx -y @pipeworx/mcp-ripe-stat
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-ripe-stat": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ripe-stat"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-ripe-stat": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ripe-stat"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-ripe-stat -- npx -y @pipeworx/mcp-ripe-stat
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-ripe-stat": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-ripe-stat"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-ripe-stat --command npx --arg -y --arg @pipeworx/mcp-ripe-stat
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-ripe-stat:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-ripe-stat"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-ripe-stat": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-ripe-stat"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-ripe-stat -t stdio -c npx -a -y @pipeworx/mcp-ripe-stat
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-ripe-stat": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ripe-stat"
      ]
    }
  }
}
```

## 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 85, +3)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 82)

First indexed and scored.

## MCP tools (10)

### `whois` (~144 tokens)

"Whois lookup for IP / ASN / prefix" / "who owns IP [X]" / "WHOIS for [resource]" — aggregated whois data for an IP address, IP prefix, or AS number across all five RIRs (ARIN, RIPE, APNIC, LACNIC, AFRINIC). Returns registrant org, registration country, abuse contacts, allocation date. Use for IP ownership, abuse-response, network forensics.

Input parameters:

- `resource` (string, required): IP address, prefix, or AS number (e.g. "8.8.8.8", "8.8.8.0/24", "AS15169")

### `network_info` (~86 tokens)

"What ASN does IP [X] belong to" / "network info for [IP]" / "what prefix is [IP] in" — get the allocated prefix and originating ASN for an IPv4/IPv6 address. Use for "which network owns this IP", DDoS source attribution, hosting-provider lookup.

Input parameters:

- `resource` (string, required): IPv4/IPv6 address

### `as_overview` (~113 tokens)

"Who owns AS[N]" / "AS[number] info" / "what company is ASN [X]" / "Cloudflare / Google / Amazon ASN" — summary for an Autonomous System Number (ASN): holder organization, country, AS type (transit / content / IXP), allocation date. Pass "AS15169" or "15169". Use for network attribution, BGP analysis.

Input parameters:

- `asn` (string, required): AS number (e.g. "AS15169" or "15169")

### `asn_neighbours` (~82 tokens)

"BGP peers / neighbours of AS[N]" / "who does [ASN] peer with" / "upstream providers for [AS]" — BGP neighbours of an AS observed by RIPE's RIS (Routing Information Service) route collectors. Use for transit / peering analysis, network topology mapping.

Input parameters:

- `asn` (string, required): AS number

### `bgp_state` (~92 tokens)

"BGP routes for [prefix]" / "what AS announces [IP]" / "BGP hijack check" / "current routing state for [resource]" — origin ASNs and AS-path lengths currently announcing a resource on the global BGP table. Use to detect BGP hijacks, audit route propagation, find anycast announcers.

Input parameters:

- `resource` (string, required): IP, prefix, or ASN

### `abuse_contact` (~90 tokens)

"Abuse contact for IP [X]" / "where to report abuse on [IP / ASN]" / "report spam from [resource]" — official abuse-contact email(s) for an IP, prefix, or ASN drawn from RIR records (inetnum / aut-num objects). Use for spam/abuse/DDoS report routing.

Input parameters:

- `resource` (string, required): IP, prefix, or ASN

### `geoloc` (~96 tokens)

"What country is IP [X] in" / "geolocate [IP]" / "RIR country for [resource]" — country geolocation of an IP or prefix derived from RIR registration data. NOTE: registration-based geo, not GeoIP — accurate for ownership country but not necessarily the host's physical location. Use for compliance / jurisdiction questions where registry truth matters.

Input parameters:

- `resource` (string, required): IP or prefix

### `prefix_overview` (~87 tokens)

"Prefix overview for [CIDR]" / "info on IP block [X/Y]" — comprehensive summary for an IP prefix: BGP announcements, origin ASes, allocation history. Use to understand a whole IP block at once instead of chaining bgp_state + whois.

Input parameters:

- `resource` (string, required): Prefix (e.g. "8.8.8.0/24")

### `ripestat_announced_prefixes` (~164 tokens)

"What IP ranges does AS[N] announce" / "all prefixes for [ASN]" / "what IP blocks does Cloudflare / Google / AWS own" / "netblocks announced by [AS]" — every IPv4 and IPv6 prefix currently announced in global BGP by an Autonomous System, as seen by RIPE's RIS route collectors. AUTHORITATIVE for "which IP ranges belong to this network": use it to build allowlists, attribute traffic to a provider, or size a network's address footprint. Note RIPEstat excludes prefixes seen by fewer than 10 full-feed peers, so very low-visibility announcements are omitted.

Input parameters:

- `asn` (string, required): AS number (e.g. "AS13335" or "13335")

### `ripestat_asn_search` (~141 tokens)

"What is [company]'s ASN" / "find the AS number for [organisation]" / "search ASNs by name" — resolve an organisation or network name to its AS numbers and prefixes using RIPEstat's resource autocomplete. Returns candidate ASNs with their holder descriptions, so it is the lookup step BEFORE as_overview / ripestat_announced_prefixes / asn_neighbours when you only know the company name. Matches on the registered AS name and holder description across all five RIRs.

Input parameters:

- `query` (string, required): Organisation or network name to search for (e.g. "cloudflare", "deutsche telekom")

## Diagnostics

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

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 82

## Common questions

### What is the Ripe Stat MCP server?

Ripe Stat is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ripe-stat. RIPE Stat MCP, IP/ASN/BGP data. This page covers its npm package (@pipeworx/mcp-ripe-stat).

### Is the Ripe Stat MCP server safe to use?

Ripe Stat scores 85 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. Its build provenance is signed and verified. 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 Ripe Stat MCP server expose?

Ripe Stat exposes 10 tools: whois, network_info, as_overview, asn_neighbours, bgp_state, and 5 more. Their descriptions and schemas cost roughly 1,095 tokens of context every time the server is loaded.

### Is the Ripe Stat MCP server still maintained?

Ripe Stat 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 Ripe Stat MCP server under?

Ripe Stat 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 Ripe Stat MCP server?

VerifyMCP ran 16 checks on Ripe Stat, 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/@pipeworx/mcp-ripe-stat
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-ripe-stat
- Repository: https://github.com/pipeworx-io/mcp-ripe-stat
- Website: https://pipeworx.io/packs/ripe-stat
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-ripe-stat/pipeworx-mcp-ripe-stat.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-ripe-stat/pipeworx-mcp-ripe-stat/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-ripe-stat/pipeworx-mcp-ripe-stat.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-ripe-stat/pipeworx-mcp-ripe-stat