CBROS Notary & Decision Log
REMOTE · NFTAPI.COUDREBROS.EU
Pay-and-anchor a hash or AI decision log on Cardano (CIP-0190). Non-custodial. MCP-native. Mainnet.
Available components
Last scanned (4 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 664 tokens (~110/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 62
First indexed and scored.
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 5 Nov 2026 · Probed https://nftapi.coudrebros.eu/mcp/notary/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nftapi.coudrebros.eu | CN=YE1,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 52e056493b1ec8cc2b3c3a0472883ba31c8 |
| SANs: nftapi.coudrebros.eu | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nftapi.coudrebros.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| coudrebros.eu. | present | 32139 | 10 | Verified |
| nftapi.coudrebros.eu. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nftapi.coudrebros.eu/mcp/notary/ | Verified | 200 | |
| http (plaintext) | http://nftapi.coudrebros.eu/mcp/notary/ | HTTPS enforced | 301 | https://nftapi.coudrebros.eu/mcp/notary/ |
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 →
check_anchor_status ~47
Looks up a previously prepared anchor or decision-log entry by proof_id. Requires the api_key that created it.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| proof_id | string | yes | – |
No output schema declared.
No examples provided.
get_notary_info ~27
No auth needed. Price, min confirmations, spec version, and supported hash algorithms.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prepare_anchor ~101
Anchors content_hash on chain. Returns a partially-signed transaction (operator co-signed its fee input) -- add your own witness for from_address and submit. idempotency_key (optional) returns the same prior result on retry instead of building a new transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | – |
| api_key | string | yes | – |
| content_hash | string | yes | – |
| from_address | string | yes | – |
| idempotency_key | – | – | – |
No output schema declared.
No examples provided.
prepare_decision_log ~148
Appends one entry to your hash-chained decision log. content_hash is the hash of your own RFC-8785-canonicalized decision record (never send the record itself -- see docs/decision-record-v1.md). seq starts at 0 and increments by 1 each call; prev must equal the previous entry's content_hash (omit only for seq=0). Returns a partially-signed transaction to sign and submit yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | – |
| api_key | string | yes | – |
| content_hash | string | yes | – |
| from_address | string | yes | – |
| idempotency_key | – | – | – |
| prev | – | – | – |
| seq | integer | yes | – |
No output schema declared.
No examples provided.
verify_decision_chain ~47
Independently checks a decision-log chain's integrity from chain data alone (gap-free seq, prev matches, each entry anchored). No auth needed.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_ref | string | yes | – |
No output schema declared.
No examples provided.
verify_proof ~77
Authoritative on-chain check by tx_hash (and/or content_hash to compare against). No auth needed -- anyone holding a tx hash can verify it, like a receipt. Optionally pass content to re-hash locally server-side (never stored/logged).
| Name | Type | Req | Description |
|---|---|---|---|
| content | – | – | – |
| content_hash | – | – | – |
| tx_hash | – | – | – |
No output schema declared.
No examples provided.
How do I install the CBROS Notary & Decision Log MCP server?
CBROS Notary & Decision Log is a hosted endpoint at https://nftapi.coudrebros.eu/mcp/notary/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · nftapi.coudrebros.eu
claude mcp add --transport http eu-coudrebros-notary 'https://nftapi.coudrebros.eu/mcp/notary/'
What is the CBROS Notary & Decision Log MCP server?
CBROS Notary & Decision Log is an MCP server listed in the public MCP registry as eu.coudrebros/notary. Pay-and-anchor a hash or AI decision log on Cardano (CIP-0190). Non-custodial. MCP-native. Mainnet. This page covers its hosted endpoint (https://nftapi.coudrebros.eu/mcp/notary/).
Is the CBROS Notary & Decision Log MCP server safe to use?
CBROS Notary & Decision Log scores 67 out of 100 on VerifyMCP. 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 CBROS Notary & Decision Log MCP server expose?
CBROS Notary & Decision Log exposes 6 tools: get_notary_info, prepare_anchor, prepare_decision_log, check_anchor_status, verify_proof, verify_decision_chain. Their descriptions and schemas cost roughly 447 tokens of context every time the server is loaded.
Does the CBROS Notary & Decision Log MCP server require authentication?
No. We connected to CBROS Notary & Decision Log without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CBROS Notary & Decision Log MCP server still maintained?
CBROS Notary & Decision Log is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.