CharmHealth MCP Server (CharmHealth/charm-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 73 out of 100, grade C. It declares 18 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
73/100

CharmHealth MCP Server

An MCP server for CharmHealth EHR that allows LLMs and MCP clients to interact with patient records, encounters, and practice information.

→ CharmHealth/charm-mcp-server· listed on glama

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

CharmHealth

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

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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: CHARMHEALTH_API_KEY, CHARMHEALTH_REFRESH_TOKEN, CHARMHEALTH_CLIENT_SECRET
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.
configENVEnvironment mode (dev/prod) No
configMCPSERVER_HOST
configMCPSERVER_PORT
configCHARMHEALTH_BASE_URLyour_base_uri_here
🔐 secretCHARMHEALTH_API_KEYyour_api_key_here
🔐 secretCHARMHEALTH_REFRESH_TOKENyour_refresh_token_here
configCHARMHEALTH_CLIENT_IDyour_client_id_here
🔐 secretCHARMHEALTH_CLIENT_SECRETyour_client_secret_here
configCHARMHEALTH_REDIRECT_URIyour_redirect_uri_here
configCHARMHEALTH_TOKEN_URLyour_token_url_here
configENABLE_PROMETHEUS
configPROMETHEUS_MULTIPROC_DIR
configOTEL_EXPORTER_OTLP_ENDPOINT
configMCP_OTEL_ENABLED
configCOLLECT_METRICSAvoid sending PHI to logs or telemetry. Keep =false unless your telemetry backend is HIPAA-compliant and covered by a BAA.
// 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 — managePatientBilling (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); managePatientVitals (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); managePatientDrugs (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.

Tool handlers catch errors

17/18 tool handlers wrap calls in try/catch (94%)

Wrap each tool handler body in try/catch and return a structured error response.

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/charmhealth/charm-mcp-server)](https://m8ven.ai/mcp/charmhealth/charm-mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 14595f5b9e9f2493baab94731f245c9d1c3f960d
code hash: c1bcf3d6c22eab48fcc0850c82b00ae394cde9074a794fe7ed9467186cd91f90
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