Ripe Stat
NPM · @PIPEWORX/MCP-RIPE-STAT · 2 COMPONENTS
RIPE Stat MCP — IP/ASN/BGP data
Available components
Last scanned (13 hours ago)
Scores higher than 87% of npm servers
Category Cloud Infrastructure
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ripe-stat). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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.
- 4 Nov 26 +3
- 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. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 82
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-ripe-stat@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-ripe-stat |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ripe-stat/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691889263 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b219c47aa19f9363ab2a12513992fd0dc1f024bc6675413eff15de4d017d8c4d43951be72d9e18d715466afbb2e6a0d3dc86eef85493ee7ad9f93b4be |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
abuse_contact ~90
"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.
| Name | Type | Req | Description |
|---|---|---|---|
| resource | string | yes | IP, prefix, or ASN |
No output schema declared.
No examples provided.
as_overview ~113
"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.
| Name | Type | Req | Description |
|---|---|---|---|
| asn | string | yes | AS number (e.g. "AS15169" or "15169") |
No output schema declared.
No examples provided.
asn_neighbours ~82
"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.
| Name | Type | Req | Description |
|---|---|---|---|
| asn | string | yes | AS number |
No output schema declared.
No examples provided.
bgp_state ~92
"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.
| Name | Type | Req | Description |
|---|---|---|---|
| resource | string | yes | IP, prefix, or ASN |
No output schema declared.
No examples provided.
geoloc ~96
"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.
| Name | Type | Req | Description |
|---|---|---|---|
| resource | string | yes | IP or prefix |
No output schema declared.
No examples provided.
network_info ~86
"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.
| Name | Type | Req | Description |
|---|---|---|---|
| resource | string | yes | IPv4/IPv6 address |
No output schema declared.
No examples provided.
prefix_overview ~87
"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.
| Name | Type | Req | Description |
|---|---|---|---|
| resource | string | yes | Prefix (e.g. "8.8.8.0/24") |
No output schema declared.
No examples provided.
ripestat_announced_prefixes ~164
"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.
| Name | Type | Req | Description |
|---|---|---|---|
| asn | string | yes | AS number (e.g. "AS13335" or "13335") |
No output schema declared.
No examples provided.
ripestat_asn_search ~141
"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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Organisation or network name to search for (e.g. "cloudflare", "deutsche telekom") |
No output schema declared.
No examples provided.
whois ~144
"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.
| Name | Type | Req | Description |
|---|---|---|---|
| resource | string | yes | IP address, prefix, or AS number (e.g. "8.8.8.8", "8.8.8.0/24", "AS15169") |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-ripe-stat
claude mcp add pipeworx-io-ripe-stat -- npx -y @pipeworx/mcp-ripe-stat
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.