io.github.rog0x/json
NPM · @ROG0X/MCP-JSON-TOOLS · SCANNED AUG 3
JSON/YAML/CSV validate, diff, transform for AI agents
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (101 of 106), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (101 of 106), so this covers what we could see, not the whole tree. View diagnostics → Partial
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 133 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 520 tokens (~74/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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @rog0x/mcp-json-tools
claude mcp add rog0x-json -- npx -y @rog0x/mcp-json-tools
codex mcp add rog0x-json -- npx -y @rog0x/mcp-json-tools
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rog0x-json": {
"type": "local",
"command": [
"npx",
"-y",
"@rog0x/mcp-json-tools"
],
"enabled": true
}
}
} openclaw mcp add rog0x-json --command npx --arg -y --arg @rog0x/mcp-json-tools
mcp_servers:
rog0x-json:
command: "npx"
args: ["-y", "@rog0x/mcp-json-tools"] {
"mcpServers": {
"rog0x-json": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-json-tools"
]
}
}
} 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.
- 2 Aug 26 +47
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 31 Jul 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@rog0x/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 101 packages
101 packages in the resolved dependency tree · 98 deprecated · 34 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
csv_to_json ~98
Convert CSV text to a JSON array of objects. Supports custom delimiters, header row detection, and automatic type casting.
| Name | Type | Req | Description |
|---|---|---|---|
| castTypes | boolean | — | Automatically cast numeric and boolean values from strings (default: false) |
| csv | string | yes | The CSV text to convert |
| delimiter | string | — | Column delimiter character (default: ',' |
| hasHeaders | boolean | — | Whether the first row contains column headers (default: true) |
No output schema declared.
No examples provided.
json_diff ~57
Compare two JSON objects and show additions, removals, and changes with their paths.
| Name | Type | Req | Description |
|---|---|---|---|
| modified | string | yes | The modified JSON object (as a JSON string) |
| original | string | yes | The original JSON object (as a JSON string) |
No output schema declared.
No examples provided.
json_to_csv ~75
Convert a JSON array of objects to CSV text. Automatically extracts headers from object keys.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | The JSON array to convert (as a JSON string) |
| delimiter | string | — | Column delimiter character (default: ',') |
| includeHeaders | boolean | — | Whether to include a header row (default: true) |
No output schema declared.
No examples provided.
json_to_yaml ~47
Convert a JSON string to YAML text.
| Name | Type | Req | Description |
|---|---|---|---|
| indent | number | — | YAML indentation spaces (default: 2) |
| jsonText | string | yes | The JSON text to convert to YAML |
No output schema declared.
No examples provided.
json_transform ~129
Apply transformations to a JSON object: pick specific fields, rename keys, flatten nested objects, or unflatten dot-notation keys.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | The JSON data to transform (as a JSON string) |
| fields | array | — | For 'pick': array of field paths to extract (supports dot notation like 'user.name') |
| mapping | object | — | For 'rename': object mapping old key names to new key names |
| operation | string | yes | The transformation operation to apply |
| separator | string | — | For 'flatten'/'unflatten': separator character (default: '.') |
No output schema declared.
No examples provided.
json_validate ~67
Validate a JSON object against a JSON Schema. Returns whether the data is valid and a list of errors with their paths.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | The JSON data to validate (as a JSON string) |
| schema | string | yes | The JSON Schema to validate against (as a JSON string) |
No output schema declared.
No examples provided.
yaml_to_json ~47
Convert YAML text to a JSON string.
| Name | Type | Req | Description |
|---|---|---|---|
| indent | number | — | JSON indentation spaces (default: 2) |
| yamlText | string | yes | The YAML text to convert to JSON |
No output schema declared.
No examples provided.