**Zero-knowledge encrypted cloud storage for AI agents and the humans they work for.** BitAtlas gives your agent a persistent, private vault. Every file is encrypted **client-side with AES-256-GCM before it ever reaches the server** — BitAtlas, and any host running this MCP server, can never read your data. EU-hosted, zero-knowledge by design. ### What your agent can do - **Store & retrieve** — upload, download, list, search, and organize encrypted files and folders ❯ [Image #7] and this ───────────────────────────── 1. Generate an API key at **bitatlas.com/vault/settings** (starts with `ba_`). 2. Provide your **API key** and your **256-bit master key** (64 hex chars, derived from your password client-side — never sent to BitAtlas). 3. Connect — your agent gets an encrypted vault it can read and write, while the data stays unreadable to everyone but you. 🔒 Client-side AES-256-GCM · 🇪🇺 EU-hosted · 🤝 Zero-knowledge share links - **Hand a file to a human** — mint a zero-knowledge share link (`/s/<id>#k=…`) whose decryption key rides in the URL fragment and never touches the server - **Manage shares** — list and revoke share links ### Tools (10) `bitatlas_vault_status` · `bitatlas_list_files` · `bitatlas_search` · `bitatlas_get_file` · `bitatlas_upload_file` · `bitatlas_delete_file` · `bitatlas_create_folder` · `bitatlas_share_file` · `bitatlas_list_shares` · `bitatlas_revoke_share` ### Setup 1. Generate an API key at **bitatlas.com/vault/settings** (starts with `ba_`). 2. Provide your **API key** and your **256-bit master key** (64 hex chars, derived from your password client-side — never sent to BitAtlas). 3. Connect — your agent gets an encrypted vault it can read and write, while the data stays unreadable to everyone but you. 🔒 Client-side AES-256-GCM · 🇪🇺 EU-hosted · 🤝 Zero-knowledge share links Why this copy: it leads with the one-line value prop (SEO + scannability), names the differentiator (zero-knowledge, client-side encryption), lists the concrete tools agents will search for, and makes setup obvious.
What we measured
Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 1,186 ms, 95th percentile 3,079 ms.
When we called tools/list it returned 10 tools, including bitatlas_vault_status, bitatlas_list_files, bitatlas_search, over MCP protocol revision 2025-11-25.
Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 5% and higher on readiness than 88%.
From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure
Tools (10)
As returned by the server's own tools/list when we called it.
- bitatlas_vault_status
- Get vault health status, file count, and storage usage.
- bitatlas_list_files
- List files in the vault. Optionally filter by folder, category, or search term.
- bitatlas_search
- Search vault files by a query string, optionally narrowed to a category.
- bitatlas_get_file
- Get file metadata and download + decrypt the file content. Returns decrypted content as UTF-8 text for text files, or base64 for binary files. Requires BITATLAS…
- bitatlas_upload_file
- Read a local file, encrypt it client-side with AES-256-GCM, and upload it to the vault. Requires BITATLAS_MASTER_KEY. Files over 100 MB are not supported via MC…
- bitatlas_delete_file
- Permanently delete a file from the vault.
- bitatlas_create_folder
- Create a new folder in the vault.
- bitatlas_share_file
- Generate a zero-knowledge share link for a vault file, to hand it to a human. The returned link is PUBLIC: ANYONE who has the link can open and read the file. T…
- bitatlas_list_shares
- List the share links you have created, with their expiry, download count, and status.
- bitatlas_revoke_share
- Revoke a share link so the server stops handing out the file. Note: anyone who already downloaded the file keeps it — revocation only stops future downloads.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (2642 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 10 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.
- Readiness
- Higher than 88% of peers
- This listing 87 · peer median 81
- Latency
- Faster than 5% of peers
- This listing 1,240 ms · peer median 349 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/bitatlas/bitatlas/mcpcurl -X POST https://server.smithery.ai/bitatlas/bitatlas/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'