M00N Report
NPM · @M00NSOLUTIONS/MCP-SERVER
Test management over MCP: author cases, run manual executions, cut releases, read health
Available components
Last scanned (11 hours ago)
Scores higher than 65% of npm servers
Category Testing and QA
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
- 33 of 106 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 (MIT).Pass
- Actively maintained (last published 73 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 17601 tokens (~314/item across 56 items; 55 tools + 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% 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
- All 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 57 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
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.93 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 +3
- 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/@m00nsolutions/mcp-server@1.5.3
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 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 33 |
| 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 →
update_execution ~286
Update a Manual Test Execution's own fields, including its overall status. Set status to in_testing while running, and passed/failed/blocked when done. status is validated against the project's execution_status values (default: not_executed, in_testing, passed, failed, blocked) - call get_project to read the exact values a project uses; do not hardcode. Does not change case results - use report_case_result for those, or set_execution_source_status for a source group's status.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedTo | string | – | Assignee user id (must be a project member) |
| description | string | – | – |
| endDate | string | – | ISO date (>= startDate) |
| environment | string | – | – |
| executionId | string | yes | Execution UUID |
| name | string | – | – |
| priority | string | – | low/medium/high/critical |
| releaseIds | array | – | Optional. The COMPLETE set of releases this execution should be linked to (replace-all): existing links not in the list are removed, new ones added. Pass [] to unlink all. Omit to leave links untouch… |
| startDate | string | – | ISO date |
| status | string | – | Execution status: not_executed/in_testing/passed/failed/blocked (+ project-custom). Use get_project to confirm valid values. |
No output schema declared.
No examples provided.
update_folder ~217
Rename a folder or suite and/or re-parent it. Set parentId to null to move it to root level, or omit it to keep the current parent. Returns the updated id, name, type, parentId, path, depth, casesCount and childFolderCount. A move carries everything nested inside along with it, so child paths change too; the new parent must be a folder in the same project, since suites cannot be parents and a folder cannot move into itself or into one of its own descendants. It never changes type and never creates or removes anything: use create_folder for a new folder or suite, delete_folder to archive one with all its contents, and move_test_case to relocate a single test case rather than its whole suite. Get folderId from list_folders.
| Name | Type | Req | Description |
|---|---|---|---|
| folderId | string | yes | Folder UUID to update |
| name | string | – | New folder name |
| parentId | string|null | – | New parent folder UUID. Set to null to move to root level. Omit to keep current parent. |
No output schema declared.
No examples provided.
update_release ~152
Update release metadata. Only provided fields are updated; omitted fields remain unchanged. Use get_release first to see current values.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description |
| endDate | string | – | New end date (YYYY-MM-DD) |
| name | string | – | New release name |
| releaseId | string | yes | Release UUID to update |
| startDate | string | – | New start date (YYYY-MM-DD) |
| status | string | – | New release status, from the project vocabulary, typically planned, in_progress, completed or cancelled, plus any the project added; call get_project for the list it uses. Setting it to completed als… |
| version | string | – | New version string |
No output schema declared.
No examples provided.
update_test_case ~315
Update an existing test case. Only provided fields are updated; omitted fields remain unchanged. Returns the full updated case object including shareUrl. TIP: Use get_test_case first to see current values.
| Name | Type | Req | Description |
|---|---|---|---|
| caseId | integer | yes | Internal numeric test case id to update - NOT the user-facing "TC-N"/caseNumber. If the user gave you a "TC-N", resolve it via list_test_cases(search: "TC-N") first. |
| customFields | object | – | Custom field values (replaces all existing custom fields) |
| dependsOn | integer|null | – | Set dependency to another numeric case ID, or null to remove dependency |
| description | string | – | New description. Supports Markdown: **bold**, *italic*, ~~strikethrough~~, inline `code`, # / ## / ### headings, "- " bullet and "1. " numbered lists, [text](url) links, and "> " blockquotes. Plain t… |
| priority | string | – | New priority. Typical values: Low, Medium, High, Critical. Check list_test_cases meta.availablePriorities for project-specific values. |
| status | string | – | New status. Typical values: Draft, Ready, Approved, Deprecated. Check list_test_cases meta.availableStatuses for project-specific values. |
| steps | array | – | Replace all steps with this array |
| tags | array | – | Replace all tags with this array |
| title | string | – | New title for the case |
No output schema declared.
No examples provided.
update_test_collection ~189
Update test collection metadata. Only provided fields are updated; omitted fields remain unchanged. Use get_test_collection first to see current values.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedTo | string | – | Email address of the assigned tester (or empty to unassign) |
| collectionId | string | yes | Test collection UUID to update |
| description | string | – | New description |
| environment | string | – | New environment |
| name | string | – | New collection name |
| priority | string | – | New priority. NOT project-configurable: the storage layer accepts only these four, in lowercase. Matching ignores case and the value is stored lowercase, so Critical and critical both land as critica… |
| status | string | – | New collection status. NOT project-configurable and matched exactly: the storage layer accepts only these four, and neither a label such as "In Progress" nor a different case such as "IN_PROGRESS" wi… |
No output schema declared.
No examples provided.
How do I install the M00N Report MCP server?
M00N Report runs locally as an npm package, launched with npx -y @m00nsolutions/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @m00nsolutions/mcp-server
claude mcp add m00nreport-mcp-server -- npx -y @m00nsolutions/mcp-server
What is the M00N Report MCP server?
M00N Report is an MCP server listed in the public MCP registry as io.github.m00nreport/mcp-server. Test management over MCP: author cases, run manual executions, cut releases, read health. This page covers its npm package (@m00nsolutions/mcp-server).
Is the M00N Report MCP server safe to use?
M00N Report scores 80 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 M00N Report MCP server expose?
M00N Report exposes 55 tools: add_cases_to_collection, add_cases_to_execution, add_collections_to_execution, add_external_link, add_suites_to_execution, and 50 more. Their descriptions and schemas cost roughly 17,521 tokens of context every time the server is loaded.
Is the M00N Report MCP server still maintained?
M00N Report 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 M00N Report MCP server under?
M00N Report declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.