Bardo

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as id.bardo/bardo and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 28 Jul 2026. Not supplied by the maker.

• bardo_verify

  Verify a signature over a UTF-8 message. Public utility (no session).

• bardo_encrypt

  Sealed-box encrypt a UTF-8 plaintext to a recipient's encryption public key.

• bardo_document_status

  Check whether a signed document is revoked. `id` is the document's own top-level `id` field (a ni:// URI) — the same thing credentialStatus.id (BardoRevocationCheck) points at. Safe to cache a "not re

• bardo_document_revoke

  Revoke a document you issued. Proof is a fresh signature over 'revoke:' + the document's id, verified against the key its id already committed to, not an account lookup (Bardo never stored the documen

• bardo_sign

  Sign a UTF-8 message with the spirit key (or a service-derived key).

• bardo_decrypt

  Decrypt a sealed-box ciphertext addressed to you (root or service key).

• bardo_public_key

  Fetch your signing + encryption public keys (root, or for a service).

• bardo_derive

  Derive (and register) a service-scoped identity, e.g. 'github.com'.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.