About srbryant86
Sign AI output for EU AI Act and FRE 902 compliance, verify content authenticity and provenance
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @certnode/mcp-serverCERTNODE_API_KEYSecretCertNode API key from https://certnode.io/dashboard/api-keys (required for sign_ai_output and authenticated verification)CERTNODE_API_URLCertNode API base URL. Defaults to https://certnode.io/api/v1Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
10Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| url | string | No | URL of the content to verify |
| hash | string | No | SHA-256 hash of the content (with or without sha256: prefix) |
| mode | enum | No | Verification mode. "quick" for basic check, "full" for complete detailsquick | full |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.