Back to MCP Trust Indexm8ven
F
Warning
32/100
2 days ago

openInvest

Research-grade investment decision engine for AI agents: isolated multi-agent committee, auditable verdicts, backtests with lookahead protection, published negative results

→ longsizhuo/openInvest· listed on github_code

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

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

longsizhuo

Source: github_code · also listed on 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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHubGlama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: INVEST_API_TOKEN, CHATBOT_INTERNAL_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 8 credentials: INVEST_API_TOKEN, EMAIL_PASSWORD, DEEPSEEK_API_KEY, CF_ACCESS_CLIENT_SECRET, GITHUB_TOKEN, CHATBOT_INTERNAL_KEY, OPENAI_API_KEY, LLM_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.
🔐 secretINVEST_API_TOKEN
configINVEST_MCP_ALLOWED_HOSTS
configINVEST_MCP_HOST
configINVEST_MCP_PORT
configINVEST_WEB_HOST
configINVEST_WEB_PORT
configINVEST_MAX_DEBATE_ROUNDS
configBACKTEST_WORKERS
configINVEST_CIO_CONFIDENCE_CAP
configINVEST_ALLOC_AGGRESSIVENESS
configEMAIL_SENDER
🔐 secretEMAIL_PASSWORD
configINVEST_API_BASE
🔐 secretDEEPSEEK_API_KEY
configINVEST_HOME~/openInvest uvx openinvest status
configCF_ACCESS_CLIENT_ID
🔐 secretCF_ACCESS_CLIENT_SECRET
configINVEST_VOL_TARGET
configRUN_TAG
configINVEST_TA_OUT
configINVEST_TA_DATES
configINVEST_SECOND_OPINION_CLI
configINVEST_EVENT_API_URL
configINVEST_EVENT_DRY_RUN
configINVEST_PNL_AUTOPUSH
🔐 secretGITHUB_TOKEN
configINVEST_PNL_PUSH_BRANCH
configINVEST_SENTINEL_DRY_RUN
configCHATBOT_ALERT_URL
🔐 secretCHATBOT_INTERNAL_KEY
configINVEST_EMBEDDING_PROVIDER
🔐 secretOPENAI_API_KEY
configINVEST_OPENAI_EMBEDDING_MODEL
configINVEST_API_BASE_URL
configDIGEST_EMAIL_TO
🔐 secretLLM_API_KEY
// quality suggestions

Tool annotations

5/21 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

21/21 tools missing one or more hints — status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); strategy (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); history (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +18 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.

Secrets stay with their owner

2 secret/sensitive values flow into network calls (INVEST_API_TOKEN → dynamic, CHATBOT_INTERNAL_KEY → dynamic)

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

Secrets never reach shell commands

1 secret value passed to shell commands — possible command injection

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

Secrets not logged

3 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 5 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/longsizhuo-openinvest-4fgp1w?variant=verified)](https://m8ven.ai/mcp/longsizhuo-openinvest-4fgp1w)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e2b68f3e745c849f7a544cd12d1a329caca0fab2
code hash: f39aec7ebd9052dcfb3873fc985bff3a131308a0be63adb95393c761f5613289
verified: 8/17/2026, 7:29:58 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