io.github.MobileReality/mdma
NPM · @MOBILE-REALITY/MDMA-MCP · SCANNED SEP 24
MCP server for MDMA — exposes spec, prompts, docs, and package metadata to AI assistants.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 64 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 482 tokens (~68/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.MobileReality/mdma MCP server?
io.github.MobileReality/mdma runs locally as an npm package, launched with npx -y @mobile-reality/mdma-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mobile-reality/mdma-mcp
claude mcp add mobilereality-mdma -- npx -y @mobile-reality/mdma-mcp
{
"mcpServers": {
"mobilereality-mdma": {
"command": "npx",
"args": [
"-y",
"@mobile-reality/mdma-mcp"
]
}
}
} {
"servers": {
"mobilereality-mdma": {
"command": "npx",
"args": [
"-y",
"@mobile-reality/mdma-mcp"
]
}
}
} codex mcp add mobilereality-mdma -- npx -y @mobile-reality/mdma-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mobilereality-mdma": {
"type": "local",
"command": [
"npx",
"-y",
"@mobile-reality/mdma-mcp"
],
"enabled": true
}
}
} openclaw mcp add mobilereality-mdma --command npx --arg -y --arg @mobile-reality/mdma-mcp
mcp_servers:
mobilereality-mdma:
command: "npx"
args: ["-y", "@mobile-reality/mdma-mcp"] {
"McpServers": {
"mobilereality-mdma": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mobile-reality/mdma-mcp"
]
}
}
} assistant mcp add mobilereality-mdma -t stdio -c npx -a -y @mobile-reality/mdma-mcp
{
"mcpServers": {
"mobilereality-mdma": {
"command": "npx",
"args": [
"-y",
"@mobile-reality/mdma-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 −3
- Stability: pass → 0.83 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/@mobile-reality/mdma-mcp@0.2.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build-system-prompt ~142
Generates a custom MDMA prompt from structured input (domain, components, fields, steps). Returns only the custom prompt part — use buildSystemPrompt({ customPrompt }) in code to combine it with the base MDMA spec.
| Name | Type | Req | Description |
|---|---|---|---|
| businessRules | string | – | Business rules or constraints |
| components | array | – | Component types to use (e.g. ["form", "approval-gate", "webhook"]) |
| domain | string | – | Domain context (e.g. "HR onboarding", "expense approval") |
| fields | array | – | Form field definitions |
| steps | array | – | Multi-step flow definitions — each step becomes a separate conversation turn |
No output schema declared.
No examples provided.
get-doc ~136
Fetches the latest version of an MDMA documentation file from the public GitHub repo (raw.githubusercontent.com/MobileReality/mdma) and returns its contents as text. Allowed paths: any entry from list-docs, plus any *.md file under "docs/" or "blueprints/". Defaults to the "main" branch.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Repo-relative path to the doc, e.g. "docs/getting-started/quick-start.md" or "blueprints/kyc-case/README.md" |
| ref | string | – | Git ref (branch, tag, or commit SHA). Defaults to "main". |
No output schema declared.
No examples provided.
get-prompt ~55
Returns a named MDMA prompt (mdma-author, mdma-reviewer, or mdma-fixer)
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Prompt name: mdma-author, mdma-reviewer, or mdma-fixer |
No output schema declared.
No examples provided.
get-spec ~32
Returns the full MDMA specification: component types, schemas (as JSON Schema), binding syntax, and authoring rules
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-docs ~46
Returns the catalog of MDMA documentation files available for fetching from the public GitHub repo (path, title, description). Use this to discover what docs you can pass to get-doc.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-packages ~28
Returns all MDMA npm packages with their purpose, install command, usage example, and category
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
validate-prompt ~43
Validates a custom prompt against MDMA conventions. Returns warnings for anti-patterns and suggestions for improvements.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | The custom prompt text to validate |
No output schema declared.
No examples provided.
What is the io.github.MobileReality/mdma MCP server?
io.github.MobileReality/mdma is an MCP server listed in the public MCP registry as io.github.MobileReality/mdma. MCP server for MDMA, exposes spec, prompts, docs, and package metadata to AI assistants. This page covers its npm package (@mobile-reality/mdma-mcp).
Is the io.github.MobileReality/mdma MCP server safe to use?
io.github.MobileReality/mdma scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.MobileReality/mdma MCP server expose?
io.github.MobileReality/mdma exposes 7 tools: get-spec, get-prompt, build-system-prompt, validate-prompt, list-packages, and 2 more. Their descriptions and schemas cost roughly 482 tokens of context every time the server is loaded.
Is the io.github.MobileReality/mdma MCP server still maintained?
io.github.MobileReality/mdma is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.