# io.github.MukundaKatta/streamparse (npm · @mukundakatta/streamparse-mcp)

Parse partial / truncated / messy JSON for LLM tool calls and structured outputs.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@mukundakatta/streamparse-mcp`
- Version: `1.0.1`
- 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-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), 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).
  - Actively maintained (last published 99 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 251 tokens (~83/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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-streamparse -- npx -y @mukundakatta/streamparse-mcp
```

### Codex

```bash
codex mcp add mukundakatta-streamparse -- npx -y @mukundakatta/streamparse-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add mukundakatta-streamparse --command npx --arg -y --arg @mukundakatta/streamparse-mcp
```

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "mukundakatta-streamparse": {
      "command": "npx",
      "args": [
        "-y",
        "@mukundakatta/streamparse-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-03 (score 70, +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 69, +48)

- [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 → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional] Licence: MIT

### 2026-07-31 (score 21, −25)

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

### 2026-07-30 (score 46, +22)

- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 24, −22)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

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

First indexed and scored.

## MCP tools (3)

### `parse_partial_json` (~118 tokens)

Parse a JSON string that may be truncated mid-stream (e.g. a partial LLM tool call). Always returns a valid JSON value with synthetic closure of any open strings, arrays, or objects. Reports whether the input represented a complete top-level value, plus the cursor path where parsing stopped.

Input parameters:

- `lenient` (boolean): When true (default), tolerates trailing commas, single quotes, unquoted keys, ```json fences, comments, and prose padding.
- `text` (string, required): The JSON text to parse. May be truncated.

### `extract_json_from_text` (~77 tokens)

Extract and parse a JSON value embedded in messy LLM output. Strips ```json fences, leading/trailing prose, code comments, and tolerates other LLM-isms. Returns the first parseable value and where in the text it started.

Input parameters:

- `text` (string, required): Free-form text that contains a JSON value somewhere inside.

### `validate_json` (~56 tokens)

Strict-mode RFC 8259 validator. Returns ok=true and the parsed value if the input is valid JSON; otherwise returns ok=false with a precise byte position and human-readable message.

Input parameters:

- `text` (string, required): The JSON text to validate.

## Diagnostics

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

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 21
- 2026-07-31: 21
- 2026-07-30: 46
- 2026-07-28: 24
- 2026-07-27: 46

## Links

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