io.github.rog0x/json
NPM · @ROG0X/MCP-JSON-TOOLS
JSON/YAML/CSV validate, diff, transform for AI agents
Available components
Last scanned (3 hours ago)
Scores higher than 68% 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 Security88
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects csv-parse 5.6.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 36 of 100 dependencies flagged as unhealthy. 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 228 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).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 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 7 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 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.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 27 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
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 6 Nov 2026 · Analysed npm/@rog0x/mcp-json-tools@1.0.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-8cw4-87c7-c6xx | CVE-2026-85063 | medium | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 100 packages
| Packages resolved | 100 |
|---|---|
| Stale | 36 |
| 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 →
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.
How do I install the io.github.rog0x/json MCP server?
io.github.rog0x/json runs locally as an npm package, launched with npx -y @rog0x/mcp-json-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-json-tools
claude mcp add rog0x-json -- npx -y @rog0x/mcp-json-tools
What is the io.github.rog0x/json MCP server?
io.github.rog0x/json is an MCP server listed in the public MCP registry as io.github.rog0x/json. JSON/YAML/CSV validate, diff, transform for AI agents. This page covers its npm package (@rog0x/mcp-json-tools).
Is the io.github.rog0x/json MCP server safe to use?
io.github.rog0x/json scores 81 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 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.rog0x/json MCP server expose?
io.github.rog0x/json exposes 7 tools: json_validate, json_diff, json_transform, csv_to_json, json_to_csv, and 2 more. Their descriptions and schemas cost roughly 520 tokens of context every time the server is loaded.
Is the io.github.rog0x/json MCP server still maintained?
io.github.rog0x/json is still listed as active in the MCP registry. We last reached this channel on 6 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.rog0x/json MCP server under?
io.github.rog0x/json declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.rog0x/json MCP server?
VerifyMCP ran 15 checks on io.github.rog0x/json, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.rog0x/json: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.