BitAtlas (bitatlas-group/bitatlas) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

C
Emerging
74/100
1 month ago

BitAtlas

Zero-knowledge encrypted cloud storage for AI agents with client-side AES-256-GCM encryption.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

bitatlas-group

Source: PulseMCP · also listed on mcp.so, Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 6 credentials: BITATLAS_API_KEY, BITATLAS_MASTER_KEY, BITATLAS_WALLET_PRIVATE_KEY, CDP_API_KEY_SECRET, CLEANUP_SECRET, STATS_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretBITATLAS_API_KEY"": "your-api-key",
configBITATLAS_API_URL
🔐 secretBITATLAS_MASTER_KEY"": "your-derived-master-key"
🔐 secretBITATLAS_WALLET_PRIVATE_KEY
configBITATLAS_WEB_URL
configCDP_API_KEY_ID
🔐 secretCDP_API_KEY_SECRET
🔐 secretCLEANUP_SECRET
configGSC_SERVICE_ACCOUNT_JSON
configGSC_SITE_URL
configSHARE_FREE_ACTIVE_CAP
configSHARE_FREE_DAILY_EGRESS
configSHARE_FREE_DEFAULT_DOWNLOADS
configSHARE_FREE_MAX_DOWNLOADS
configSHARE_FREE_MAX_EXPIRY
configSHARE_FREE_MAX_MB
configSHARE_PAID_DAILY_EGRESS
configSHARE_PAID_MAX_EXPIRY
configSHARE_PAID_MAX_MB
🔐 secretSTATS_TOKEN
configX402_ENABLED
configX402_FACILITATOR_URL
configX402_NETWORK
configX402_PRICE_DOWNLOAD
configX402_PRICE_LIST
configX402_PRICE_UPLOAD
configX402_STORAGE_DAYS_INCLUDED
configX402_WALLET_ADDRESS
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_API_URL
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

10/10 tools missing one or more hints — bitatlas_vault_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bitatlas_list_files (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bitatlas_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 0/10 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not logged

2 secret values sent to console.log

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/bitatlas-group/bitatlas)](https://m8ven.ai/mcp/bitatlas-group/bitatlas)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ebb715734865e248d8396fcaa68681b6fb392869
code hash: a06d34144c8022d14594349aa7d00cd74ac5fdc5609688ab19a315a04c01c6af
verified: 7/26/2026, 8:49:51 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client