Remote MCP · Endpoint

Doichain MCP server

No. Doichain answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://doi-api.sendlabs.de/mcp

The last check completed an MCP handshake.

Registry name
io.github.neubuot/doichain
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
298 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Proof of existence, names and chain data of the Doichain blockchain for AI agents
Listing
From the official MCP registry (active).
Recent checks of Doichain
CheckedResultHandshake
6 hours agoHandshake completed298 ms
9 days agoHandshake completed298 ms
10 days agoHandshake completed297 ms
11 days agoHandshake completed303 ms
12 days agoHandshake completed382 ms
14 days agoHandshake completed309 ms
15 days agoHandshake completed304 ms
15 days agoHandshake completed303 ms
17 days agoHandshake completed295 ms
19 days agoHandshake completed315 ms
22 days agoHandshake completed298 ms
24 days agoHandshake completed306 ms
26 days agoHandshake completed322 ms
28 days agoHandshake completed309 ms

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

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 Doichain and makes no claim about it beyond what these checks measured.