Warning

28/100

1 day ago

first-aid-public

Item: first-aid-public
Rating: 28
Author: M8ven

→ ashen-321/first-aid-public · 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 push why connect →

Who stands behind it

ashen-321

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

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

// key findings

🚨

Secret credentials may flow to a network call

1 flow detected: openai_api_token. We can’t prove the destination matches the brand the credential belongs to.

🚨

Reads files from sensitive locations

Touches: ~/.aws/credentials, ~/.aws/credentials

🔐

You'll be asked for 19 credentials: pubmed_api_token, OPENAI_API_KEY, bedrock_api_token, tavily_api_token, anthropic_api_token, ANTHROPIC_API_KEY, PUBMED_API_KEY, TAVILY_API_KEY, GMAPS_API_KEY, gmaps_api_token, PERPLEXITY_API_KEY, openperplex_api_token, langsmith_api_token, SERPER_API_KEY, serp_api_token, google_api_key, SERPAPI_API_KEY, openai_api_token, AWS_SECRET_ACCESS_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.

configPUBMED_EMAIL

configPUBMED_TOOL

🔐 secretpubmed_api_token

🔐 secretOPENAI_API_KEY

🔐 secretbedrock_api_token

configOPENAI_BASE_URL

configbedrock_api_url

🔐 secrettavily_api_token

🔐 secretanthropic_api_token

🔐 secretANTHROPIC_API_KEY

🔐 secretPUBMED_API_KEY

🔐 secretTAVILY_API_KEY

🔐 secretGMAPS_API_KEY

🔐 secretgmaps_api_token

🔐 secretPERPLEXITY_API_KEY

🔐 secretopenperplex_api_token

🔐 secretlangsmith_api_token

configOPENAI_MODEL_NAME

🔐 secretSERPER_API_KEY

🔐 secretserp_api_token

configAWS_REGION

configAWS_DEFAULT_REGION

configAWS_PROFILE

🔐 secretgoogle_api_key

configgoogle_cse_id

🔐 secretSERPAPI_API_KEY

🔐 secretopenai_api_token

configAWS_ACCESS_KEY_ID

🔐 secretAWS_SECRET_ACCESS_KEY

// 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

18/18 tools missing one or more hints — search_pubmed (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_paper_fulltext (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); add (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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.

README present

No README found

Add a README.md describing the server and its tools.

License file

No license file

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

Tool test coverage

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

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

No access to sensitive paths

Reads sensitive paths: ~/.aws/credentials, ~/.aws/credentials

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Shell command execution

6 child_process/subprocess calls in production code — runs shell commands (backend/mcp/mcp_client.py:103, backend/tools.py:120, backend/tools.py:170)

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

Secrets not written to files

4 secret values written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Secrets not logged

6 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 9 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/ashen-321-first-aid-public-1nwzc4?variant=verified)](https://m8ven.ai/mcp/ashen-321-first-aid-public-1nwzc4)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: 3c8e3e7fd5a91126e2465ae054f4939258129a76

code hash: 175283f7616a9540dd02a251cfe6a5686d146c3abc3bbf7acfc3aba7998559a2

verified: 8/18/2026, 3:54:42 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