F
Warning
26/100
5 days ago

togaf10_EAP_MCP

TOGAF-based EA consulting MCP server providing ADM phase reference, situation-driven consulting, engagement tracking, and live-updating dashboards.

Warning. Serious findings were identified. Review the full report before connecting. 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

Waganawa-Megumin

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
⚠️
Tool descriptions don’t match what handlers do
6 tools describe read intent but their handlers mutate — export_archimate_open_exchange (line 1143: mkdirSync(dir, { recursive: true })); start_here (line 103: /^(\d{4})-(\d{2})-(\d{2})$/.exec(due.trim().slice(0, 10))); explain_for (line 3164: pattern.exec(topic))
🚨
Known vulnerabilities in dependencies: 2 critical, 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// known CVEs in dependencies2 critical3 high

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

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

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

criticalvitest@2.1.0GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

high@modelcontextprotocol/sdk@1.12.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

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.
configDASH_BOTH
configDASH_JA
configPLAYWRIGHT_MODULE
configTOGAF_EAP_DASHBOARD_PORT0(空きポート自動割当) open_dashboard が listen するポート
configTOGAF_EAP_DATA_DIR~/.togaf-eap エンゲージメント状態の保存先ディレクトリ
configTOGAF_EAP_NO_BROWSERget_dashboard / open_dashboard Markdown ダッシュボード / ブラウザのライブダッシュボード( を設定するとブラウザを起動せず URL だけ返す)
// 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

84/84 tools missing one or more hints — gap_analysis (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); risk_matrix (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); stakeholder_matrix (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +81 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.

Descriptions match behaviour

6 tools describe read intent but their handlers mutate — export_archimate_open_exchange (line 1143: mkdirSync(dir, { recursive: true })); start_here (line 103: /^(\d{4})-(\d{2})-(\d{2})$/.exec(due.trim().slice(0, 10))); explain_for (line 3164: pattern.exec(topic))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

64/84 tool handlers declare input schemas (76%)

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

Tool test coverage

Only 15/84 tools referenced in tests (18%)

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

Shell command execution

2 child_process/subprocess calls in production code — runs shell commands (src/dashboard/httpServer.ts:125, pic/screenshots/capture/seed-demo.mjs:33)

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 — @modelcontextprotocol/sdk@1.12.0 (high), @modelcontextprotocol/sdk@1.12.0 (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.

Tool description accuracy

4 tools have description/behavior mismatches: export_archimate_open_exchange: description implies read-only but handler writes/deletes/executes; whats_new_for_me: description implies read-only but handler writes/deletes/executes; get_roadmap: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 9 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/waganawa-megumin-togaf10-eap-mcp-1mbmls?variant=verified)](https://m8ven.ai/mcp/waganawa-megumin-togaf10-eap-mcp-1mbmls)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: c5a805a2ccab66c595060747afe4222cebf21e51
code hash: 4507f2b9ba92459d5b867cc31cad946a230c42b9c3b914411f7bd289dae6caf6
verified: 8/14/2026, 9:57:25 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