Remote MCP · Endpoint
DERO MCP Server MCP server
Yes, as of 2 hours ago: the hostname does not resolve.
DownLast checked 2 hours ago
Server URL
https://mcp.derod.org/mcp
The last check failed: the hostname does not resolve.
- Registry name
- io.github.DHEBP/dero-mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 33 tools
- Uptime, last 30 days
- 10.5% from 19 checks
- Described by its publisher as
- Read-only DERO blockchain MCP: 33 tools (12 composites) incl. TELA discovery + bundled docs.
- Website
- https://derod.org/
- Repository
- https://github.com/DHEBP/dero-mcp-server
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the hostname does not resolve | — |
| 12 hours ago | Failed - the hostname does not resolve | — |
| 1 day ago | Failed - the hostname does not resolve | — |
| 2 days ago | Failed - the hostname does not resolve | — |
| 4 days ago | Failed - the hostname does not resolve | — |
| 4 days ago | Failed - the hostname does not resolve | — |
| 5 days ago | Failed - the hostname does not resolve | — |
| 6 days ago | Failed - the hostname does not resolve | — |
| 8 days ago | Failed - the hostname does not resolve | — |
| 11 days ago | Failed - the hostname does not resolve | — |
| 13 days ago | Failed - the hostname does not resolve | — |
| 16 days ago | Failed - the hostname does not resolve | — |
| 18 days ago | Failed - the hostname does not resolve | — |
| 20 days ago | Failed - the hostname does not resolve | — |
| 22 days ago | Failed - the hostname does not resolve | — |
| 24 days ago | Failed - the hostname does not resolve | — |
| 26 days ago | Failed - the hostname does not resolve | — |
| 28 days ago | Handshake completed | 275 ms |
| 29 days ago | Handshake completed | 281 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 31.
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 DERO MCP Server and makes no claim about it beyond what these checks measured.