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

C
Caution
74/100

polyplan-mcp

Enables structured multi-model AI planning sessions across multiple CLI coding tools, orchestrating independent planning, peer review, and final synthesis.

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

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

IMAFDI

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 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
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.
// tools this server exposes18 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

init

Initialize PolyPlan in this project — creates .plans/ and .polyplan/ directories

round_1

Start Round 1 — create an independent plan for this model/CLI (no other models seen)

round_1_context

Get the Round 1 prompt — call this first, then generate your plan, then call round_1 to save

round_2

Start Round 2 — peer-review all Round 1 plans and write a revised master plan (requires ≥2 Round 1 plans)

round_2_context

Get the Round 2 prompt with all other models' Round 1 plans injected — call this before generating your Round 2 plan

final_plan

Start Final round — synthesize ALL Round 1 + Round 2 plans into one implementable plan (requires ≥1 Round 2 plan)

final_plan_context

Get the Final round prompt with ALL Round 1 + Round 2 plans injected — call this before generating the final plan

show_status

Show full session state — which models completed each round, open questions, and conflicts

clear_plans

Delete ALL plan files across all rounds. Must set confirm=true.

clear_round_1

Delete only Round 1 plan files — leaves Round 2 and Final intact. Must set confirm=true.

clear_round_2

Delete only Round 2 plan files — leaves Round 1 and Final intact. Must set confirm=true.

show_conflicts

Show all points where models disagreed in Round 1 — technology choices, approach, and assumption conflicts

show_questions

Show all open questions raised by any model in Round 1, and whether other models answered them

show_diff

Show what changed for a specific model between their Round 1 and Round 2 plans

show_agree

Show what ALL models agreed on independently in Round 1 — highest-confidence decisions

show_summary

One-paragraph summary of each model's plan — quick overview of all positions

export_plans

Bundle the entire .plans/ session into one readable markdown file for sharing or archiving

show_history

Full audit log — which model, which CLI tool, which round, what time, what action

// known CVEs in dependencies1 high1 low

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

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

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

lowzod@3.22.0GHSA-m95q-7qp3-xv42

Zod denial of service vulnerability

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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

18/18 tools missing one or more hints — init (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); round_1 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); round_1_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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

16/18 tool handlers declare input schemas (89%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.0.0 (high), zod@3.22.0 (low)

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

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/imafdi/polyplan-mcp?variant=verified)](https://m8ven.ai/mcp/imafdi/polyplan-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 02ed3d5701d58a3cd6eb8ae7bae5b0f4158d82b5
code hash: 0f34303c226bcdd5509bacf06642af5b4c0f1b03ebd2c9f2e84dbed8979e8a34
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