io.github.srbryant86/mcp-server
NPM · @CERTNODE/MCP-SERVER · SCANNED SEP 20
Sign AI output for EU AI Act + FRE 902 compliance, verify content authenticity provenance
Available components
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 145 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).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 Management90
- Stability observed for 27 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
How do I install the io.github.srbryant86/mcp-server server?
io.github.srbryant86/mcp-server runs locally as an npm package, launched with npx -y @certnode/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @certnode/mcp-server
claude mcp add srbryant86-mcp-server -- npx -y @certnode/mcp-server
{
"mcpServers": {
"srbryant86-mcp-server": {
"command": "npx",
"args": [
"-y",
"@certnode/mcp-server"
]
}
}
} {
"servers": {
"srbryant86-mcp-server": {
"command": "npx",
"args": [
"-y",
"@certnode/mcp-server"
]
}
}
} codex mcp add srbryant86-mcp-server -- npx -y @certnode/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"srbryant86-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@certnode/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add srbryant86-mcp-server --command npx --arg -y --arg @certnode/mcp-server
mcp_servers:
srbryant86-mcp-server:
command: "npx"
args: ["-y", "@certnode/mcp-server"] {
"McpServers": {
"srbryant86-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@certnode/mcp-server"
]
}
}
} assistant mcp add srbryant86-mcp-server -t stdio -c npx -a -y @certnode/mcp-server
{
"mcpServers": {
"srbryant86-mcp-server": {
"command": "npx",
"args": [
"-y",
"@certnode/mcp-server"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/@certnode/mcp-server@1.2.2
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 →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
get_proof ~57
Get detailed information about a specific proof by its ID. Returns full proof details including timestamps, signatures, and verification chain.
| Name | Type | Req | Description |
|---|---|---|---|
| proof_id | string | yes | The 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).
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | – | SHA-256 hash of the content |
| url | string | – | URL 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.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_type | string | yes | Type of approval |
| comment | string | – | Optional comment about the approval |
| file_path | string | yes | Path to the file being approved |
| line_end | number | – | Ending line number of approved code |
| line_start | number | – | Starting line number of approved code |
| session_id | string | – | Session 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.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the file containing generated code |
| lines_changed | number | yes | Number of lines of code generated |
| model | string | – | AI model used (e.g., "claude-3-opus", "gpt-4") |
| output_hash | string | yes | SHA-256 hash of the generated output |
| prompt_hash | string | – | SHA-256 hash of the prompt (optional, for privacy) |
| session_id | string | – | Session ID. If not provided, uses the active session. |
| tool | string | yes | AI 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.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | – | Session 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.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_tools | array | – | AI tools being used (e.g., ["claude", "copilot"]) |
| branch | string | – | Git branch name (optional) |
| developer_email | string | yes | Email of the developer starting the session |
| ide | string | – | IDE being used for development |
| repo_url | string | – | Git 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.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | – | Session 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results (default 10, max 50) |
| query | string | yes | Search query (title, organization, creator, or partial hash) |
| type | string | – | Filter 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).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The content to sign. Raw text for ai_output / document / json. Base64 for binary (image). |
| content_type | string | – | How 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. |
| model | string | – | Optional AI model identifier (e.g. "claude-opus-4-7", "gpt-4-turbo", "gemini-2.5"). Embedded in the receipt for downstream verification. |
| prompt_hash | string | – | Optional 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. |
| provider | string | – | Optional 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.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | – | SHA-256 hash of the content (with or without sha256: prefix) |
| mode | string | – | Verification mode. "quick" for basic check, "full" for complete details |
| url | string | – | URL of the content to verify |
No output schema declared.
No examples provided.
What is the io.github.srbryant86/mcp-server server?
io.github.srbryant86/mcp-server is listed in the public MCP registry as io.github.srbryant86/mcp-server. Sign AI output for EU AI Act + FRE 902 compliance, verify content authenticity provenance. This page covers its npm package (@certnode/mcp-server).
Is the io.github.srbryant86/mcp-server server safe to use?
io.github.srbryant86/mcp-server scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.srbryant86/mcp-server server expose?
io.github.srbryant86/mcp-server exposes 10 tools: verify_content, search_registry, get_proof, get_trust_score, proof_session_start, and 5 more. Their descriptions and schemas cost roughly 1,103 tokens of context every time the server is loaded.
Is the io.github.srbryant86/mcp-server server still maintained?
io.github.srbryant86/mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.srbryant86/mcp-server server under?
io.github.srbryant86/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.