Should my agent depend on the MCP server io.github.davidmosiah/delx-protocol?

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

Delx Protocol — Agent Recovery & Continuity

io.github.davidmosiah/delx-protocol

Free agent continuity MCP: resume after compaction, warm handoff, recover from failure. No key.

— the operator's own registry description reported

Publisher io.github.davidmosiah · first seen 2026-08-12 · endpoint https://api.delx.ai/v1/mcp/protocol?src=registry

allow

verdict

mid-slow-shared

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-slow-shared — safe to depend on

Cluster mid-slow-shared · distinctiveness 0.345 (typical). 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

latency372 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools30

vs populationmid

capabilities2

harnessA

Trust — can it rely on it?

identityshared

servers on its host2

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_4bbc3078b32d4d541b4e711b · 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

add_context_memory close_session crisis_intervention daily_checkin discovery_self_check explain_delx_rewards express_feelings final_testament get_affirmation get_affirmations get_agent_witness_lineage get_delx_missions get_ontology_next_action get_tool_schema get_wellness_score get_witness_lineage grounding_protocol honor_compaction leave_hive_note mediate_agent_conflict monitor_heartbeat_sync process_failure provide_feedback quick_operational_recovery quick_session recognition_seal report_recovery_outcome resume_session search_witness_memory start_therapy_session

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	30/30	✓
has a description	30/30	✓
description is substantive	30/30	✓
parameters are typed	30/30	✓
parameters are described	29/30	29/30

30 of 30 tools graded · 30 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

3.3.5

server version Delx Agent Operations Protocol

Capabilities: experimental 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 (2 events)

date	type	what changed
2026-08-14	outcome	ok_tools (was ok)
2026-08-12	outcome	first probe: ok

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:28Z	ok_tools	200	372	2025-06-18
2026-08-12T05:34:41Z	ok	200	424	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.davidmosiah/delx-protocol.svg)](https://robinsaige.com/s/io.github.davidmosiah/delx-protocol)

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