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

medical-evidence-assistant

Provides medical evidence tools including PubMed search, citation verification, clinical trial lookup, drug information, drug interaction checking, PICO extraction, and medical entity recognition via MCP.

→ menessss/medical-evidence-assistant· 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

menessss

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.
✅
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 3 credentials: OPENAI_API_KEY, COHERE_API_KEY, ALI_BAILIAN_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.
🔐 secretOPENAI_API_KEY"env": { "": "sk-xxxx", "OPENAI_BASE_URL": "https://api.deepseek.com" }
configOPENAI_BASE_URL"env": { "OPENAI_API_KEY": "sk-xxxx", "": "https://api.deepseek.com" }
configOPENAI_LLM_MODELdeepseek-chat
configSEMANTIC_COLLECTION_NAME
configCLOUD_DB_PATH
configEMBEDDING_DIM
configEMBEDDING_MODEL
configEMBEDDING_MODEL_PATH
configEMBED_BATCH_SIZE
configEMBED_MAX_LENGTH
configDEEPSEEK_REASONER_MODEL
configCHROMA_DB_PATH
configCHROMA_COLLECTION_NAME
configCHUNK_TARGET_TOKENS
configCHUNK_OVERLAP_TOKENS
configEMBEDDING_PROVIDER
configOPENAI_EMBEDDING_MODEL
configRETRIEVE_TOP_K_DENSE
configRETRIEVE_TOP_K_SPARSE
configRETRIEVE_TOP_K_RRF
configRETRIEVE_TOP_K_RERANK
🔐 secretCOHERE_API_KEY
configCOHERE_RERANK_MODEL
🔐 secretALI_BAILIAN_API_KEY
configALI_BAILIAN_BASE_URL
configALI_BAILIAN_VL_MODEL
// 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

8/8 tools missing one or more hints — search_pubmed_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); verify_citation_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_trial_record_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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 test coverage

Only 0/8 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/subprocess call in production code — runs shell commands (embeddings.py:116)

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

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/menessss-medical-evidence-assistant-dr6ljp)](https://m8ven.ai/mcp/menessss-medical-evidence-assistant-dr6ljp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ce0b9b819e29f76d8a6e9ad87355f9fe6115f073
code hash: ae2015ca1d5e63056849b3d11180ef26e8d5e9df61c9dc49c98b8df82247a504
verified: 8/14/2026, 9:51:03 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