C
Emerging
74/100
15 days ago

Callosium

One shared memory for every AI you use, in plain Markdown files you own. Teach one AI something and the rest know it, with per-AI folder permissions so each assistant only sees what you allow.

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

callosium

Source: 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 4 credentials: CALLOSIUM_DESKTOP_TOKEN, CALLOSIUM_GITHUB_CLIENT_SECRET, CALLOSIUM_GOOGLE_CLIENT_SECRET, CALLOSIUM_SESSION_SECRET
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.
configCALLOSIUM_ACTIVITY_ROOT
configCALLOSIUM_AUTH
configCALLOSIUM_BRAIN
configCALLOSIUM_DESKTOP
🔐 secretCALLOSIUM_DESKTOP_TOKEN
configCALLOSIUM_EMBED_BATCH
configCALLOSIUM_EMBED_DEVICE
configCALLOSIUM_GATE_PROBE
configCALLOSIUM_GITHUB_CLIENT_ID
🔐 secretCALLOSIUM_GITHUB_CLIENT_SECRET
configCALLOSIUM_GOOGLE_CLIENT_ID
🔐 secretCALLOSIUM_GOOGLE_CLIENT_SECRET
configCALLOSIUM_HISTORY_KEEP
configCALLOSIUM_HISTORY_ROOT
configCALLOSIUM_KEYGEN_ACCOUNT
configCALLOSIUM_KEYGEN_API
configCALLOSIUM_MODEL_DIR
configCALLOSIUM_NO_TTY
configCALLOSIUM_SEM_RESCUE_MIN
🔐 secretCALLOSIUM_SESSION_SECRET
configSystemDrive
configSystemRoot
configwindir
// quality suggestions

Tool annotations

5/21 tools have annotations

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

All four hints declared on every tool

16/21 tools missing one or more hints — recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_notes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +13 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

15/21 tool handlers declare input schemas (71%)

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

Tool handlers catch errors

Only 3/21 tool handlers wrap calls in try/catch (14%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Shell command execution

12 child_process calls — runs shell commands

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

Dependency freshness

1/5 production deps stale: gray-matter@2023-07-12 (3.1y)

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 7 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/callosium-callosium-1pn834)](https://m8ven.ai/mcp/callosium-callosium-1pn834)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 59ea5685afc4920f32230192d94e2c09a0a7d6f0
code hash: f8e7ada5707c831a9ccf10cc1e51cef955c37f4e794a17dca97983aa5511ec5c
verified: 8/5/2026, 8:58:42 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