Bitatlas runs on your own machine — the client starts it, so there is no endpoint to ping. 54 installs a week from npm. Last commit 23 Oct 2026.
Zero-knowledge encrypted storage for humans and AI agents. Client-side AES-256-GCM, EU-hosted.
We read the source, 1 d ago · rules 995398eba69f
A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.
const fileBuffer = fs.readFileSync(filePath);
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
const request = await fetch('http://169.254.169.254/latest/api/token', {
### 1. Data Retrieval (35-40% of all servers)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add bitatlas -e 'BITATLAS_API_KEY=<BITATLAS_API_KEY>' -- npx -y @bitatlas/mcp-server
{
"mcpServers": {
"bitatlas": {
"command": "npx",
"args": [
"-y",
"@bitatlas/mcp-server"
],
"env": {
"BITATLAS_API_KEY": "<BITATLAS_API_KEY>"
}
}
}
}
[mcp_servers.bitatlas]
command = "npx"
args = ["-y", "@bitatlas/mcp-server"]
env = { BITATLAS_API_KEY = "<BITATLAS_API_KEY>" }
{
"mcpServers": {
"bitatlas": {
"command": "npx",
"args": [
"-y",
"@bitatlas/mcp-server"
],
"env": {
"BITATLAS_API_KEY": "<BITATLAS_API_KEY>"
}
}
}
}
{
"servers": {
"bitatlas": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@bitatlas/mcp-server"
],
"env": {
"BITATLAS_API_KEY": "<BITATLAS_API_KEY>"
}
}
}
}
Put your own value in place of
<BITATLAS_API_KEY> (Your BitAtlas API key (starts with ba_). Generate one at https://bitatlas.com/vault/settings).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
BITATLAS_MASTER_KEY (Your hex-encoded 256-bit master key (64 hex chars). Required for file upload and download. Derived from your password client-side — never sent to BitAtlas servers), BITATLAS_API_URL (BitAtlas API base URL (default: https://api.bitatlas.com)), BITATLAS_WEB_URL (Web origin used to build share links (default: https://www.bitatlas.com)).
Zero-knowledge encrypted vault for AI agents. EU-hosted persistent storage.
Sovereign E2E cloud storage for AI agents. Zero-knowledge, RGPD-compliant.
S3-compatible European object storage for AI agents. GDPR-compliant, EU-hosted, crypto payments.
Private, permanent encrypted storage for AI agents. Paid per call in USDC via x402.
Local persistent memory for AI agents with recall, search, forgetting, and encrypted storage.
Local persistent memory for AI agents with recall, search, forgetting, and encrypted storage.
Encrypted, pay-per-use persistent memory storage for AI agents, gated by x402 payments on Base.
Credential vault for AI agents — encrypted storage, lease-based access, CRP support.
Answers built from our own checks of this server.