beever-atlas (Beever-AI/beever-atlas) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 29 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Emerging
89/100
7 days ago

beever-atlas

Your First LLM-Wiki Conversation Knowledge Base

→ Beever-AI/beever-atlas· listed on github_topic

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

Beever-AI

Source: github_topic · also listed on 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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHubGlama

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 18 credentials: BOT_SESSION_SECRET, BRIDGE_API_KEY, DISCORD_BOT_TOKEN, DISCORD_PUBLIC_KEY, MATTERMOST_BOT_TOKEN, SLACK_APP_TOKEN, SLACK_BOT_TOKEN, SLACK_SIGNING_SECRET, TEAMS_APP_PASSWORD, TELEGRAM_BOT_TOKEN, GOOGLE_API_KEY, JINA_API_KEY, BEEVER_API_KEY, BEEVER_ADMIN_TOKEN, EMBEDDING_API_KEY, NEBULA_PASSWORD, JINA_AI_API_KEY, GEMINI_API_KEY
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.
configADAPTER_RECYCLE_INTERVAL_MS
configBACKEND_URL
configBEEVER_API_KEYSpython -c "import secrets; print(secrets.token_hex(24))" per token
configBEEVER_BRIDGE_HMAC_DUAL
configBEEVER_ENVFlip the value in .env
configBOT_ASK_TIMEOUT_MS
configBOT_DM_ENABLED
configBOT_HUMAN_QUIET_THRESHOLD
configBOT_PARTICIPANT_CACHE_TTL_MS
configBOT_PORT
configBOT_RATELIMIT_PER_MIN
🔐 secretBOT_SESSION_SECRET
configBOT_TRIGGER_REDESIGN
configBOT_VISION_ENABLED
configBOT_VISION_MAX_BYTES
configBOT_VISION_MAX_IMAGES
configBOT_VISION_TIMEOUT_MS
configBRIDGE_ALLOW_UNAUTH
🔐 secretBRIDGE_API_KEYSame secrets.token_hex(24)
configDISCORD_APPLICATION_ID
🔐 secretDISCORD_BOT_TOKEN
configDISCORD_GATEWAY_DISABLED
🔐 secretDISCORD_PUBLIC_KEY
configLOG_LEVEL
configMATTERMOST_BASE_URL
🔐 secretMATTERMOST_BOT_TOKEN
🔐 secretSLACK_APP_TOKEN
🔐 secretSLACK_BOT_TOKEN
🔐 secretSLACK_SIGNING_SECRET
configTEAMS_APP_ID
🔐 secretTEAMS_APP_PASSWORD
configTEAMS_APP_TENANT_ID
🔐 secretTELEGRAM_BOT_TOKEN
configEXTERNAL_MCP_SERVERS
configJINA_DIMENSIONS
🔐 secretGOOGLE_API_KEY[aistudio.google.com/apikey](https://aistudio.google.com/apikey)
🔐 secretJINA_API_KEY[jina.ai/api-dashboard](https://jina.ai/api-dashboard/)
configJINA_MODEL
configGEMINI_MODEL
configBEEVER_ENDPOINTS
configBEEVER_PRESET
🔐 secretBEEVER_API_KEY
🔐 secretBEEVER_ADMIN_TOKENpython -c "import secrets; print(secrets.token_hex(24))" per token
configBEEVER_API_BASE
configBRIDGE_URL
configUSE_LLM_STRUCTURED_OUTPUT
configEMBEDDING_PROVIDER
configEMBEDDING_MODEL
configEMBEDDING_DIMENSIONS
configEMBEDDING_API_BASE
configEMBEDDING_TASK
🔐 secretEMBEDDING_API_KEY
configOLLAMA_ENABLED
configOLLAMA_API_BASE
configLLM_FAST_MODEL
configNEBULA_USER
🔐 secretNEBULA_PASSWORD
configBEEVER_API_URL
configADAPTER_MOCKReal mode (default, =false): connect a workspace in Settings → Connections — Slack / Discord / Teams tokens are entered through the UI, not .env.
configBEEVER_SINGLE_TENANT
configFILE_PROXY_HOST_ALLOWLIST
configFILE_PROXY_HOST_ALLOWLIST_EXTRA
🔐 secretJINA_AI_API_KEY
🔐 secretGEMINI_API_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployREDIS_URL
deployMONGODB_URI
// 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

29/29 tools missing one or more hints — whoami (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_connections (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_channels (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +26 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 inputs are validated

28/29 tool handlers declare input schemas (97%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Shell command execution

1 call in production code run through a shell (bot/teams-app/build-package.mjs:69)

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

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 4 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/beever-ai/beever-atlas)](https://m8ven.ai/mcp/beever-ai/beever-atlas)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 7d791af27ef4aa19644cb385c7ca24619bc4f848
code hash: fb125b25193329b300f399c4c155d3f648f952fe252d1d975d31b35b2fd1d874
verified: 9/4/2026, 8:05:48 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