# io.github.MukundaKatta/toml-yaml-json-mcp (npm · @mukundakatta/toml-yaml-json-mcp)

Parse, format, and convert configs across TOML, YAML, and JSON.

- Trust score: 64/100 (medium)
- Change this week: +46
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-07

## Components

- npm · `@mukundakatta/toml-yaml-json-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/mukundakatta-toml-yaml-json-mcp/mukundakatta-toml-yaml-json-mcp.md), [page](https://verifymcp.io/servers/mukundakatta-toml-yaml-json-mcp/mukundakatta-toml-yaml-json-mcp)

## Channel facts

- Registry: `npm`
- Package: `@mukundakatta/toml-yaml-json-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-07.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 97 of 101 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 97 of 101 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT OR Apache-2.0).
  - Actively maintained (last published 88 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 166 tokens (~55/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 14% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add mukundakatta-toml-yaml-json-mcp -- npx -y @mukundakatta/toml-yaml-json-mcp
```

### Codex

```bash
codex mcp add mukundakatta-toml-yaml-json-mcp -- npx -y @mukundakatta/toml-yaml-json-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mukundakatta-toml-yaml-json-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mukundakatta/toml-yaml-json-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mukundakatta-toml-yaml-json-mcp --command npx --arg -y --arg @mukundakatta/toml-yaml-json-mcp
```

### Hermes

```yaml
mcp_servers:
  mukundakatta-toml-yaml-json-mcp:
    command: "npx"
    args: ["-y", "@mukundakatta/toml-yaml-json-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "mukundakatta-toml-yaml-json-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mukundakatta/toml-yaml-json-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-06 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-04 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-03 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 61, +43)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Schema quality: unverified → fair
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] License: unverified → pass
- [functional] Licence: MIT OR Apache-2.0

### 2026-07-31 (score 18, −6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 24, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 42)

First indexed and scored.

## MCP tools (3)

### `parse` (~46 tokens)

Parse a config string (TOML, YAML, or JSON) into a value. Returns the parsed value as JSON.

Input parameters:

- `format` (string, required)
- `text` (string, required)

### `format` (~57 tokens)

Serialize a value into TOML, YAML, or JSON. Use to generate config files an LLM-produced value would otherwise mangle (TOML especially).

Input parameters:

- `format` (string, required)
- `value` (required): Any JSON-serializable value.

### `convert` (~63 tokens)

Round-trip a config from one format to another (TOML <-> YAML <-> JSON). Useful when an upstream tool produced one and a downstream tool wants the other.

Input parameters:

- `from` (string, required)
- `text` (string, required)
- `to` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mukundakatta-toml-yaml-json-mcp/mukundakatta-toml-yaml-json-mcp#diagnostics

## Score history

- 2026-08-07: 64
- 2026-08-06: 64
- 2026-08-05: 63
- 2026-08-04: 63
- 2026-08-03: 62
- 2026-08-02: 61
- 2026-08-01: 18
- 2026-07-31: 18
- 2026-07-30: 24
- 2026-07-28: 42
- 2026-07-27: 42

## Links

- npm package: https://www.npmjs.com/package/@mukundakatta/toml-yaml-json-mcp
- Socket report: https://socket.dev/npm/package/@mukundakatta/toml-yaml-json-mcp
- Repository: https://github.com/MukundaKatta/mcp-stack
- Changelog RSS feed: https://verifymcp.io/servers/mukundakatta-toml-yaml-json-mcp/mukundakatta-toml-yaml-json-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mukundakatta-toml-yaml-json-mcp/mukundakatta-toml-yaml-json-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mukundakatta-toml-yaml-json-mcp/mukundakatta-toml-yaml-json-mcp