Should my agent depend on the MCP server io.github.DHEBP/dero-mcp-server?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

DERO MCP Server

io.github.DHEBP/dero-mcp-server

Read-only DERO blockchain MCP: 33 tools (12 composites) incl. TELA discovery + bundled docs.

— the operator's own registry description reported

Publisher io.github.DHEBP · first seen 2026-08-12 · endpoint https://mcp.derod.org/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.569 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency344 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools33

vs populationhigh

capabilities3

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_66fff8941e3b7a5c597f5924 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

audit_chain_artifact_claim dero_daemon_echo dero_daemon_ping dero_decode_proof_string dero_docs_get_page dero_docs_list dero_docs_search dero_durl_to_scid dero_forge_demo_proof dero_get_block dero_get_block_count dero_get_block_header_by_hash dero_get_block_header_by_topo_height dero_get_block_template dero_get_encrypted_balance dero_get_gas_estimate dero_get_height dero_get_info dero_get_last_block_header dero_get_random_address dero_get_sc dero_get_transaction dero_get_tx_pool dero_name_to_address dero_tela_list_apps diagnose_chain_health estimate_deploy_cost explain_smart_contract recommend_docs_path tela_get_doc_content tela_inspect trace_transaction_with_context verify_supply

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	33/33	✓
has a description	33/33	✓
description is substantive	33/33	✓
parameters are typed	33/33	✓
parameters are described	33/33	✓

33 of 33 tools graded · 33 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.5.2

server version dero-daemon-mcp

Capabilities: prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:59Z	ok_tools	200	344	2025-06-18
2026-08-12T05:34:14Z	ok_tools	200	366	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.DHEBP/dero-mcp-server.svg)](https://robinsaige.com/s/io.github.DHEBP/dero-mcp-server)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview