The official Svelte MCP server providing docs and autofixing tools for Svelte development
Tools
json_validate
Validate JSON syntax and report errors.
json_text string · required
JSON string to validate
A call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
96/100
tool-list score
4
tools declared
remote
via our gateway
—
p95 latency
What it does
DataForge MCP Toolkit helps developers and AI agents validate JSON, format structured data, compare JSON documents, and analyze text. Four lightweight tools run on Cloudflare Workers without GPU.Fast.
Quickstart
# 1 — buy it first ($50 a month): mcprush.com/checkout?server=dataforge-mcp-toolkit
# a key alone is not enough: the gateway refuses every call until it is bought
# 2 — sign in with a key of the account that bought it: npx mcprush@latest login
# the key is at mcprush.com/dashboard#access
# 3 — install
npx mcprush@latest add audy-hayden/dataforge-mcp-toolkit
# 4 — ask your agent for something these tools do
# json_validate, json_format, json_diff and 1 more
Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Codenot declared — it may still work
Claude Code has its own MCP command, and the key rides on it as a header — the gateway refuses a call that carries none. Claude Code reads MCPRUSH_KEY each time it connects, so the key stays out of its config: export your key from Access in your shell profile (macOS, Linux), or run setx MCPRUSH_KEY <your key> and open a new terminal (Windows). Or let npx mcprush@latest add audy-hayden/dataforge-mcp-toolkit write the entry with the key for you; --scope user makes it available in every project.
Buy it first — $50 a month. A key alone is not enough: until this account has bought it, the gateway refuses every call. Subscribe, then use a key of the account that bought it.
claude mcp add --transport http --scope user dataforge-mcp-toolkit https://mcprush.com/gw/dataforge-mcp-toolkit/mcp --header 'Authorization: Bearer ${MCPRUSH_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing: the gateway answers only a key of an account whose subscription to it is active — how the login works. Until then add writes nothing: signed out, it names the price and the checkout link; signed in, it prints the checkout link, or why the subscription is held (ended, paused, an unpaid invoice) and the link that lifts it. The gateway refuses every call the same way, and most clients only show the server as failed.
What it writes
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
What you approve
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Validate JSON syntax and report errors.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| json_text | string | yes | JSON string to validate |
Format or minify JSON data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| json_text | string | yes | — |
| minify | boolean | no | Set true to minify JSON |
Compare two JSON documents and report differences.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| json_a | string | yes | — |
| json_b | string | yes | — |
Count characters, words, lines and UTF-8 bytes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
Starter
$50 / month
- 250 calls a month, included
- No rate limit
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against the 250 calls a month on Starter
| Tool | Unit | Calls used | Out of the monthly allowance |
|---|---|---|---|
| json_validate | call | 1 | 0.4000% |
| json_format | call | 1 | 0.4000% |
| json_diff | call | 1 | 0.4000% |
| text_statistics | call | 1 | 0.4000% |
Failed calls, timeouts and anything the gateway rejects never count. When the allowance runs out the gateway returns an error naming the plan limit — nothing is billed beyond the subscription, ever.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.1.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest36d39c98b6f049269bef5a67651aeb0b26d23aeff4e48a3376dc792da41c636c
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| json_validate | no tags | |
| json_format | no tags | |
| json_diff | no tags | |
| text_statistics | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest36d39c98b6f04926
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
The gateway serves every install the publisher’s current release, so a release cannot be pinned or rolled back to here yet. The history below is for reading; the current release on file is 0.1.0.
0.1.0
16 Oct 2026
latest- The version this listing went live with, after review.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish DataForge MCP Toolkit can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.