unstringify
NPM · @UNSTRINGIFY/MCP · SCANNED SEP 20
Fix broken JSON by line, validate, convert, read CSV/NDJSON/logs as records, unpack, compare. Local.
Available components
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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 12 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
npm · @unstringify/mcp
claude mcp add tekinnnnn-unstringify -- npx -y @unstringify/mcp
{
"mcpServers": {
"tekinnnnn-unstringify": {
"command": "npx",
"args": [
"-y",
"@unstringify/mcp"
]
}
}
} {
"servers": {
"tekinnnnn-unstringify": {
"command": "npx",
"args": [
"-y",
"@unstringify/mcp"
]
}
}
} codex mcp add tekinnnnn-unstringify -- npx -y @unstringify/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tekinnnnn-unstringify": {
"type": "local",
"command": [
"npx",
"-y",
"@unstringify/mcp"
],
"enabled": true
}
}
} openclaw mcp add tekinnnnn-unstringify --command npx --arg -y --arg @unstringify/mcp
mcp_servers:
tekinnnnn-unstringify:
command: "npx"
args: ["-y", "@unstringify/mcp"] {
"McpServers": {
"tekinnnnn-unstringify": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@unstringify/mcp"
]
}
}
} assistant mcp add tekinnnnn-unstringify -t stdio -c npx -a -y @unstringify/mcp
{
"mcpServers": {
"tekinnnnn-unstringify": {
"command": "npx",
"args": [
"-y",
"@unstringify/mcp"
]
}
}
} 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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 15 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 7 Sept 26 61
First indexed and scored.
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 20 Sept 2026 · Analysed npm/@unstringify/mcp@0.1.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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
compare Compare ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
convert Convert ~238
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The target format. |
No output schema declared.
No examples provided.
fix_json Fix JSON ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
read_records Read as records ~211
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
unpack Unpack ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
validate Validate ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
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.