Stock Research MCP Server (sahupra1357/StockReSearchMCP) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Limited view
71/100
2 months ago

Stock Research MCP Server

A multi-agent MCP server for comprehensive stock research and analysis using natural language queries, backed by SEC filings and real-time market data.

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

sahupra1357

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
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 9 credentials: OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, DEEPSEEK_API_KEY, GROQ_API_KEY, ALPHA_VANTAGE_API_KEY, POLYGON_API_KEY, FMP_API_KEY, NASDAQ_DATA_LINK_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.
configCHROMA_PERSIST_DIR"./chroma_db"
🔐 secretOPENAI_API_KEYexport ="your-openai-api-key"
configTICKERS_FILE
configSEC_DIR
configMAX_WORKERS"4" # Parallel downloads (default: 4)
configBATCH_SIZE"32" # Embedding batch size (default: 32)
configEMBED_MODEL
configSEC_EDGAR_COMPANY_NAME
configSEC_EDGAR_EMAIL
configSEC_TICKERS_URL
configOPENAI_MODEL
configCLAUDE_MODEL
🔐 secretANTHROPIC_API_KEY
configGOOGLE_MODEL
🔐 secretGOOGLE_API_KEY
configDEEPSEEK_MODEL
🔐 secretDEEPSEEK_API_KEY
configGROQ_MODEL
🔐 secretGROQ_API_KEY
configPYTHONHTTPSVERIFY
configOPENAI_AUDIO_MODEL
🔐 secretALPHA_VANTAGE_API_KEYapi_key = os.getenv("")
🔐 secretPOLYGON_API_KEYyour_key_here
🔐 secretFMP_API_KEY
🔐 secretNASDAQ_DATA_LINK_KEY
configTICKER_FETCH_LIMIT
configUSE_CHROMA_SECTORS"": "true",
configUSE_REAL_API"": "true",
// 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

1/1 tools missing one or more hints — analyze_sector (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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

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 4 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/sahupra1357-stockresearchmcp-1eqj8u)](https://m8ven.ai/mcp/sahupra1357-stockresearchmcp-1eqj8u)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: aa663cbea31dd440a9797e996cb992f15be65bb6
code hash: 04a730367edd72691d62f05024bf4ee4dcb7b98574aecae76e4b1217a47c1b98
verified: 6/22/2026, 12:22:58 PM
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