Softwareheritage
NPM · @PIPEWORX/MCP-SOFTWAREHERITAGE · 2 COMPONENTS
Software Heritage MCP. The archive of public source code: which repositories have been archived…
Available components
Last scanned (9 hours ago)
Scores higher than 76% 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
- 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-softwareheritage). 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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 709 tokens (~177/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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 5 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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-softwareheritage@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-softwareheritage |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-softwareheritage/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692354135 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:604ad6bfbc73b28c829b799ca57fc25f8dcb2521f325e703807f62839becbf3cdece8519f76503a5980d10c6a9bc19f8694598643466e9ece106c9824 |
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 →
origin_search ~196
Search the Software Heritage archive for archived origins (repository URLs) whose URL matches a substring or pattern. Returns each matching origin with its visit count and the date it was last captured. Use this to find the archived URL for a project before asking about its status — the archive keys everything on the ORIGIN URL, so "torvalds/linux" finds the GitHub origin and any separately archived copy of the same project on another forge. Sourced from the Software Heritage archive.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum origins to return, 1-1000 (default 10). |
| query | string | yes | Substring of the repository URL to match (e.g. "torvalds/linux", "pallets/flask", "gitlab.com/inkscape"). |
| with_visit | boolean | – | When true, return only origins that have actually been visited and archived (default true). False also returns origins that are merely known. |
No output schema declared.
No examples provided.
origin_status ~142
Report whether one repository URL is archived, and as of when. Returns the most recent visit that produced a usable snapshot: the visit date, the snapshot id, and the visit type (git, hg, svn, npm, pypi…). This is the tool that answers "is this code safe" — a repository that vanishes tomorrow is recoverable from the snapshot named here. Pass the origin URL exactly as it appears in origin_search; the archive treats a differing URL as a different origin. Sourced from the Software Heritage archive.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full origin URL as archived (e.g. "https://github.com/torvalds/linux"). |
No output schema declared.
No examples provided.
origin_visits ~141
List the archive's visit history for one repository URL, newest first: when each capture ran, what it produced, and whether it succeeded ("full"), partially succeeded, or failed ("not_found" — the origin was unreachable at that moment). Use this to see how continuously a project has been captured, and to distinguish "never archived" from "archived for years and unreachable this week". Sourced from the Software Heritage archive.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum visits to return, 1-100 (default 10). |
| url | string | yes | Full origin URL as archived (e.g. "https://github.com/torvalds/linux"). |
No output schema declared.
No examples provided.
revision ~175
Fetch one archived commit by its Software Heritage revision id (the 40-hex id, which for a git repository is the git commit sha). Returns the commit message, author and committer with their dates, the directory id of the tree it points at, and its parent commits. Accepts a bare hex id or a full SWHID ("swh:1:rev:<hex>"). Because the archive is content-addressed, this keeps resolving after the repository it came from has been renamed, moved or deleted. Sourced from the Software Heritage archive.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Revision id — a 40-character hex sha ("309cf37fe2a781279b7675d4bb7173198e532867") or a SWHID ("swh:1:rev:309cf37f…"). |
No output schema declared.
No examples provided.
How do I install the Softwareheritage MCP server?
Softwareheritage runs locally as an npm package, launched with npx -y @pipeworx/mcp-softwareheritage. 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-softwareheritage
claude mcp add pipeworx-io-softwareheritage -- npx -y @pipeworx/mcp-softwareheritage
What is the Softwareheritage MCP server?
Softwareheritage is an MCP server listed in the public MCP registry as io.github.pipeworx-io/softwareheritage. Software Heritage MCP. The archive of public source code: which repositories have been archived… This page covers its npm package (@pipeworx/mcp-softwareheritage).
Is the Softwareheritage MCP server safe to use?
Softwareheritage scores 83 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 Softwareheritage MCP server expose?
Softwareheritage exposes 4 tools: origin_search, origin_status, origin_visits, revision. Their descriptions and schemas cost roughly 654 tokens of context every time the server is loaded.
Is the Softwareheritage MCP server still maintained?
Softwareheritage 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 Softwareheritage MCP server under?
Softwareheritage declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.