medusa-mcp (mneema/ai-medusa-mcp-server-integration) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
66/100

medusa-mcp

MCP server for integrating AI agents and automation with Medusa commerce platforms, enabling management of products, orders, and workflows through a scalable backend layer.

→ mneema/ai-medusa-mcp-server-integration· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

mneema

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
🚨
Known vulnerabilities in dependencies: 1 critical, 5 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: MEDUSA_PASSWORD, PUBLISHABLE_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical5 high5 medium2 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

critical@mikro-orm/core@6.4.11GHSA-gwhv-j974-6fxm

MikroORM is vulnerable to SQL Injection via specially crafted object

high@modelcontextprotocol/sdk@1.8.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.8.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

high@mikro-orm/core@6.4.11GHSA-qpfv-44f3-qqx6

MikroORM has Prototype Pollution in Utils.merge

highvite@6.2.5GHSA-fx2h-pf6j-xcff

vite: `server.fs.deny` bypass on Windows alternate paths

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configMEDUSA_BACKEND_URLYour Medusa backend URL
🔐 secretMEDUSA_PASSWORDMedusa admin password (for admin)
configMEDUSA_USERNAMEMedusa admin username (for admin)
🔐 secretPUBLISHABLE_KEYYour Medusa publishable API key
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_MEDUSA_PUBLISHABLE_KEY
deployPORT
// quality suggestions

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

1 secret value sent to log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 2 high severity in production deps — @modelcontextprotocol/sdk@1.8.0 (high), @modelcontextprotocol/sdk@1.8.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

4 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Domain consistency

npm scope @sgftech doesn't match GitHub owner mneema

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 5 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/mneema/ai-medusa-mcp-server-integration?variant=verified)](https://m8ven.ai/mcp/mneema/ai-medusa-mcp-server-integration)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: c2f65aa47aeaa7aba6a4c620aac05a62d366a2a3
code hash: 08227f5e86e3f04913ad14b3b3687a9ec2fd27faadd0363b2cf56be178592419
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