
Srbryant86
io.github.srbryant86Published by GitHub account srbryant86v1.2.2Updated Oct 30, 2026
Sign AI output for EU AI Act + FRE 902 compliance, verify content authenticity provenance
Overview
Local CertNode MCP server that lets an assistant sign AI-generated output and verify content authenticity and provenance for compliance records.
- What you can do
- Sign AI output through CertNode, per the description aimed at EU AI Act and FRE 902 compliance.
- Verify content authenticity and provenance, including authenticated verification with an API key.
- Point the client at a custom CertNode API base URL instead of the default endpoint.
- No tool list is published, so the exact operations beyond signing and verification are not documented.
- When to use it
- Use it when you need a verifiable record that a piece of AI-generated content came from a given source, or when signing and verifying outputs is part of a compliance or evidentiary workflow.
- Requirements
- Runs as a local stdio process, installed from the npm package @certnode/mcp-server, so Node.js is needed. A CertNode API key in CERTNODE_API_KEY is required for signing and authenticated verification. CERTNODE_API_URL optionally overrides the API base URL, which defaults to the CertNode API. Desktop client only; network access to CertNode is needed.
Installation
In SourceWeft
- Open Srbryant86 in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
1- v1.2.2LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.