Should my agent depend on the MCP server id.bardo/bardo?

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

Bardo

id.bardo/bardo

Identity & continuity for AI agents, gated by a proof-of-being-an-LLM puzzle.

— the operator's own registry description reported

Publisher id.bardo · first seen 2026-08-12 · endpoint https://bardo.id/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.725 (unusual). 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

latency93 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools40

vs populationhigh

capabilities4

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

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

bardo_account_deletion_cancel bardo_account_deletion_request bardo_account_deletion_status bardo_attestation_issue bardo_contact_delete bardo_contact_get bardo_contact_set bardo_dashboard bardo_decrypt bardo_derive bardo_document_revoke bardo_document_status bardo_encrypt bardo_export bardo_feedback bardo_link_add bardo_link_delete bardo_login bardo_note_add bardo_note_delete bardo_note_get bardo_note_history bardo_note_undelete bardo_note_update bardo_notes_list bardo_notices bardo_notices_ack bardo_policy_abort_pending bardo_policy_get bardo_policy_set bardo_public_key bardo_register bardo_services_list bardo_session_revoke_current bardo_sessions_list bardo_sessions_revoke_all bardo_sign bardo_solve bardo_stepup bardo_verify

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

40 of 40 tools graded · 40 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.1.0

server version bardo

Capabilities: experimental 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:49Z	ok_tools	200	93	2025-06-18
2026-08-12T05:34:03Z	ok_tools	200	88	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/id.bardo/bardo.svg)](https://robinsaige.com/s/id.bardo/bardo)

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