# unstringify (npm · @unstringify/mcp)

Fix broken JSON by line, validate, convert, read CSV/NDJSON/logs as records, unpack, compare. Local.

- Trust score: 67/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@unstringify/mcp`
- Version: `0.1.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-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license.
  - Actively maintained (last published 12 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1091 tokens (~181/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the unstringify MCP server?

unstringify runs locally as an npm package, launched with npx -y @unstringify/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add tekinnnnn-unstringify -- npx -y @unstringify/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "tekinnnnn-unstringify": {
      "command": "npx",
      "args": [
        "-y",
        "@unstringify/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tekinnnnn-unstringify": {
      "command": "npx",
      "args": [
        "-y",
        "@unstringify/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add tekinnnnn-unstringify -- npx -y @unstringify/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add tekinnnnn-unstringify --command npx --arg -y --arg @unstringify/mcp
```

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "tekinnnnn-unstringify": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@unstringify/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add tekinnnnn-unstringify -t stdio -c npx -a -y @unstringify/mcp
```

### Other

```json
{
  "mcpServers": {
    "tekinnnnn-unstringify": {
      "command": "npx",
      "args": [
        "-y",
        "@unstringify/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-09-18 (score 67, +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-09-16 (score 66, +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-09-15 (score 65, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-07 (score 61)

First indexed and scored.

## MCP tools (6)

### `fix_json` (~134 tokens)

Fix JSON

Fix broken JSON (or YAML, XML) with named, line-by-line fixes: single quotes, unquoted keys, trailing commas, Python True/False/None, missing commas, a truncated file, a code fence around it. Returns the fixed text, each fix by line and kind, and whether the result is valid now. Deterministic — no guessing at content.

Input parameters:

- `format` (string): Absent: detected.
- `path` (string): A file to read instead of `text`, relative to the working directory.
- `text` (string): The text to work on. Either this or `path`.

### `validate` (~100 tokens)

Validate

Say whether text is valid JSON, YAML or XML, and where it is not: line, column, the parser’s message, and a hint when the engine has one. Detects the format when not told.

Input parameters:

- `format` (string): Absent: detected.
- `path` (string): A file to read instead of `text`, relative to the working directory.
- `text` (string): The text to work on. Either this or `path`.

### `convert` (~238 tokens)

Convert

Convert between JSON, YAML, XML, CSV, NDJSON, a Markdown table and TypeScript interfaces. A document into rows takes its main list of records, the rest of the document repeated on every row (the way pandas normalizes); rows into JSON is one array. Targets: yaml, csv, ts, markdown, ndjson, xml, json, json-min.

Input parameters:

- `delimiter` (string): CSV/TSV separator. Absent: detected.
- `from` (string): The source format. Absent: detected.
- `header` (boolean): CSV/TSV: is the first row the header? Absent: decided from the rows.
- `path` (string): A file to read instead of `text`, relative to the working directory.
- `pattern` (string): Log: a regex with named groups to read each line with. Absent: the best of the known shapes, measured.
- `rootName` (string): TypeScript: the root interface name. Default Root.
- `text` (string): The text to work on. Either this or `path`.
- `to` (string, required): The target format.

### `read_records` (~211 tokens)

Read as records

Read CSV, TSV, NDJSON, a Markdown table or a raw log as records — one JSON value per row, the header as keys, a log line split by the best known shape (JSON lines, logfmt, nginx, syslog…) or your regex with named groups. Returns the records, the counts (rows, broken, raw lines kept), the columns and the level counts.

Input parameters:

- `delimiter` (string): CSV/TSV separator. Absent: detected.
- `format` (string): Absent: detected.
- `header` (boolean): CSV/TSV: is the first row the header? Absent: decided from the rows.
- `path` (string): A file to read instead of `text`, relative to the working directory.
- `pattern` (string): Log: a regex with named groups to read each line with. Absent: the best of the known shapes, measured.
- `text` (string): The text to work on. Either this or `path`.

### `unpack` (~160 tokens)

Unpack

Open every string value that holds JSON, XML or YAML — an SNS envelope’s Message, a Kibana row’s message column, a double-encoded field — in place: the literal is replaced by what it held and every other byte stays where it was. NDJSON is unpacked one line at a time. Pass `path` (a JSON path such as $.Message) to open one value only.

Input parameters:

- `format` (string): Absent: detected.
- `path` (string): A file to read instead of `text`, relative to the working directory.
- `text` (string): The text to work on. Either this or `path`.
- `valuePath` (string): Open only the value at this path, e.g. $.Message.

### `compare` (~248 tokens)

Compare

Compare two documents by structure — keys sorted, whitespace ignored, one row per path that differs — or two sets of rows (CSV, NDJSON, a log) by key: which records were added, removed, changed, and in which fields. Formatting differences are not differences.

Input parameters:

- `delimiter` (string): CSV/TSV separator. Absent: detected.
- `format` (string): Both sides’ format. Absent: detected from the left.
- `header` (boolean): CSV/TSV: is the first row the header? Absent: decided from the rows.
- `key` (string|null): Rows: the field to match records on. Absent: detected; null: line order.
- `left` (string): The left text. Either this or `leftPath`.
- `leftPath` (string): A file to read for the left side.
- `pattern` (string): Log: a regex with named groups to read each line with. Absent: the best of the known shapes, measured.
- `right` (string): The right text. Either this or `rightPath`.
- `rightPath` (string): A file to read for the right side.

## Diagnostics

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

## Score history

- 2026-09-20: 67
- 2026-09-19: 67
- 2026-09-18: 67
- 2026-09-17: 66
- 2026-09-16: 66
- 2026-09-15: 65
- 2026-09-14: 61
- 2026-09-13: 61
- 2026-09-12: 61
- 2026-09-11: 61
- 2026-09-10: 61
- 2026-09-09: 61
- 2026-09-08: 61
- 2026-09-07: 61

## Common questions

### What is the unstringify MCP server?

unstringify is an MCP server listed in the public MCP registry as io.github.tekinnnnn/unstringify. Fix broken JSON by line, validate, convert, read CSV/NDJSON/logs as records, unpack, compare. Local. This page covers its npm package (@unstringify/mcp).

### Is the unstringify MCP server safe to use?

unstringify scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 unstringify MCP server expose?

unstringify exposes 6 tools: fix_json, validate, convert, read_records, unpack, compare. Their descriptions and schemas cost roughly 1,091 tokens of context every time the server is loaded.

### Is the unstringify MCP server still maintained?

unstringify is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- npm package: https://www.npmjs.com/package/@unstringify/mcp
- Socket report: https://socket.dev/npm/package/@unstringify/mcp
- Website: https://unstringify.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/tekinnnnn-unstringify/unstringify-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tekinnnnn-unstringify/unstringify-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tekinnnnn-unstringify/unstringify-mcp