Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CCS Verifier MCP

NPM · CCS-VERIFIER-MCP

Free, unlimited CCS receipt verification via Ed25519 signatures. CC0-1.0 licensed.

Available components

0 this week 57 Trust /100

Last scanned (15 hours ago)

Scores higher than 27% of npm servers

Category Security

Trust breakdown (7 categories)

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 Security78
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 9 of 16 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency35
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • License check failed: the license (CC0-1.0) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 9 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 116 tokens (~38/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 18 Nov 26 0
    • Security disclosure: fail → pass ▲ functional
  • 12 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 11 Nov 26 57

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/ccs-verifier-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 4 findings
ID CVE Severity Vector Fix available
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 16 packages
Packages resolved 16
Deprecated 1
Stale 8
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~116 tokens

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 →

Tool Tokens
generate_test_receipt ~57

Generate a test CCS receipt for development/testing (requires private key)

NameTypeReqDescription
model_idstring–Model identifier for test receipt
private_keystringyesEd25519 private key (hex-encoded, 64 chars)

No output schema declared.

No examples provided.

get_verifier_info ~24

Get information about the CCS verifier (version, spec, usage stats)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verify_receipt ~35

Verify a CCS (Cryptographic Commitment Scheme) receipt. Free and unlimited.

NameTypeReqDescription
receiptobjectyesCCS receipt to verify

No output schema declared.

No examples provided.

Install

How do I install the CCS Verifier MCP server?

CCS Verifier MCP runs locally as an npm package, launched with npx -y ccs-verifier-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 · ccs-verifier-mcp

# add to Claude Code
claude mcp add dshcorrectover-ccs-verifier-mcp -- npx -y ccs-verifier-mcp
Common questions

What is the CCS Verifier MCP server?

CCS Verifier MCP is listed in the public MCP registry as io.github.DSHCorrectover/ccs-verifier-mcp. Free, unlimited CCS receipt verification via Ed25519 signatures. CC0-1.0 licensed. This page covers its npm package (ccs-verifier-mcp).

Is the CCS Verifier MCP server safe to use?

CCS Verifier MCP scores 57 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. 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 CCS Verifier MCP server expose?

CCS Verifier MCP exposes 3 tools: verify_receipt, get_verifier_info, generate_test_receipt. Their descriptions and schemas cost roughly 116 tokens of context every time the server is loaded.

Is the CCS Verifier MCP server still maintained?

CCS Verifier MCP is still listed as active in the MCP registry. We last reached this channel on 21 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 CCS Verifier MCP server under?

CCS Verifier MCP declares the CC0-1.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

What did VerifyMCP test on the CCS Verifier MCP server?

VerifyMCP ran 15 checks on CCS Verifier MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about CCS Verifier MCP: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.