io.github.srbryant86/mcp-server

MCPcommunity
v1.2.2io.github.srbryant86UnknownUpdated 5mo agonpm

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

Enable AI assistants like Claude to verify content authenticity using CertNode's proof infrastructure. Or run directly with npx: Set the environment variable to use a different API endpoint: Verify the authenticity of content by URL or SHA-256 hash. (string, optional): URL of the content to verify (string, optional): SHA-256 hash of the content (string, optional): "quick" or "full" (default:…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.srbryant86
LicenseUnknown
Version1.2.2
Sourcemcp-registry
npm@certnode/mcp-server
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · none privileged
Security scan✓ Cleanv1.2.2 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagev1.2.2 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

verify_contentNo description published

This tool published no description. Forge does not invent one.

search_registryNo description published

This tool published no description. Forge does not invent one.

get_proofNo description published

This tool published no description. Forge does not invent one.

get_trust_scoreNo description published

This tool published no description. Forge does not invent one.

proof_session_startNo description published

This tool published no description. Forge does not invent one.

proof_session_endNo description published

This tool published no description. Forge does not invent one.

proof_log_generationNo description published

This tool published no description. Forge does not invent one.

proof_approveNo description published

This tool published no description. Forge does not invent one.

proof_verifyNo description published

This tool published no description. Forge does not invent one.

sign_ai_outputNo description published

This tool published no description. Forge does not invent one.

0 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Enable AI assistants like Claude to verify content authenticity using CertNode's proof infrastructure. Or run directly with npx: Set the environment variable to use a different API endpoint: Verify the authenticity of content by URL or SHA-256 hash. (string, optional): URL of the content to verify (string, optional): SHA-256 hash of the content (string, optional): "quick" or "full" (default: "quick") Search the CertNode public content registry. (string, required): Search query (string,…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

10 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.