BitAtlas
https://mcp.bitatlas.com/mcp ↗
Description
**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
What our measurements say
BitAtlas is a remote MCP server published at mcp.bitatlas.com. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 381 ms, placing it among the faster endpoints. It offers a narrow, focused set of 10 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names clearly indicate their purpose (e.g., 'bitatlas_upload_file' for uploading).
- Some tools explicitly mention constraints (e.g., 100MB file size limit for uploads).
Weaknesses
- Descriptions often omit parameter requirements (e.g., which parameters are optional/required).
- Error handling and edge cases are not consistently documented across tools.
bitatlas_get_file— Does not specify if BITATLAS_MASTER_KEY is optional or required in parameters.bitatlas_delete_file— No mention of irreversible deletion or error conditions (e.g., file not found).bitatlas_share_file— Incomplete description (truncated) and lacks parameter details for share link generation.
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · system moved to legacy mode with compliance score activation
- 2026-09-11T01:59:45.474Z — complianceScore increased from null to 100 · full compliance achieved in legacy era
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test passed · last run:
- Cold-start: cold 7ms → warm 8ms (penalty 0ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.1.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/bitatlas-bitatlas)<a href="https://mcpmetrics.io/servers/bitatlas-bitatlas"><img src="https://mcpmetrics.io/badge/bitatlas/bitatlas/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see