morning-brief-mcp (Mars-0310/morning-brief-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
10 days ago

morning-brief-mcp

Deterministic A-share morning brief service exposing MCP tools to generate full market briefs, filtered news events, previous close context, and news coverage without external LLM keys.

→ Mars-0310/morning-brief-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

Mars-0310

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glama

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 2 credentials: HITHINK_FINANCE_API_KEY, HITHINK_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.
configDOMESTIC_TIMEOUT_SECONDS
configDOMESTIC_MAX_RETRIES
configDOMESTIC_MAX_PAGES分页均受 与 DOMESTIC_MAX_ITEMS 限制。每个 provider
configDOMESTIC_MAX_ITEMS分页均受 DOMESTIC_MAX_PAGES 与 限制。每个 provider
configDOMESTIC_BACKOFF_BASE_SECONDS
configDOMESTIC_MAX_BACKOFF_SECONDS
configDOMESTIC_BACKOFF_JITTER_SECONDS
configEASTMONEY_MIN_REQUEST_INTERVAL_SECONDS
configGDELT_TIMEOUT_SECONDS
configGDELT_MAX_RECORDS_PER_QUERY
configGDELT_OFFICIAL_MAX_RECORDS
configGDELT_MAX_RETRIES
configGDELT_MIN_REQUEST_INTERVAL_SECONDS
configGDELT_BACKOFF_BASE_SECONDS
configGDELT_MAX_BACKOFF_SECONDS
configGDELT_BACKOFF_JITTER_SECONDS
configGDELT_USER_AGENT
🔐 secretHITHINK_FINANCE_API_KEY（用于交易日历和上一交易日市场背景）
🔐 secretHITHINK_API_KEY
configHITHINK_TIMEOUT_SECONDS
configHITHINK_MARKET_DUMP_TIMEOUT_SECONDS
// 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

4/4 tools missing one or more hints — generate_morning_brief (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_morning_news (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_previous_close_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 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.

License file

No license file

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

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/mars-0310-morning-brief-mcp-14xkd3)](https://m8ven.ai/mcp/mars-0310-morning-brief-mcp-14xkd3)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 244b0b9f327127517c4f46f64055b280aaae4af8
code hash: 6de880dd32d3a786edf04540cd48f5847aa246077a97c5564ae770fa5a7b8520
verified: 8/17/2026, 7:32:37 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