Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.bitatlas-group/bitatlas

NPM · @BITATLAS/MCP-SERVER

Zero-knowledge encrypted storage for humans and AI agents. Client-side AES-256-GCM, EU-hosted.

0 this week 82 Trust /100

Last scanned (20 hours ago)

Scores higher than 71% of npm servers

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 34 of 125 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 600 tokens (~60/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "bitatlas_delete_file" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Nov 26 +1
    • Stability: 0.97 → pass security
  • 17 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 30 Oct 26 +3
    • CVE-2023-54404 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
    • Stability: 0.97 → pass security
  • 29 Oct 26 0
    • Stability: pass → 0.97 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@bitatlas/mcp-server@1.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 125 packages
Packages resolved 125
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~600 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bitatlas_create_folder ~44

Create a new folder in the vault.

NameTypeReqDescription
namestringyesFolder name
parent_idstring–Parent folder ID (omit to create at root)

No output schema declared.

No examples provided.

bitatlas_delete_file ~31

Permanently delete a file from the vault.

NameTypeReqDescription
file_idstringyesFile UUID to delete

No output schema declared.

No examples provided.

bitatlas_get_file ~57

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_MASTER_KEY.

NameTypeReqDescription
file_idstringyesFile UUID

No output schema declared.

No examples provided.

bitatlas_list_files ~61

List files in the vault. Optionally filter by folder, category, or search term.

NameTypeReqDescription
categorystring–Filter by category
folderIdstring–Filter by folder ID
searchstring–Search by file name

No output schema declared.

No examples provided.

bitatlas_list_shares ~29

List the share links you have created, with their expiry, download count, and status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bitatlas_revoke_share ~55

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.

NameTypeReqDescription
share_idstringyesShare ID to revoke

No output schema declared.

No examples provided.

bitatlas_search ~47

Search vault files by a query string, optionally narrowed to a category.

NameTypeReqDescription
categorystring–Narrow results to this category
querystringyesSearch query (file name)

No output schema declared.

No examples provided.

bitatlas_share_file ~147

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. The decryption key is in the URL fragment (#k=...) — BitAtlas never sees it and cannot read the file, but whoever you send the link to can. Confirm with the user before sharing anything sensitive. Requires BITATLAS_MASTER_KEY.

NameTypeReqDescription
expires_instring–How long the link stays live (default 7d)
file_idstringyesFile UUID to share
max_downloadsnumber–Optional cap on total downloads before the link expires

No output schema declared.

No examples provided.

bitatlas_upload_file ~106

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 MCP.

NameTypeReqDescription
categorystring–File category
file_pathstringyesAbsolute or relative path to the local file
folder_idstring–Destination folder ID (omit for root)
namestring–Override display name (defaults to the filename)

No output schema declared.

No examples provided.

bitatlas_vault_status ~23

Get vault health status, file count, and storage usage.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.bitatlas-group/bitatlas MCP server?

io.github.bitatlas-group/bitatlas runs locally as an npm package, launched with npx -y @bitatlas/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @bitatlas/mcp-server

# add to Claude Code
claude mcp add bitatlas-group-bitatlas -- npx -y @bitatlas/mcp-server
Common questions

What is the io.github.bitatlas-group/bitatlas MCP server?

io.github.bitatlas-group/bitatlas is an MCP server listed in the public MCP registry as io.github.bitatlas-group/bitatlas. Zero-knowledge encrypted storage for humans and AI agents. Client-side AES-256-GCM, EU-hosted. This page covers its npm package (@bitatlas/mcp-server).

Is the io.github.bitatlas-group/bitatlas MCP server safe to use?

io.github.bitatlas-group/bitatlas scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.bitatlas-group/bitatlas MCP server expose?

io.github.bitatlas-group/bitatlas exposes 10 tools: bitatlas_vault_status, bitatlas_list_files, bitatlas_search, bitatlas_get_file, bitatlas_upload_file, and 5 more. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.

Is the io.github.bitatlas-group/bitatlas MCP server still maintained?

io.github.bitatlas-group/bitatlas is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.bitatlas-group/bitatlas MCP server under?

io.github.bitatlas-group/bitatlas declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.bitatlas-group/bitatlas MCP server?

VerifyMCP ran 16 checks on io.github.bitatlas-group/bitatlas, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.