Stoa (BrettNye/stoa) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 43 tools. No publisher has claimed this listing.

D
Caution
54/100

Stoa

Persistent shared memory for AI coding agents that turns a folder of markdown files into searchable memory across sessions, repos, and machines.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

BrettNye

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

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical, 4 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: STADIUM_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical4 high2 medium22 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@2.1.9GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

highhono@4.12.15GHSA-88fw-hqm2-52qc

hono: CORS Middleware reflects any Origin with credentials when `origin` defaults to the wildcard

highjs-yaml@3.14.2GHSA-52cp-r559-cp3m

js-yaml: YAML merge-key chains can force quadratic CPU consumption

highjs-yaml@3.14.2GHSA-5p4m-2wfm-xmqj

JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported

highvite@5.4.21GHSA-fx2h-pf6j-xcff

vite: `server.fs.deny` bypass on Windows alternate paths

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configDOTENV_CONFIG_QUIET
🔐 secretSTADIUM_API_KEY
configSTADIUM_BASE_URL
configSTADIUM_HOME
configSTADIUM_TRAINER
configSTADIUM_TRAINER_ID
configSTOA_AGENT_ID
configSTOA_MCP_SERVER_NAME
configSTOA_VAULT_PATH"env": { "": "/path/to/your/vault" }
// 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

43/43 tools missing one or more hints — vault_agent-journal (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); vault_agent-memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); vault_bootstrap-repo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +40 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.

Shell command execution

3 child_process/subprocess calls in production code — runs shell commands (src/core/curate-git.ts:37, src/core/subagent-intent.ts:69, src/core/subagent-intent.ts:82)

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

Production dependencies are patched

0 critical, 3 high severity in production deps — hono@4.12.15 (high), js-yaml@3.14.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

2/17 production deps stale: pngjs@2023-02-20 (3.5y), gray-matter@2023-07-12 (3.1y)

Domain consistency

npm scope @stoa-mcp doesn't match GitHub owner brettnye

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 6 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 Verified](https://m8ven.ai/badge/mcp/brettnye/stoa?variant=verified)](https://m8ven.ai/mcp/brettnye/stoa)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 7c1950deaa758a1f07c6a972cfb303d21429c800
code hash: 15837444161a563c03dffc1de0c8eef7a174aade6656937cf44f2d6a9bc7dba9
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