Rulemorph MCP Server
MCPB · RULEMORPH-MCP-V0.3.4-X86_64-UNKNOWN-LINUX-GNU.MCPB · 4 COMPONENTS
MCP server for CSV/JSON data transformation using YAML rules
Last scanned (3 hours ago)
Scores higher than 84% of MCPB servers
Category Data and Analytics
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- 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 149 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- 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
- Context-footprint check failed: tool/resource definitions use about 1146 tokens (~114/item across 10 items; 7 tools + 3 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 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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 0
- Stability: 0.97 → pass security
- 4 Nov 26 +1
- Provenance: unverified → fail ▼ security
- 3 Nov 26 −1
- Provenance: fail → unverified ▼ security
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 5 Nov 2026 · Analysed mcpb/https://github.com/vinhphatfsg/rulemorph/releases/download/v0.3.4/rulemorph-mcp-v0.3.4-x86_64-unknown-linux-gnu.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
analyze_input ~163
Analyze input data and summarize field paths and types.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Input format when input_text/input_path is used. |
| input_json | object|array | – | Inline typed JSON value. Mutually exclusive with input_path and input_text. Duplicate-key validation applies to raw JSON input_text/input_path, not to input_json after JSON-RPC decoding. |
| input_path | string | – | Path to the input CSV/JSON file. Mutually exclusive with input_text and input_json. |
| input_text | string | – | Inline input text (CSV or JSON). Mutually exclusive with input_path and input_json. |
| max_paths | integer | – | Maximum number of unique paths to include in the response. |
| records_path | string | – | Optional records path for JSON inputs. |
No output schema declared.
No examples provided.
generate_dto ~108
Generate DTO definitions from a YAML rule file.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | yes | DTO output language. |
| name | string | – | Optional DTO root type name. |
| rules_format | string | – | Rule parser format. Defaults to file extension for rules_path and yaml for rules_text. |
| rules_path | string | – | Path to the YAML or JSON rules file. Mutually exclusive with rules_text. |
| rules_text | string | – | Inline YAML or JSON rules content. Mutually exclusive with rules_path. |
No output schema declared.
No examples provided.
generate_rules_from_base ~226
Generate rules by mapping input data to existing rule targets.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Override input format. |
| input_json | object|array | – | Inline typed JSON value. Mutually exclusive with input_path and input_text. Duplicate-key validation applies to raw JSON input_text/input_path, not to input_json after JSON-RPC decoding. |
| input_path | string | – | Path to the input CSV/JSON file. Mutually exclusive with input_text and input_json. |
| input_text | string | – | Inline input text (CSV or JSON). Mutually exclusive with input_path and input_json. |
| max_candidates | integer | – | Maximum number of candidates to return per target. |
| records_path | string | – | Optional records path for JSON inputs. |
| rules_format | string | – | Rule parser format. Defaults to file extension for rules_path and yaml for rules_text. |
| rules_path | string | – | Path to the YAML or JSON rules file. Mutually exclusive with rules_text. |
| rules_text | string | – | Inline YAML or JSON rules content. Mutually exclusive with rules_path. |
No output schema declared.
No examples provided.
generate_rules_from_dto ~180
Generate rules by mapping input data to a DTO schema.
| Name | Type | Req | Description |
|---|---|---|---|
| dto_language | string | yes | DTO language. |
| dto_text | string | yes | DTO source text. |
| format | string | – | Override input format. |
| input_json | object|array | – | Inline typed JSON value. Mutually exclusive with input_path and input_text. Duplicate-key validation applies to raw JSON input_text/input_path, not to input_json after JSON-RPC decoding. |
| input_path | string | – | Path to the input CSV/JSON file. Mutually exclusive with input_text and input_json. |
| input_text | string | – | Inline input text (CSV or JSON). Mutually exclusive with input_path and input_json. |
| max_candidates | integer | – | Maximum number of candidates to return per target. |
| records_path | string | – | Optional records path for JSON inputs. |
No output schema declared.
No examples provided.
list_ops ~19
List supported expression ops, comparisons, and type casts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
transform ~334
Transform CSV/JSON input with a YAML rule file.
| Name | Type | Req | Description |
|---|---|---|---|
| context_json | object | – | Optional inline JSON context value. Mutually exclusive with context_path. |
| context_path | string | – | Optional path to a JSON context file. Mutually exclusive with context_json. |
| format | string | – | Override input format from the rule file. |
| input_json | object|array | – | Inline typed JSON value. Mutually exclusive with input_path and input_text. Duplicate-key validation applies to raw JSON input_text/input_path, not to input_json after JSON-RPC decoding. |
| input_path | string | – | Path to the input file. Mutually exclusive with input_text and input_json. |
| input_text | string | – | Inline text input. Mutually exclusive with input_path and input_json. |
| max_output_bytes | integer | – | Maximum output size in bytes before truncation. |
| ndjson | boolean | – | Emit NDJSON output (one JSON object per line). |
| output_path | string | – | Optional path to write the output. |
| preview_rows | integer | – | Maximum rows to return when ndjson=true. |
| return_output_json | boolean | – | Include parsed output JSON in meta.output when ndjson=false and within size limits. |
| rules_format | string | – | Rule parser format. Defaults to file extension for rules_path and yaml for rules_text. |
| rules_path | string | – | Path to the YAML or JSON rules file. Mutually exclusive with rules_text. |
| rules_text | string | – | Inline YAML or JSON rules content. Mutually exclusive with rules_path. |
| validate | boolean | – | Validate the rule file before transforming. |
No output schema declared.
No examples provided.
validate_rules ~82
Validate a YAML rule file.
| Name | Type | Req | Description |
|---|---|---|---|
| rules_format | string | – | Rule parser format. Defaults to file extension for rules_path and yaml for rules_text. |
| rules_path | string | – | Path to the YAML or JSON rules file. Mutually exclusive with rules_text. |
| rules_text | string | – | Inline YAML or JSON rules content. Mutually exclusive with rules_path. |
No output schema declared.
No examples provided.
How do I install the Rulemorph MCP Server server?
Rulemorph MCP Server ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · rulemorph-mcp-v0.3.4-x86_64-unknown-linux-gnu.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the Rulemorph MCP Server server?
Rulemorph MCP Server is listed in the public MCP registry as io.github.vinhphatfsg/rulemorph-mcp. MCP server for CSV/JSON data transformation using YAML rules. This page covers its MCPB bundle (https://github.com/vinhphatfsg/rulemorph/releases/download/v0.3.4/rulemorph-mcp-v0.3.4-x86_64-unknown-linux-gnu.mcpb).
Is the Rulemorph MCP Server server safe to use?
Rulemorph MCP Server scores 52 out of 100 on VerifyMCP. 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 Rulemorph MCP Server server expose?
Rulemorph MCP Server exposes 7 tools: transform, validate_rules, generate_dto, list_ops, analyze_input, and 2 more. Their descriptions and schemas cost roughly 1,112 tokens of context every time the server is loaded.
What licence is the Rulemorph MCP Server server under?
Rulemorph MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.