C
Caution
74/100
11 days ago

turbo-ea

Source Available Enterprise Architecture Management Solution

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

vincentmakes

Source: github_code

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
🚨
Secret credentials may flow to a network call
4 flows detected: SCREENSHOT_PASSWORD. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 7 credentials: SCREENSHOT_PASSWORD, TURBO_EA_PASSWORD, POSTGRES_PASSWORD, SECRET_KEY, EMAIL_OAUTH_CLIENT_SECRET, OPS_PUBLIC_KEY, TEAX_SIGNING_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.
configBASE_URL
configPLAYWRIGHT_EXECUTABLE_PATH
configSCREENSHOT_EMAIL
🔐 secretSCREENSHOT_PASSWORD
configTURBO_EA_EMAIL
configTURBO_EA_USERNAME
🔐 secretTURBO_EA_PASSWORD
configTURBO_EA_URL
configMCP_PORT
configMCP_PUBLIC_URL
configMCP_MAX_CARDS_PER_CALL
configMCP_MAX_RELATIONS_PER_CALL
configMCP_BATCH_CONFIRMATION_THRESHOLD
configMCP_OAUTH_ALLOWED_REDIRECT_URIS
configPOSTGRES_HOST2. In .env, point at your server (and update credentials):
configPOSTGRES_PORT5432 PostgreSQL port
configPOSTGRES_DBexport =turboea
configPOSTGRES_USERexport =turboea
🔐 secretPOSTGRES_PASSWORDchoose-a-strong-password>
configDB_POOL_SIZE
configDB_MAX_OVERFLOW
configDB_POOL_TIMEOUT
configMUTATION_BATCH_RETENTION_DAYS
configRESET_DBThen restart: docker compose pull && docker compose up -d. Remove from .env afterward to avoid resetting on every restart.
configSEED_DEMOtrue # Full demo: NexaTech Industries (~150 cards, BPM processes, PPM projects)
configSEED_BPMtrue # Only BPM demo data (requires SEED_DEMO to have run first)
configSEED_PPMtrue # Only PPM demo data (requires SEED_DEMO to have run first)
configSEED_SECURITY
🔐 secretSECRET_KEYyour-generated-secret>
configACCESS_TOKEN_EXPIRE_MINUTES1440 JWT token lifetime (24h default)
configPORTAL_TOKEN_EXPIRE_MINUTES
configENVIRONMENTproduction Runtime environment (development enables API docs)
configALLOWED_ORIGINSUpdate to match your domain:
configEMAIL_METHOD
configEMAIL_OAUTH_PROVIDER
configEMAIL_OAUTH_TENANT_ID
configEMAIL_OAUTH_CLIENT_ID
🔐 secretEMAIL_OAUTH_CLIENT_SECRET
configEMAIL_OAUTH_SCOPE
configEMAIL_OAUTH_TOKEN_ENDPOINT
configEMAIL_GRAPH_SENDER
configEMAIL_SERVICE_ACCOUNT_JSON
🔐 secretOPS_PUBLIC_KEY
configAI_PROVIDER_URL(empty) Ollama-compatible LLM provider URL
configAI_MODEL(empty) LLM model name (e.g., gemma3:4b)
configAI_SEARCH_PROVIDERduckduckgo Web search provider: duckduckgo, google, or searxng
configAI_SEARCH_URL(empty) Search provider URL (SearXNG URL or API_KEY:CX for Google)
configAI_AUTO_CONFIGUREfalse Auto-enable AI on startup if provider is reachable
🔐 secretTEAX_SIGNING_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deploySMTP_HOST
deploySMTP_PORT
deploySMTP_USER
deploySMTP_PASSWORD
deploySMTP_FROM
deploySMTP_TLS
// 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

47/47 tools missing one or more hints — search_cards (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_card (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_card_relations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +44 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

41/47 tool handlers declare input schemas (87%)

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

Tool handlers catch errors

Only 3/47 tool handlers wrap calls in try/catch (6%)

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

Tool test coverage

Only 0/47 tools referenced in tests (0%)

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

Shell command execution

1 child_process call — runs shell commands

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

Secrets stay with their owner

4 secret/sensitive values flow into network calls (SCREENSHOT_PASSWORD → dynamic, SCREENSHOT_PASSWORD → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not logged

10 secret values sent to console.log

Redact or omit secret values from log output.

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 8 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/vincentmakes-turbo-ea-2abn14?variant=verified)](https://m8ven.ai/mcp/vincentmakes-turbo-ea-2abn14)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 6f8e82c4921ed4fa9e19a62ad5dbea9b948bb4e5
code hash: 73fed616696b44260a6e818fb8ac511963f7f69ae9003e555a23075f1157f34f
verified: 8/8/2026, 8:30:56 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