io.github.rog0x/config
NPM · @ROG0X/MCP-CONFIG-TOOLS
JSON, YAML, TOML, INI config tools for AI agents
Available components
Last scanned (8 hours ago)
Scores higher than 84% 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 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
- 30 of 93 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
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 503 tokens (~100/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 19 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 Oct 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.
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-config-tools@1.0.2
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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
config_diff ~100
Compare two configuration files in any supported format (JSON, YAML, TOML, INI). Shows additions, removals, and changes with nested path information.
| Name | Type | Req | Description |
|---|---|---|---|
| content_a | string | yes | First config file content |
| content_b | string | yes | Second config file content |
| format_a | string | – | Format of first file (default: auto-detect) |
| format_b | string | – | Format of second file (default: auto-detect) |
No output schema declared.
No examples provided.
ini_parser ~97
Parse INI and properties configuration files. Read sections and keys, convert between INI and JSON formats.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action: parse, get_sections, get_value, to_json (INI->JSON), from_json (JSON->INI) |
| content | string | yes | INI or JSON content |
| key | string | – | Key name (for get_value) |
| section | string | – | Section name (for get_value) |
No output schema declared.
No examples provided.
json_config ~96
Read, validate, deep merge, and diff JSON/JSONC configuration files. Supports comments and trailing commas.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform: parse (parse JSONC), validate (check validity), merge (deep merge two configs), diff (find differences) |
| content | string | yes | Primary JSON/JSONC content |
| content2 | string | – | Second JSON/JSONC content (for merge/diff actions) |
No output schema declared.
No examples provided.
toml_parser ~121
Parse TOML configuration files (Cargo.toml, pyproject.toml, etc.). Extract sections, list dependencies, compare versions.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action: parse, extract_section, list_deps, compare_versions |
| content | string | – | TOML content to parse (for parse/extract_section/list_deps) |
| section | string | – | Dot-separated section path (for extract_section) |
| version_a | string | – | First version string (for compare_versions) |
| version_b | string | – | Second version string (for compare_versions) |
No output schema declared.
No examples provided.
yaml_config ~89
Read, validate, and convert YAML configuration files. Validate against docker-compose, GitHub Actions, or Kubernetes schemas.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action: parse, validate, to_json (YAML->JSON), from_json (JSON->YAML), validate_schema |
| content | string | yes | YAML or JSON content to process |
| schema_type | string | – | Schema type for validate_schema action |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/config MCP server?
io.github.rog0x/config runs locally as an npm package, launched with npx -y @rog0x/mcp-config-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-config-tools
claude mcp add rog0x-config -- npx -y @rog0x/mcp-config-tools
What is the io.github.rog0x/config MCP server?
io.github.rog0x/config is an MCP server listed in the public MCP registry as io.github.rog0x/config. JSON, YAML, TOML, INI config tools for AI agents. This page covers its npm package (@rog0x/mcp-config-tools).
Is the io.github.rog0x/config MCP server safe to use?
io.github.rog0x/config scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting 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/config MCP server expose?
io.github.rog0x/config exposes 5 tools: json_config, yaml_config, toml_parser, ini_parser, config_diff. Their descriptions and schemas cost roughly 503 tokens of context every time the server is loaded.
Is the io.github.rog0x/config MCP server still maintained?
io.github.rog0x/config 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/config MCP server under?
io.github.rog0x/config 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/config MCP server?
VerifyMCP ran 16 checks on io.github.rog0x/config, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.