io.github.mova-compact/mova-flat-runner
NPM · MOVA-MCP · SCANNED SEP 20
Governed AI workflows with human approval gates and audit trails for Claude and MCP clients.
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 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT-0).Pass
- Actively maintained (last published 142 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 685 tokens (~76/item across 9 items; 7 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.mova-compact/mova-flat-runner MCP server?
io.github.mova-compact/mova-flat-runner runs locally as an npm package, launched with npx -y mova-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 · mova-mcp
claude mcp add mova-compact-mova-flat-runner -- npx -y mova-mcp
{
"mcpServers": {
"mova-compact-mova-flat-runner": {
"command": "npx",
"args": [
"-y",
"mova-mcp"
]
}
}
} {
"servers": {
"mova-compact-mova-flat-runner": {
"command": "npx",
"args": [
"-y",
"mova-mcp"
]
}
}
} codex mcp add mova-compact-mova-flat-runner -- npx -y mova-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mova-compact-mova-flat-runner": {
"type": "local",
"command": [
"npx",
"-y",
"mova-mcp"
],
"enabled": true
}
}
} openclaw mcp add mova-compact-mova-flat-runner --command npx --arg -y --arg mova-mcp
mcp_servers:
mova-compact-mova-flat-runner:
command: "npx"
args: ["-y", "mova-mcp"] {
"McpServers": {
"mova-compact-mova-flat-runner": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mova-mcp"
]
}
}
} assistant mcp add mova-compact-mova-flat-runner -t stdio -c npx -a -y mova-mcp
{
"mcpServers": {
"mova-compact-mova-flat-runner": {
"command": "npx",
"args": [
"-y",
"mova-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.
- 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 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.
- 12 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.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 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.
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 20 Sept 2026 · Analysed npm/mova-mcp@2.0.6
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 95 packages
| Packages resolved | 95 |
|---|---|
| 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 →
mova_connector ~105
Manage connector overrides for your org. Overrides replace the sandbox mock with your real endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| auth_header | string | – | Auth header name, e.g. X-Api-Key |
| auth_value | string | – | Secret value — never echoed back in the response |
| connector_id | string | – | e.g. connector.ocr.document_extract_v1 |
| endpoint | string | – | Your HTTPS endpoint URL |
| label | string | – | – |
No output schema declared.
No examples provided.
mova_contract ~165
Manage your own registered MOVA contracts: list, register, set visibility, delete, run, or check run status.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| connector_overrides | object | – | Per-run connector overrides |
| contract_id | string | – | – |
| description | string | – | – |
| execution_mode | string | – | deterministic | bounded_variance | ai_assisted | human_gated |
| inputs | object | – | Input key-value pairs for run action |
| required_connectors | array | – | – |
| run_id | string | – | run_id from a previous run action |
| source_url | string | – | HTTPS URL to the contract JSON |
| title | string | – | – |
| version | string | – | – |
| visibility | string | – | private or public |
No output schema declared.
No examples provided.
mova_decide ~94
Submit a human decision at a contract gate. Uses ENV kind env.decision.submit_v0. contract_id comes from the mova_run response, not from business IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_id | string | yes | Contract ID from mova_run response |
| option | string | yes | Decision option_id from the decision gate (e.g. approve, reject, escalate) |
| reason | string | – | Human reasoning for the decision |
No output schema declared.
No examples provided.
mova_health ~27
Check MOVA runner health: config completeness, API connectivity, registered validator count, version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mova_query ~51
Query contract state or retrieve the signed audit trail.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_id | string | yes | – |
| view | string | yes | status = current state | audit = signed receipt | audit_compact = full event journal |
No output schema declared.
No examples provided.
mova_registry ~58
Browse the MOVA contract marketplace, connector catalogue, or your own contracts.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | Optional filter keyword |
| scope | string | yes | contracts = public marketplace | connectors = available connectors | my_contracts = your registered contracts |
No output schema declared.
No examples provided.
mova_run ~146
Start a MOVA contract execution. Before calling, read the manifest resource mova://contracts/{contract_type}/manifest to understand required inputs (DataSpec) and available decision options. Built-in contract types: invoice, po, trade, aml, complaint, compliance, credit, supply_chain, churn, contract_gen. For custom registered contracts use mova_contract with action=run.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_type | string | yes | Built-in type: invoice | po | trade | aml | complaint | compliance | credit | supply_chain | churn | contract_gen |
| inputs | object | yes | Contract inputs per the DataSpec in the manifest. Read mova://contracts/{contract_type}/manifest first. |
No output schema declared.
No examples provided.
What is the io.github.mova-compact/mova-flat-runner MCP server?
io.github.mova-compact/mova-flat-runner is an MCP server listed in the public MCP registry as io.github.mova-compact/mova-flat-runner. Governed AI workflows with human approval gates and audit trails for Claude and MCP clients. This page covers its npm package (mova-mcp).
Is the io.github.mova-compact/mova-flat-runner MCP server safe to use?
io.github.mova-compact/mova-flat-runner scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.mova-compact/mova-flat-runner MCP server expose?
io.github.mova-compact/mova-flat-runner exposes 7 tools: mova_run, mova_decide, mova_query, mova_registry, mova_connector, and 2 more. Their descriptions and schemas cost roughly 646 tokens of context every time the server is loaded.
Is the io.github.mova-compact/mova-flat-runner MCP server still maintained?
io.github.mova-compact/mova-flat-runner is still listed as active in the MCP registry. We last reached this channel on 20 September 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.mova-compact/mova-flat-runner MCP server under?
io.github.mova-compact/mova-flat-runner declares the MIT-0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.