Comparison · checked 25 September 2026

X-TKN vs Vaulted

Vaulted shipped agent tooling before we did, and theirs is built to read secrets back out. That is the comparison, and it is the one that decides the question if the agent is part of what you are defending against.

Read the API docs See pricing
10K
free ops/month
256-bit
codes, hashed at rest
0
decryption keys we hold
One-time handoff
Retrieval link
x-tkn.com/s/#7f3a9c1e…
one read expires in 24h unread
Encrypted before it left the sender
We hold ciphertext; the key stays in the link
Waiting for the one read…
Where they win

They shipped the agent tooling first

Taking this first because it is the honest order.

  • A first-party MCP server today, free, no account, installed with npx. Ours is in build.
  • A CLI and a GitHub Action. We ship neither.
  • Client-side AES-256-GCM, the same shape as ours.
  • A free tier that covers small handoffs: up to 1,000 characters, 30-day maximum expiry, and 1, 3, 5 or 10 views.
Tool surface

view_secret, and why we have no equivalent

Their MCP source defines create_secret, view_secret, check_status and list_secrets, and view_secret decrypts a secret and can hand it straight back to the agent. The npm release, 0.1.6, still answers "not implemented yet" for it, so today only create_secret works there. It is built to read.

  • Ours will expose create_secret, check_status and revoke_secret. No read tool, by construction.
  • Two of the three names are also theirs, so read the lists side by side.
  • An agent cannot exfiltrate through a tool it does not have.
Where we differ

What the paid tiers add

  • Recipient auth before reveal, by passphrase or an emailed 6-digit code.
  • Retrieval webhooks, and audit history you can export or stream.
  • Per-tenant isolation and per-API-key IP allowlists.
  • 256 KB payloads, against a 1,000-character cap on their free tier.

Being second

We are second here, so this page has to earn its visit on the argument rather than on novelty.

If you want agent tooling today, and an agent being able to read a secret back is acceptable where you work, theirs works and costs nothing. We would rather say that than have you discover it.

If the agent is part of what you are defending against, then a tool list with no read tool is a property you cannot reach by configuring theirs carefully. That is the argument, and it is the whole of it.

Checked against vaulted.fyi, their MCP source on GitHub and the npm release on 25 September 2026. If something here has changed since, tell us and we will correct it.

No account needed

Call it before you commit to it

The sandbox endpoint returns a working key: 100 operations, 24 hours.

Read the API docs Compare with Onetime Secret