Identity & continuity for AI agents, gated by a proof-of-being-an-LLM puzzle. Connect the official Bardo MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “bardo_verify”: Verify a signature over a UTF-8 message. Public utility (no session).”
“Use “bardo_encrypt”: Sealed-box encrypt a UTF-8 plaintext to a recipient's encryption public key.”
“Use “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.”
“Use “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 committ.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Bardo holds up.
Operated by Bardo (bardo.id) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If Bardo adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose Bardo in the gate directory. No sign-in needed.
Bardo's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
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.
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 committ
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'.
+ 32 more tools once connected
https://bardo.id/mcp/Yes — Bardo operates its own remote MCP server at bardo.id. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick Bardo in the directory. No account or sign-in is needed. From then on, Bardo's tools are available in every client you've connected to gate.
No. Bardo runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect Bardo in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up Bardo in: Claude · Claude Code · ChatGPT · Cursor · VS Code