io.github.MAIAS-project/maias
NPM · @MAIAS/MCP
Validate, query, safely edit, and wireframe MAIAS app-IA documents: cascading renames, atomic edits.
Available components
Last scanned (5 hours ago)
Scores higher than 58% of npm servers
Category Developer Tools
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 102 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 866 tokens (~173/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 5 Nov 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.
- 3 Nov 26 −2
- Stability: pass → 0.87 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
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 5 Nov 2026 · Analysed npm/@maias/mcp@0.5.1
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| 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 →
edit Safely edit a MAIAS document ~186
Reference-safe edits: rename_screen cascades to flows, the navigation registry, and every target; add_screen registers the screen; remove_screen refuses to leave dangling references unless cascade is set. Writes the result back to the file (canonically formatted when format_output is true).
| Name | Type | Req | Description |
|---|---|---|---|
| cascade | boolean | – | remove_screen: also remove inbound references |
| file | string | yes | Path to the MAIAS document |
| flow | string | – | Flow to append the new screen to (add_screen) |
| format_output | boolean | – | Write canonical form (default true) |
| new_id | string | – | New id (rename_screen) |
| operation | string | yes | – |
| registry | string | – | Registry list for add_screen (default secondary) |
| screen | object | – | Screen object per the spec (add_screen) |
| screen_id | string | – | Target screen id (rename_screen / remove_screen) |
No output schema declared.
No examples provided.
edit_elements Safely edit a screen's elements ~233
Batch edit of a screen's `elements` list (or a declared state's list): insert, update, remove, move. The batch is atomic — a failing op refuses the whole batch and the file is untouched. Ops apply sequentially, so each op's index addresses the list as left by the previous ops (0-based; insert at list length appends; move's `to` is the final index). `update.set` patches only the given keys — an explicit null deletes a key, `x_` fields not named survive. An op introducing a `target` that matches no screen is refused, as is editing a state the screen does not declare. Pass `expect` so a stale index fails loudly instead of editing the wrong element. Writes the result back to the file (canonically formatted when format_output is true).
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Path to the MAIAS document |
| format_output | boolean | – | Write canonical form (default true) |
| ops | array | yes | Operations, applied in order, all-or-nothing |
| screen_id | string | yes | Screen whose elements are edited |
No output schema declared.
No examples provided.
query Query a MAIAS document graph ~178
Graph utilities over a MAIAS file: get one screen, list screens/flows, reachability analysis, orphan detection, "what links here" for a screen id, a text outline of the structure (tree — show this to the user after creating or restructuring a document), and a Mermaid flowchart (mermaid — renders in GitHub/Claude/Obsidian). tree and mermaid return plain text, not JSON; mermaid accepts an optional flow to scope the diagram.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Path to the MAIAS document |
| flow | string | – | mermaid: scope the diagram to one flow |
| operation | string | yes | – |
| refs | boolean | – | tree: append each screen's outbound targets and states |
| screen_id | string | – | Screen id — required for 'screen' and 'what_links_here' |
No output schema declared.
No examples provided.
validate Validate a MAIAS document ~63
JSON Schema validation plus semantic lint (dangling targets, orphans, registry membership, …) for a MAIAS file. Returns { valid, diagnostics[] } with line/col positions.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Path to a .yaml or .json MAIAS document |
No output schema declared.
No examples provided.
wireframe Render an HTML wireframe board ~206
Deterministic mobile wireframes from a MAIAS file: one self-contained HTML file (inline CSS, no JS, no external URLs) with one phone frame per screen, flows as rows, and click-through anchors between frames. Pass out to write the file (recommended — returns a summary); without out the raw HTML is returned as text (large). Refuses documents with validation errors (dangling targets become dead links) unless force is set.
| Name | Type | Req | Description |
|---|---|---|---|
| accent | string | – | Hex accent colour (e.g. #0A84FF) replacing the default wireframe grey |
| file | string | yes | Path to the MAIAS document |
| flow | string | – | Render only this flow |
| force | boolean | – | Render despite validation errors |
| out | string | – | Write the HTML here (e.g. <app>-wireframes.html); when absent the HTML is returned as text |
| states | boolean | – | Also emit declared empty/loading/error variants as extra frames |
No output schema declared.
No examples provided.
How do I install the io.github.MAIAS-project/maias MCP server?
io.github.MAIAS-project/maias runs locally as an npm package, launched with npx -y @maias/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 · @maias/mcp
claude mcp add maias-project-maias -- npx -y @maias/mcp
What is the io.github.MAIAS-project/maias MCP server?
io.github.MAIAS-project/maias is an MCP server listed in the public MCP registry as io.github.MAIAS-project/maias. Validate, query, safely edit, and wireframe MAIAS app-IA documents: cascading renames, atomic edits. This page covers its npm package (@maias/mcp).
Is the io.github.MAIAS-project/maias MCP server safe to use?
io.github.MAIAS-project/maias scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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.MAIAS-project/maias MCP server expose?
io.github.MAIAS-project/maias exposes 5 tools: validate, query, edit, edit_elements, wireframe. Their descriptions and schemas cost roughly 866 tokens of context every time the server is loaded.
Is the io.github.MAIAS-project/maias MCP server still maintained?
io.github.MAIAS-project/maias is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.MAIAS-project/maias MCP server under?
io.github.MAIAS-project/maias declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.