Back to MCP Trust Indexm8ven
C
Limited view
67/100
1 month ago

pilldoc-user-mcp

Provides tools for managing pharmacy accounts, user information, and campaigns via a local MCP server that interfaces with the EDB API.

→ hjsh200219/pilldoc-user-mcp· 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

hjsh200219

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 3 credentials: EDB_PASSWORD, EDB_TOKEN, POSTGRES_PASSWORD
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.
configEDB_TIMEOUT
configEDB_LOGIN_URL(개발: https://dev-adminapi.edbintra.co.kr/v1/auth/login, 실서버: https://webconsole-api.edbintra.co.kr/v1/auth/login)
configEDB_USER_ID, EDB_PASSWORD (로그인 시 기본값)
🔐 secretEDB_PASSWORDEDB_USER_ID, (로그인 시 기본값)
configEDB_FORCE_LOGIN(true/false)
configEDB_ACCEPT
configMCP_ON_DEMAND
🔐 secretEDB_TOKEN
configEDB_BASE_URL(개발: https://dev-adminapi.edbintra.co.kr, 실서버: https://webconsole-api.edbintra.co.kr)
configPOSTGRES_HOST
configPOSTGRES_PORT
configPOSTGRES_USER
🔐 secretPOSTGRES_PASSWORD
configPOSTGRES_DB
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// 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

35/35 tools missing one or more hints — get_server_metrics (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); reset_server_metrics (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); health_check (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +32 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 inputs are validated

26/35 tool handlers declare input schemas (74%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

23/35 tool handlers wrap calls in try/catch (66%)

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

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 6 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/hjsh200219-pilldoc-user-mcp-1cqtux)](https://m8ven.ai/mcp/hjsh200219-pilldoc-user-mcp-1cqtux)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: c0d9b3198f060cbe0a71b72577c8e59a88a37de8
code hash: 4654d4efc798a03abba6e0b594e726e98847abb2f29a7c68026d56c41d137978
verified: 6/22/2026, 12:10:33 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