Remote MCP · Endpoint

CBROS Notary & Decision Log MCP server

No. CBROS Notary & Decision Log answered an MCP handshake 13 hours ago.

UpLast checked 13 hours ago

Server URL

https://nftapi.coudrebros.eu/mcp/notary/

The last check completed an MCP handshake.

Registry name
eu.coudrebros/notary
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
336 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 10 checks
Described by its publisher as
Pay-and-anchor a hash or AI decision log on Cardano (CIP-0190). Non-custodial. MCP-native. Mainnet.
Listing
From the official MCP registry (active).
Recent checks of CBROS Notary & Decision Log
CheckedResultHandshake
13 hours agoHandshake completed336 ms
23 hours agoHandshake completed365 ms
1 day agoHandshake completed335 ms
3 days agoHandshake completed338 ms
4 days agoHandshake completed331 ms
5 days agoHandshake completed344 ms
6 days agoHandshake completed576 ms
7 days agoHandshake completed341 ms
9 days agoHandshake completed336 ms
11 days agoHandshake completed331 ms

The last 10 checks. Full history is kept for 30 days; the all-time counter stands at 10 responding of 10.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with CBROS Notary & Decision Log and makes no claim about it beyond what these checks measured.