PlanExe (planexeorg/planexe) is an MCP server listed on the M8ven Trust Index. It scores 75 out of 100, grade B. It declares 2 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Limited view
75/100
1 month ago

PlanExe

Create a plan from a description in minutes. The generated plan contains: Gantt, executive summary, pitch, risk analysis and financial strategies. Audience: decision-makers. Obtain an API key from: [home.planexe.org](https://home.planexe.org/) This is what a a report looks like. - [Minecraft-themed escape room](https://planexe.org/20251016_minecraft_escape_report.html). - See more [examples plans here](https://planexe.org/examples/).

→ planexeorg/planexe· 5 installs· listed on smithery

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

planexeorg

Source: Smithery · also listed on Glama, mcp.so

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

SmitheryGlamamcp.so

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 14 credentials: PLANEXE_POSTGRES_PASSWORD, PLANEXE_DATABASE_WORKER_API_KEY, PLANEXE_FRONTEND_MULTIUSER_SECRET_KEY, PLANEXE_OAUTH_GOOGLE_CLIENT_SECRET, PLANEXE_OAUTH_GITHUB_CLIENT_SECRET, PLANEXE_OAUTH_DISCORD_CLIENT_SECRET, PLANEXE_API_KEY_SECRET, PLANEXE_STRIPE_SECRET_KEY, PLANEXE_TELEGRAM_BOT_TOKEN, PLANEXE_MCP_API_KEY, PLANEXE_MCP_REQUIRE_USER_KEY, OPENROUTER_API_KEY, PLANEXE_STRIPE_WEBHOOK_SECRET, ANTHROPIC_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.
configPLANEXE_POSTGRES_HOST
configPLANEXE_POSTGRES_PORT
configPLANEXE_POSTGRES_DB
configPLANEXE_POSTGRES_USER
🔐 secretPLANEXE_POSTGRES_PASSWORD
🔐 secretPLANEXE_DATABASE_WORKER_API_KEY
configPLANEXE_DATABASE_WORKER_PORT
configPLANEXE_LOG_LEVEL
configPLANEXE_CONFIG_PATH
configPLANEXE_WORKER_RELAY_PROCESS_OUTPUT
configPLANEXE_PURGE_ENABLED
configPLANEXE_PURGE_MAX_AGE_HOURS
configPLANEXE_PURGE_INTERVAL_SECONDS
configPLANEXE_PURGE_RUN_PREFIX
configPLANEXE_WORKER_HOST
configPLANEXE_WORKER_PORT
configPLANEXE_WORKER_ID
configPLANEXE_CREDIT_PRICE_CENTS
configPLANEXE_SUCCESS_PLAN_FEE_USD
configPLANEXE_WORKER_PLAN_URL
configPLANEXE_MODEL_PROFILE
🔐 secretPLANEXE_FRONTEND_MULTIUSER_SECRET_KEY
configPLANEXE_FRONTEND_MULTIUSER_PUBLIC_URL
configFLASK_ENV
configPLANEXE_API_KEY_SHOW_ONCE
configWERKZEUG_RUN_MAIN
configFLASK_DEBUG
configPLANEXE_OAUTH_GOOGLE_CLIENT_ID
🔐 secretPLANEXE_OAUTH_GOOGLE_CLIENT_SECRET
configPLANEXE_OAUTH_GITHUB_CLIENT_ID
🔐 secretPLANEXE_OAUTH_GITHUB_CLIENT_SECRET
configPLANEXE_OAUTH_DISCORD_CLIENT_ID
🔐 secretPLANEXE_OAUTH_DISCORD_CLIENT_SECRET
configPLANEXE_AUTH_REQUIRED
configPLANEXE_GOOGLE_ANALYTICS
🔐 secretPLANEXE_API_KEY_SECRET
🔐 secretPLANEXE_STRIPE_SECRET_KEY
🔐 secretPLANEXE_TELEGRAM_BOT_TOKEN
configPLANEXE_FRONTEND_MULTIUSER_DEBUG
configPLANEXE_FRONTEND_MULTIUSER_HOST
configPLANEXE_FRONTEND_MULTIUSER_PORT
configPLANEXE_DEBUG_STARTUP
🔐 secretPLANEXE_MCP_API_KEY
configPLANEXE_MCP_HTTP_HOST
configPLANEXE_MCP_HTTP_PORT
configPLANEXE_MCP_MAX_BODY_BYTES
configPLANEXE_MCP_RATE_LIMIT
configPLANEXE_MCP_RATE_WINDOW_SECONDS
configPLANEXE_MCP_DOWNLOAD_RATE_LIMIT
configPLANEXE_MCP_DOWNLOAD_RATE_WINDOW_SECONDS
configPLANEXE_MCP_CORS_ORIGINS
configPLANEXE_DEDUP_WINDOW_SECONDS
configSQLALCHEMY_DATABASE_URI
configPLANEXE_MCP_PUBLIC_BASE_URL
configPLANEXE_DOWNLOAD_TOKEN_TTL
🔐 secretPLANEXE_MCP_REQUIRE_USER_KEY
configPLANEXE_SSE_POLL_INTERVAL
configPLANEXE_SSE_HEARTBEAT_INTERVAL
configPLANEXE_SSE_MAX_DURATION
configPLANEXE_SSE_MAX_CONNECTIONS
configPLANEXE_SSE_MAX_TOTAL_CONNECTIONS
configPLANEXE_FRONTEND_MULTIUSER_ADMIN_USERNAME
🔐 secretOPENROUTER_API_KEY
configPLANEXE_DATABASE_WORKER_URL
configPLANEXE_TELEGRAM_LOGIN_URL
configPLANEXE_STRIPE_CURRENCY
🔐 secretPLANEXE_STRIPE_WEBHOOK_SECRET
configPLANEXE_TELEGRAM_STARS_PER_CREDIT
configPLANEXE_MIN_CREDITS_TO_CREATE_PLAN
🔐 secretANTHROPIC_API_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

2/2 tools missing one or more hints — handle_call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_67 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 3 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/planexeorg/planexe)](https://m8ven.ai/mcp/planexeorg/planexe)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 846f61200594597c003a1bc45029dc104d9e7749
code hash: 85d8bb728640e7cc763b0c0aa749a4bf09b1b251e4911e528aaeef44a7455b35
verified: 8/7/2026, 2:03:51 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