Warden Magento MCP Server (seandearnaley/mcp-warden-magento-ts) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 16 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
54/100

Warden Magento MCP Server

A Model Context Protocol (MCP) server that provides AI assistants with safe, structured access to Magento 2 operations within Warden environments.

→ seandearnaley/mcp-warden-magento-ts· 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

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

seandearnaley

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, 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// tools this server exposes16 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

magento.cacheClean

Runs bin/magento cache:clean [types?] inside php-fpm

magento.cacheFlush

Runs bin/magento cache:flush [types?] inside php-fpm

magento.setupUpgrade

Runs bin/magento setup:upgrade then cache:clean

magento.diCompile

Runs bin/magento setup:di:compile

magento.staticDeploy

Runs bin/magento setup:static-content:deploy [options]

magento.indexerReindex

Runs bin/magento indexer:reindex

magento.modeShow

Shows Magento deploy mode

magento.modeSet

Sets Magento deploy mode (developer|production)

magento.configSet

Sets a Magento config value: bin/magento config:set <path> <value>

magento.configShow

Shows a Magento config value: bin/magento config:show <path>

warden.exec

Run a command in a specific container (php-fpm, php-debug, varnish, redis, etc.)

warden.varnishFlush

Varnish ban all: varnishadm 'ban req.url ~ .'

warden.redisFlushAll

Redis flushall (USE WITH CAUTION)

warden.logsTail

Tail last N lines of logs for given services (no follow)

warden.showEnv

Read and return sanitized .env for a Warden project

warden.projectInfo

Show information about the current Warden project

// known CVEs in dependencies1 critical3 high

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

criticalvitest@3.2.4GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.17.4GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

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.
configLOG_DIRCustom log directory (defaults to ./logs)
configLOG_TO_FILEWhen NODE_ENV=production or =true:
configMCP_STDIO_MODEWhen true, disables console logging to protect MCP stdio transport
// quality suggestions

Dependencies

18 dependencies, 1 flagged: @playwright/test

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

16/16 tools missing one or more hints — magento.cacheClean (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); magento.cacheFlush (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); magento.setupUpgrade (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +13 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

8/16 tool handlers declare input schemas (50%)

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

Tool handlers catch errors

Only 1/16 tool handlers wrap calls in try/catch (6%)

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

Tool test coverage

12/16 tools referenced in tests (75%)

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

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.17.4 (high), @modelcontextprotocol/sdk@1.17.4 (high)

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

Dev dependencies

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

Upgrade dev dependencies when convenient.

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 7 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/seandearnaley/mcp-warden-magento-ts?variant=verified)](https://m8ven.ai/mcp/seandearnaley/mcp-warden-magento-ts)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 8efc4175edabd09448a48af42092f119c3a1ca96
code hash: 954f9bc544cc7815f72465967675cd6d5160ac4d8bc6f8727d9467d178751766
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