InternetData
NPM · INTERNETDATA-MCP · 2 COMPONENTS
List InternetData's IP and ASN databases, your license for each, what one holds, and its digests.
Available components
Last scanned (22 hours ago)
Scores higher than 93% of npm servers
Category Code Search and Documentation
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
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to internetdata/mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 556 tokens (~139/item across 4 items; 4 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 Management53
- Stability observed for 16 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- Package version: 3.1.9 → 3.1.10 functional
- 2 Nov 26 −25
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: 1.00 → unverified ▼ functional
- Package version: 3.1.7 → 3.1.9 functional
- Package version: 3.1.7 → 3.1.8 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +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.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 24 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
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 4 Nov 2026 · Analysed npm/internetdata-mcp@3.1.10
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 | internetdata/mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/internetdata/mcp/.github/workflows/release.yml@refs/tags/v3.1.10 |
| Rekor log index | 3662412270 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d72734f3b6fb80237587667d0e2442e2f68583770f65cd4392d8a198d53e1dcd501b9b8d89aa9a56489c9582f5b0b3d9818ea365b6364652e3cda312b |
Background: How many MCP packages publish verified provenance →
Dependencies 6 packages
| Packages resolved | 6 |
|---|---|
| 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 →
database_checksum Get a database's checksums ~142
The published digests for one database file, for verifying a copy you already hold or deciding whether a build has changed since you last fetched it. It is licensed like the download itself, so a database this key cannot download is refused here too. Looking up a checksum is not a download and does not appear in `list_downloads`.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | A VERSIONED database ID, from `versions[].id` in `list_databases` - `bogon_ip_v1`, not `bogon_ip`. The unversioned base ID is a license reference and is not accepted here. |
| format | string | yes | Which published file to digest. |
| Name | Type | Req | Description |
|---|---|---|---|
| checksums | object | yes | – |
No examples provided.
database_metadata Describe a database ~129
What is inside one database before you fetch it: the columns in each published format with their types, a few sample rows, the row count, the build date and the file sizes. Use this to answer questions about what a database contains without downloading it - the files reach several GB - and to budget a transfer before starting one.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | A VERSIONED database ID, from `versions[].id` in `list_databases` - `bogon_ip_v1`, not `bogon_ip`. The unversioned base ID is a license reference and is not accepted here. |
| Name | Type | Req | Description |
|---|---|---|---|
| entries | integer | yes | Row count in the current build. |
| id | string | yes | – |
| sample | object | – | A few real rows, keyed by format. |
| sample_entries | integer | – | Row count in the evaluation sample. |
| sample_size | object | – | Bytes per format of the evaluation sample, where one is published. |
| schema | object | yes | Columns, keyed by format. |
| size | object | yes | Bytes per format. |
| update_freq | string | – | How often a new build is published. |
| updated | string | yes | ISO-8601 date (YYYY-MM-DD) the published build was generated on. |
No examples provided.
list_databases List databases ~151
The IP database catalog as this API key's organization may see it, one entry per database FAMILY, with `standing` saying where their license stands: `licensed` if the family is theirs today, `expired` if the term has ended, `unlicensed` if it is published but has never been bought. Each entry has a `base` ID, which is what a license names, and a `versions` array whose `id` is what the other tools take - pass `versions[].id` (`bogon_ip_v1`), never the `base` (`bogon_ip`). Ask again rather than holding on to this: it is answered per key and is not the same for everyone.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| databases | array | yes | – |
No examples provided.
list_downloads List recent download attempts ~134
This organization's own recent download attempts, newest first, REFUSALS INCLUDED - a denial carries the `outcome` and `http_status` that answer "it stopped working", which nothing else here can. Use it to explain a failing fetch, to confirm a transfer ran, or to check whether a request was theirs. This is a bounded WINDOW of at most 200 rows, so a database missing from the answer means it is not in this window - never that it was never downloaded.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many attempts to return, newest first. At most 200; the API defaults to 50. |
| Name | Type | Req | Description |
|---|---|---|---|
| downloads | array | yes | – |
No examples provided.
How do I install the InternetData MCP server?
InternetData runs locally as an npm package, launched with npx -y internetdata-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · internetdata-mcp
claude mcp add io-internetdata-mcp -- npx -y internetdata-mcp
What is the InternetData MCP server?
InternetData is an MCP server listed in the public MCP registry as io.internetdata/mcp. List InternetData's IP and ASN databases, your license for each, what one holds, and its digests. This page covers its npm package (internetdata-mcp).
Is the InternetData MCP server safe to use?
InternetData scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 InternetData MCP server expose?
InternetData exposes 4 tools: list_databases, database_metadata, database_checksum, list_downloads. Their descriptions and schemas cost roughly 556 tokens of context every time the server is loaded.
Is the InternetData MCP server still maintained?
InternetData is still listed as active in the MCP registry. We last reached this channel on 4 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 InternetData MCP server under?
InternetData declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.