# JSONPad documentation (remote · mcp.jsonpad.io)

JSONPad docs, API, SDK and CLI references, and offline checkers for write rules and flows.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `mcp.jsonpad.io`: 74/100 (this document), [markdown](https://verifymcp.io/servers/io-jsonpad-docs/docs.md), [page](https://verifymcp.io/servers/io-jsonpad-docs/docs)
- npm · `@basementuniverse/jsonpad-docs-mcp`: 65/100, [markdown](https://verifymcp.io/servers/io-jsonpad-docs/basementuniverse-jsonpad-docs-mcp.md), [page](https://verifymcp.io/servers/io-jsonpad-docs/basementuniverse-jsonpad-docs-mcp)

## Channel facts

- Endpoint: `https://mcp.jsonpad.io/docs`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-04.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 87/100
  - 97% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 6365 tokens (~46/item across 138 items; 14 tools + 124 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "eval_write_rule" implies "eval" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 16 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 JSONPad documentation MCP server?

JSONPad documentation is a hosted endpoint at https://mcp.jsonpad.io/docs, so there is nothing to install locally. 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 --transport http io-jsonpad-docs 'https://mcp.jsonpad.io/docs'
```

### Cursor

```json
{
  "mcpServers": {
    "io-jsonpad-docs": {
      "url": "https://mcp.jsonpad.io/docs"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-jsonpad-docs": {
      "type": "http",
      "url": "https://mcp.jsonpad.io/docs"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-jsonpad-docs]
url = "https://mcp.jsonpad.io/docs"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-jsonpad-docs": {
      "type": "remote",
      "url": "https://mcp.jsonpad.io/docs",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-jsonpad-docs --url 'https://mcp.jsonpad.io/docs' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-jsonpad-docs:
    url: "https://mcp.jsonpad.io/docs"
```

### Netclaw

```json
{
  "McpServers": {
    "io-jsonpad-docs": {
      "Transport": "http",
      "Url": "https://mcp.jsonpad.io/docs"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-jsonpad-docs -t streamable-http -u 'https://mcp.jsonpad.io/docs'
```

### Other

```json
{
  "mcpServers": {
    "io-jsonpad-docs": {
      "type": "http",
      "url": "https://mcp.jsonpad.io/docs"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-04 (score 74, +1)

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

### 2026-10-03 (score 73, +8)

- [security improvement] Judged manipulation: unverified → pass
- [functional improvement] Schema quality: unverified → excellent

### 2026-10-02 (score 65, −7)

- [security regression] Judged manipulation: pass → unverified
- [functional regression] Schema quality: excellent → unverified

### 2026-10-01 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-30 (score 72)

First indexed and scored.

## MCP tools (14)

### `search_docs` (~147 tokens)

Search the JSONPad docs

Search the JSONPad documentation, the JavaScript SDK references and the command line tool reference. Returns the best-matching sections with a snippet and their jsonpad.io URL; read one with read_doc. Exact identifiers work well: error codes and names, headers, SDK methods, CLI commands, $jsonpad-var variables, "POST /lists/{listId}/items".

Input parameters:

- `limit` (integer): How many results (1-10)
- `query` (string, required): What to look for
- `section` (string): Only search one section: guides, api-reference (every API reference section), lists, items, indexes, identities, tokens, flows, schema-sync, sdk or cli

Output parameters:

- `results` (array)

### `read_doc` (~150 tokens)

Read a JSONPad docs page

Read a documentation page as markdown, or one section of it. Give a page slug ("indexing"), a /docs path, a jsonpad.io URL (with or without .md, and with an optional #anchor), "sdk/jsonpad-sdk", "sdk/jsonpad-realtime-sdk", "cli/reference" or "cli/readme". Long pages are cut at a section boundary; read on with the returned nextSection.

Input parameters:

- `maxChars` (integer): The most characters of markdown to return
- `page` (string, required): The page: a slug, path or URL
- `section` (string): A heading anchor ("filtering-items") or heading text; overrides a #anchor in page

Output parameters:

- `markdown` (string)
- `title` (string)
- `truncated` (boolean)
- `url` (string)

### `list_docs` (~37 tokens)

List the JSONPad docs pages

List the documentation pages by section, with a description of each: the table of contents.

Input parameters:

- `section` (string): Only list one section

Output parameters:

- `sections` (array)

### `list_api_endpoints` (~47 tokens)

List the JSONPad API endpoints

List the REST API endpoints an API token can use, as method, path and title. Get one in full with get_api_endpoint.

Input parameters:

- `resource` (string): Only one resource

Output parameters:

- `endpoints` (array)

### `get_api_endpoint` (~148 tokens)

Get a JSONPad API endpoint contract

The full contract of one REST API endpoint: parameters, headers, request body, responses and examples, and the JavaScript SDK method that calls it. Find it by id (the docs page slug, e.g. "item-restore"), by method and path (templates or concrete paths both work: "/lists/my-list/items/abc"), or by a description.

Input parameters:

- `id` (string): The endpoint id, from list_api_endpoints
- `method` (string): The HTTP method
- `path` (string): The path, e.g. /lists/{listId}/items
- `query` (string): What the endpoint does, e.g. "restore a deleted item"

Output parameters:

- `endpoint` (object)

### `get_sdk_method` (~106 tokens)

Get a JSONPad SDK method

The signature, description and example of a method in the JavaScript SDK (@basementuniverse/jsonpad-sdk) or the realtime SDK, and the REST endpoint it calls. Find it by name ("restoreItem") or by what it does.

Input parameters:

- `name` (string): The method name, e.g. restoreItem
- `package` (string): Only one package
- `query` (string): What the method does, e.g. "wait for an index to build"

Output parameters:

- `method` (object)

### `get_cli_command` (~106 tokens)

Get a JSONPad CLI command

The usage, arguments and options of a jsonpad command line tool (@basementuniverse/jsonpad-cli) command, and whether it works offline. Find it by name ("rules test", "jsonpad sync-schema --dry-run") or by what it does.

Input parameters:

- `name` (string): The command, e.g. "sync-schema" or "jsonpad rules test"
- `query` (string): What the command does, e.g. "export items to a file"

Output parameters:

- `command` (object)

### `lookup_error` (~95 tokens)

Look up a JSONPad error

What a JSONPad API error code means, its HTTP status, and the guides that explain it. Give the numeric code (10013) or the name (QUOTA_EXCEEDED), as found in an error response's "code" and "name".

Input parameters:

- `code` (integer): The numeric code, e.g. 10013
- `name` (string): The name, e.g. QUOTA_EXCEEDED

Output parameters:

- `error` (object)

### `get_plan_limits` (~110 tokens)

Get JSONPad plan limits

The limits of each public plan (Free, Indie, Pro, Scale): requests per month and minute, the minimum gap between requests, storage, item size, versions kept, tokens, identities, realtime connections, webhooks and flows. null means unlimited. Sizes are in bytes, rateLimit in milliseconds, prices in GBP.

Input parameters:

- `limit` (string): One limit, e.g. maxItemSize
- `plan` (string): One plan, by id or name, e.g. "free"

Output parameters:

- `plans` (array)

### `check_write_rules` (~163 tokens)

Check write rules

Compile a list's write rules with the same engine the API uses, and run their tests (a rules-tests-v1 document). Returns every diagnostic with its line and column, and for each failing test what it expected, what happened, and how each rule came out. Costs nothing and sees no data: lookups find the test document's items. Use it before saving rules.

Input parameters:

- `knownLists` (array): Path names of lists that exist, so lookups into any other list are warned about, as the API does when rules are saved
- `rules` (required): The rule text, or its lines as an array (as in a schema sync document)
- `tests`: The rule tests: a rules-tests-v1 document ({ "tests": [...] }), optional

Output parameters:

- `diagnostics` (array)
- `ok` (boolean)

### `eval_write_rule` (~182 tokens)

Try a write against write rules

Check one write against a rule set, as the API would, and say whether it would be allowed, denied (403) or failed (400), which statement decided it, and (with trace) what every expression evaluated to. The write is shaped like a rule test case: action, identity, token, old, new, patch, merge, now. Costs nothing and sees no data.

Input parameters:

- `identities` (object): Named identities the write can refer to
- `items` (object): Items for lookups to find: { "<list>": { "<item id or alias>": { "data": ... } } }
- `rules` (required): The rule text, or its lines as an array (as in a schema sync document)
- `trace` (boolean): Include the value of every expression
- `write` (object, required): The write to check

Output parameters:

- `ok` (boolean)

### `check_flow` (~121 tokens)

Check a flow

Compile a flow document (flows-v1) with the same engine the API uses, and run its tests (flow-tests-v1) against in-memory data. Returns diagnostics (with JSON pointers into the document), what the flow reads and writes, and why each failing test failed. Costs nothing and sees no data.

Input parameters:

- `flow` (required): The flow document
- `knownLists` (array): Path names of lists that exist, so the flow using any other list is warned about
- `tests`: The flow tests: a flow-tests-v1 document, optional

Output parameters:

- `diagnostics` (array)
- `ok` (boolean)

### `validate_sync_document` (~155 tokens)

Validate a schema sync document

Check a schema sync document (sync-v1) as far as possible without an account: against the JSON schema the API uses, the API's rules for keys and indexes, and every rule set and flow in it with their tests. Documents that reference files (rulesFile, flowFile and their tests) are checked too if the files' contents are given in files. What a sync would change needs the account: the API server's plan_schema_sync, or jsonpad sync-schema --dry-run.

Input parameters:

- `document` (required): The schema sync document
- `files` (object): The contents of files the document references, keyed by the path written in the document, e.g. { "rules/games.rules": "allow ..." }

Output parameters:

- `ok` (boolean)
- `problems` (array)

### `validate_token_permissions` (~108 tokens)

Validate token permissions

Check an API token's permission rules against the schema the API uses, say which rule shape a broken one was meant to be, and warn about valid rules that probably don't do what was meant (rule order, restore without view, sync-schema alone, allow "*").

Input parameters:

- `permissions` (required): The permission rules, e.g. [{ "mode": "allow", "action": "view", "resourceType": "item", "listIds": ["*"], "itemIds": ["*"] }]

Output parameters:

- `ok` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-jsonpad-docs/docs#diagnostics

## Score history

- 2026-10-04: 74
- 2026-10-03: 73
- 2026-10-02: 65
- 2026-10-01: 72
- 2026-09-30: 72

## Common questions

### What is the JSONPad documentation MCP server?

JSONPad documentation is an MCP server listed in the public MCP registry as io.jsonpad/docs. JSONPad docs, API, SDK and CLI references, and offline checkers for write rules and flows. This page covers its hosted endpoint (https://mcp.jsonpad.io/docs).

### Is the JSONPad documentation MCP server safe to use?

JSONPad documentation scores 74 out of 100 on VerifyMCP. 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 JSONPad documentation MCP server expose?

JSONPad documentation exposes 14 tools: search_docs, read_doc, list_docs, list_api_endpoints, get_api_endpoint, and 9 more. Their descriptions and schemas cost roughly 1,675 tokens of context every time the server is loaded.

### Does the JSONPad documentation MCP server require authentication?

No. We connected to JSONPad documentation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the JSONPad documentation MCP server still maintained?

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

## Links

- Remote endpoint: https://mcp.jsonpad.io/docs
- Website: https://jsonpad.io/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-jsonpad-docs/docs.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-jsonpad-docs/docs.json
- HTML version of this page: https://verifymcp.io/servers/io-jsonpad-docs/docs