Clearlydefined
NPM · @PIPEWORX/MCP-CLEARLYDEFINED · 2 COMPONENTS
ClearlyDefined — the licence, copyright attribution and provenance actually found inside an…
Available components
Last scanned (2 hours ago)
Scores higher than 72% of npm servers
Category Security
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-clearlydefined). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 898 tokens (~299/item across 3 items; 3 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 3 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 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
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 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.
- 1 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 78
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-clearlydefined@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-clearlydefined |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-clearlydefined/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612095890 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f000624cec4f765e38c054981ec7960ef6219bd83ce3e1c700cf5d38a22a28d0f86322e5769ffd6396d1c250cfa6f275cb678809cf6e3f605b323d069 |
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 →
clearlydefined_definition ~381
Get the curated licence and attribution record for one exact component version from ClearlyDefined: declared SPDX licence, every licence expression discovered in the files, the copyright holders that must be attributed, the upstream source repo + commit the release was built from, release date, file hashes, and 0-100 completeness scores. AUTHORITATIVE for "what licence is <package>@<version> really under" and "who do I have to attribute" — it reports what scanners found in the shipped files, not just what the manifest claims. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| file_limit | number | – | How many file rows to include when include_files is true. Default 50, max 500. |
| include_files | boolean | – | Include the per-file licence/attribution rows (can be long). Default false. |
| name | string | yes | Component name, e.g. "express", "log4j-core", "requests". |
| namespace | string | – | Group/scope/org, e.g. "org.apache.logging.log4j" for Maven or "@babel" for a scoped npm package. Omit (or pass "-") when the ecosystem has none. |
| provider | string | yes | Where it was published: "npmjs", "mavencentral", "pypi", "rubygems", "nuget", "cratesio", "packagist", "golang", "github", "debian", "cocoapods". |
| revision | string | yes | Exact version or commit, e.g. "4.18.2", "2.17.1", or a git SHA. |
| type | string | yes | Component type: "npm", "maven", "pypi", "gem", "nuget", "crate", "composer", "go", "git", "deb", "pod". |
No output schema declared.
No examples provided.
clearlydefined_harvest_status ~282
List which harvesting tools (ScanCode, Licensee, REUSE, FOSSology, clearlydefined) have analysed one exact component version, and at which tool versions. Use it to judge how much evidence sits behind a definition, or to explain why a definition looks thin. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Component name, e.g. "express", "log4j-core", "requests". |
| namespace | string | – | Group/scope/org, e.g. "org.apache.logging.log4j" for Maven or "@babel" for a scoped npm package. Omit (or pass "-") when the ecosystem has none. |
| provider | string | yes | Where it was published: "npmjs", "mavencentral", "pypi", "rubygems", "nuget", "cratesio", "packagist", "golang", "github", "debian", "cocoapods". |
| revision | string | yes | Exact version or commit, e.g. "4.18.2", "2.17.1", or a git SHA. |
| type | string | yes | Component type: "npm", "maven", "pypi", "gem", "nuget", "crate", "composer", "go", "git", "deb", "pod". |
No output schema declared.
No examples provided.
clearlydefined_search ~182
Find ClearlyDefined component coordinates by name pattern across npm, Maven, PyPI, RubyGems, NuGet, crates.io, Packagist, Go and GitHub. Returns coordinate strings like "npm/npmjs/-/express/4.18.2" that clearlydefined_definition takes. Use it when you know a package name but not its exact ecosystem/namespace/version. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum coordinates to return. Default 25, max 200. |
| pattern | string | yes | Name fragment to match, e.g. "express", "lodash", "requests". Broad or very common fragments can time out upstream — be specific. |
| type | string | – | Optional: keep only coordinates of this component type, e.g. "npm", "maven", "pypi", "git". Filtered client-side. |
No output schema declared.
No examples provided.
How do I install the Clearlydefined MCP server?
Clearlydefined runs locally as an npm package, launched with npx -y @pipeworx/mcp-clearlydefined. 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-clearlydefined
claude mcp add pipeworx-io-clearlydefined -- npx -y @pipeworx/mcp-clearlydefined
What is the Clearlydefined MCP server?
Clearlydefined is an MCP server listed in the public MCP registry as io.github.pipeworx-io/clearlydefined. ClearlyDefined, the licence, copyright attribution and provenance actually found inside an… This page covers its npm package (@pipeworx/mcp-clearlydefined).
Is the Clearlydefined MCP server safe to use?
Clearlydefined scores 82 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 Clearlydefined MCP server expose?
Clearlydefined exposes 3 tools: clearlydefined_search, clearlydefined_definition, clearlydefined_harvest_status. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.
Is the Clearlydefined MCP server still maintained?
Clearlydefined 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 Clearlydefined MCP server under?
Clearlydefined declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.