npm:@mobile-reality/mdma-mcp

Item: npm:@mobile-reality/mdma-mcp
Rating: 55
Author: wmcp.sh

https://www.npmjs.com/package/@mobile-reality/mdma-mcp

55/100 · MCP Trust Grade · checked 5h ago · MCP 0.2.10

What it offers — 8 tools · Developer Tools

get-spec

Returns the full MDMA specification: component types, schemas (as JSON Schema), binding syntax, and authoring rules

get-prompt

Returns a named MDMA prompt (mdma-author, mdma-reviewer, or mdma-fixer). For mdma-author, pass an optional variantId (e.g.

list-prompt-variants

Returns all available MDMA_AUTHOR prompt variants with their id, label, and description. Pass the id to get-prompt as variantId to retrieve the model-

build-system-prompt

Generates a custom MDMA prompt from structured input (domain, components, fields, steps). Returns only the custom prompt part — use buildSystemPrompt(

validate-prompt

Validates a custom prompt against MDMA conventions. Returns warnings for anti-patterns and suggestions for improvements.

list-packages

Returns all MDMA npm packages with their purpose, install command, usage example, and category

list-docs

Returns the catalog of MDMA documentation files available for fetching from the public GitHub repo (path, title, description). Use this to discover wh

get-doc

Fetches the latest version of an MDMA documentation file from the public GitHub repo (raw.githubusercontent.com/MobileReality/mdma) and returns its co

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 8 tool(s) detected in source

Security (OWASP MCP)30%15

⚠ prompt-injection / hidden-instruction markup in source
scanned 6 source files

Maintenance / popularity20%100

published within 90 days
10 published versions

Tool hygiene15%70

no TypeScript types
4 runtime deps

Transparency / provenance15%65

✓ public repository linked
no license declared

Findings

FAILMCP01 Prompt-injection / hidden-instruction markup found in package source.

INFO Static analysis of npm package @mobile-reality/mdma-mcp@0.2.10 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:@mobile-reality/mdma-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:@mobile-reality/mdma-mcp grade F

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3A%40mobile-reality%2Fmdma-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade F](https://wmcp.sh/mcp/grade/npm%3A%40mobile-reality%2Fmdma-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40mobile-reality%2Fmdma-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3A%40mobile-reality%2Fmdma-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3A%40mobile-reality%2Fmdma-mcp/badge.svg" alt="MCP Trust Grade F · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.