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

io.github.srbryant86/mcp-server

NPM · @CERTNODE/MCP-SERVER · SCANNED AUG 3

Sign AI output for EU AI Act + FRE 902 compliance, verify content authenticity provenance

−13 this week 59 Trust /100
Trust breakdown (6 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 →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1103 tokens (~110/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 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @certnode/mcp-server

# add to Claude Code
claude mcp add srbryant86-mcp-server -- npx -y @certnode/mcp-server
# add to Codex CLI
codex mcp add srbryant86-mcp-server -- npx -y @certnode/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "srbryant86-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@certnode/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add srbryant86-mcp-server --command npx --arg -y --arg @certnode/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  srbryant86-mcp-server:
    command: "npx"
    args: ["-y", "@certnode/mcp-server"]
// mcp.json
{
  "mcpServers": {
    "srbryant86-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@certnode/mcp-server"
      ]
    }
  }
}
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.

  • 2 Aug 26 +15
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass 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
    • Maintenance: unverified → pass functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Licence: MIT functional
  • 1 Aug 26 +15
    • Malware scan: unverified → pass security
  • 31 Jul 26 −4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +14
    • Malware scan: pass → unverified security
    • Dependency health: partial → unverified functional
    • Tool coverage: unverified → 100 functional
  • 28 Jul 26 −53
    • Known CVEs: partial → unverified security
    • Provenance: fail → unverified security
    • Install scripts: pass → unverified security
    • License: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Maintenance: pass → unverified functional
    • Licence: MIT functional
  • 27 Jul 26 +53
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Maintenance: unverified → pass functional
    • License: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: good functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fail functional
    • Licence: MIT functional
  • 26 Jul 26 19

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/@certnode/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 10 exposed · ~1,103 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.

Tool Tokens
get_proof ~57

Get detailed information about a specific proof by its ID. Returns full proof details including timestamps, signatures, and verification chain.

NameTypeReqDescription
proof_idstringyesThe proof ID (e.g., prf_abc123xyz or receipt ID)

No output schema declared.

No examples provided.

get_trust_score ~67

Calculate the trust score for a piece of content. Returns a score from 0-100 and a trust level (unverified, basic, verified, certified).

NameTypeReqDescription
hashstringSHA-256 hash of the content
urlstringURL of the content

No output schema declared.

No examples provided.

proof_approve ~111

Log human approval of AI-generated code. Call this when the developer reviews and accepts code.

NameTypeReqDescription
approval_typestringyesType of approval
commentstringOptional comment about the approval
file_pathstringyesPath to the file being approved
line_endnumberEnding line number of approved code
line_startnumberStarting line number of approved code
session_idstringSession ID. If not provided, uses the active session.

No output schema declared.

No examples provided.

proof_log_generation ~167

Log an AI code generation event. Call this after any AI-generated code is written to create a cryptographic receipt.

NameTypeReqDescription
file_pathstringyesPath to the file containing generated code
lines_changednumberyesNumber of lines of code generated
modelstringAI model used (e.g., "claude-3-opus", "gpt-4")
output_hashstringyesSHA-256 hash of the generated output
prompt_hashstringSHA-256 hash of the prompt (optional, for privacy)
session_idstringSession ID. If not provided, uses the active session.
toolstringyesAI tool that generated the code (e.g., "claude", "copilot")

No output schema declared.

No examples provided.

proof_session_end ~48

End the current development session. This finalizes the proof chain and generates a session summary.

NameTypeReqDescription
session_idstringSession ID to end. If not provided, ends the active session.

No output schema declared.

No examples provided.

proof_session_start ~111

Start a tracked development session for AI code accountability. This creates a cryptographic proof chain for all AI-assisted code changes during the session.

NameTypeReqDescription
ai_toolsarrayAI tools being used (e.g., ["claude", "copilot"])
branchstringGit branch name (optional)
developer_emailstringyesEmail of the developer starting the session
idestringIDE being used for development
repo_urlstringGit repository URL (optional)

No output schema declared.

No examples provided.

proof_verify ~47

Verify the integrity of a session's receipt chain. Returns verification status and any issues found.

NameTypeReqDescription
session_idstringSession ID to verify. If not provided, verifies the active session.

No output schema declared.

No examples provided.

search_registry ~91

Search the CertNode public content registry for proofs. Search by title, organization, creator, or content hash.

NameTypeReqDescription
limitnumberMaximum number of results (default 10, max 50)
querystringyesSearch query (title, organization, creator, or partial hash)
typestringFilter by proof type (e.g., "receipt", "content", "contract")

No output schema declared.

No examples provided.

sign_ai_output ~305

Sign AI-generated content with a cryptographic receipt that proves when it was created, by which model, on whose behalf, with what prompt hash. Returns a signed token + public verification URL. Anyone can verify the signature later via /api/v1/provenance/verify without contacting CertNode. Designed for EU AI Act Article 50 compliance and FRE 902(13)/(14) court admissibility — not for creator badging (use Adobe Content Credentials for that).

NameTypeReqDescription
contentstringyesThe content to sign. Raw text for ai_output / document / json. Base64 for binary (image).
content_typestringHow the content field should be interpreted. Use "ai_output" for AI-generated text. Use "image" for base64-encoded images. Use "document" for documents. Use "json" for structured data.
modelstringOptional AI model identifier (e.g. "claude-opus-4-7", "gpt-4-turbo", "gemini-2.5"). Embedded in the receipt for downstream verification.
prompt_hashstringOptional SHA-256 hex digest of the prompt that generated this content. Privacy-preserving audit signal — proves the prompt existed without revealing it. 64 hex chars.
providerstringOptional AI provider name (e.g. "anthropic", "openai", "google", "mistral"). Embedded in the receipt.

No output schema declared.

No examples provided.

verify_content ~99

Verify the authenticity of content by URL or SHA-256 hash. Returns verification status, trust score, and proof details if the content has been registered with CertNode.

NameTypeReqDescription
hashstringSHA-256 hash of the content (with or without sha256: prefix)
modestringVerification mode. "quick" for basic check, "full" for complete details
urlstringURL of the content to verify

No output schema declared.

No examples provided.