Skip to content

JSONPad documentation MCP server

io.jsonpad/docsjsonpad.iostreamable-httpv0.1.0Scanned

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

14 tools: 3 change things and 11 only read.

Tools: 0 delete, 0 irreversible, 3 write, 11 read.
  • Reads private data · 3
  • Reads text others write · 1
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the JSONPad documentation MCP server can do

The JSONPad documentation MCP server is published by jsonpad.io, a domain the MCP Registry verified. It has 14 tools. It can create or change data (3 tools: check_write_rules, eval_write_rule and check_flow), but cannot delete data. 11 tools only read.

3 tools read private data (search_docs, read_doc and list_docs); 1 tool brings in text other people can write (lookup_error).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Changes things 3Claude Code: ask
  • check_flowCompile a flow document (flows-v1) with the same engine the API uses, and run its tests (flow-tests-v1) against in-memory data.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • check_write_rulesCompile a list's write rules with the same engine the API uses, and run their tests (a rules-tests-v1 document).1 finding

    Why it is in this group

    • The name "check_write_rules" says "write": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "check_write_rules" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_write_rules" says "write": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • eval_write_ruleCheck 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 exp…1 finding

    Why it is in this group

    • The name "eval_write_rule" says "write": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "eval_write_rule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "eval_write_rule" says "write": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 11Show 11 read-only tools
  • get_api_endpointThe full contract of one REST API endpoint: parameters, headers, request body, responses and examples, and the JavaScript SDK method that calls it.No findings

    Why it is in this group

    • The name "get_api_endpoint" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_cli_commandThe usage, arguments and options of a jsonpad command line tool (@basementuniverse/jsonpad-cli) command, and whether it works offline.No findings

    Why it is in this group

    • The name "get_cli_command" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_plan_limitsThe 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, re…No findings

    Why it is in this group

    • The name "get_plan_limits" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_sdk_methodThe signature, description and example of a method in the JavaScript SDK (@basementuniverse/jsonpad-sdk) or the realtime SDK, and the REST endpoint it calls.No findings

    Why it is in this group

    • The name "get_sdk_method" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_api_endpointsList the REST API endpoints an API token can use, as method, path and title.No findings

    Why it is in this group

    • The name "list_api_endpoints" says "list": a word for reading.
    Description, as the server wrote it
    List the REST API endpoints an API token can use, as method, path and title. Get one in full with get_api_endpoint.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_docsList the documentation pages by section, with a description of each: the table of contents.Reads private dataNo findings

    Why it is in this group

    • The name "list_docs" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_docs" says "list" and "doc": it reads documents.
    • private-dataThe description's first sentence says "list" and "table": it reads databases.
    Description, as the server wrote it
    List the documentation pages by section, with a description of each: the table of contents.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • lookup_errorWhat a JSONPad API error code means, its HTTP status, and the guides that explain it.Reads text others writeNo findings

    Why it is in this group

    • The name "lookup_error" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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".

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • read_docRead a documentation page as markdown, or one section of it.Reads private dataNo findings

    Why it is in this group

    • The name "read_doc" says "read": a word for reading.

    What it can reach

    • private-dataThe name "read_doc" says "read" and "doc": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • search_docsSearch the JSONPad documentation, the JavaScript SDK references and the command line tool reference.Reads private dataNo findings

    Why it is in this group

    • The name "search_docs" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_docs" says "search" and "doc": it reads documents.
    Description, as the server wrote it
    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".

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • validate_sync_documentCheck 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 flo…No findings

    Why it is in this group

    • The name "validate_sync_document" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • validate_token_permissionsCheck 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…No findings

    Why it is in this group

    • The name "validate_token_permissions" says "validate": a word for reading.
    Description, as the server wrote it
    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 "*").

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:13 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.jsonpad.io/.well-known/oauth-protected-resource
Authorization servers
https://api.jsonpad.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.jsonpad.io/docs: tools/list returned 14 tools to an anonymous client, including check_write_rules (write), eval_write_rule (write), check_flow (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "check_write_rules" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_write_rules" says "write": a word for a change.

    What this check looks for
  • The server marks "eval_write_rule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "eval_write_rule" says "write": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http docs https://mcp.jsonpad.io/docs
claude mcp add --transport http docs https://mcp.jsonpad.io/docs

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__docs__search_docs",
      "mcp__docs__read_doc",
      "mcp__docs__list_docs",
      "mcp__docs__list_api_endpoints",
      "mcp__docs__get_api_endpoint",
      "mcp__docs__get_sdk_method",
      "mcp__docs__get_cli_command",
      "mcp__docs__lookup_error",
      "mcp__docs__get_plan_limits",
      "mcp__docs__validate_sync_document",
      "mcp__docs__validate_token_permissions"
    ],
    "ask": [
      "mcp__docs__check_write_rules",
      "mcp__docs__eval_write_rule",
      "mcp__docs__check_flow"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as docs. Review it before you use it.

Capability tags behind 4 rules
  • mcp__docs__search_docs private-data
  • mcp__docs__read_doc private-data
  • mcp__docs__list_docs private-data
  • mcp__docs__lookup_error untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.jsonpad/docs/verify?hash=10d297228fb8c901f4267378df5d75eb059f8a771c60bbeeb2d93e4b865f944c" | jq -e '.changed == false'

Pinned hash 10d297228fb8, from Nov 18, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.jsonpad/docs/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.jsonpad/docs
[![Anlyon Radar](https://radar.anlyon.com/badge/io.jsonpad/docs.svg)](https://radar.anlyon.com/servers/io.jsonpad/docs)

Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.

JSONPad documentation MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the JSONPad documentation MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the JSONPad documentation MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the JSONPad documentation MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the JSONPad documentation MCP server have?

14 tools: 3 write, 11 read. check_write_rules, eval_write_rule, check_flow, search_docs, read_doc, list_docs, list_api_endpoints, get_api_endpoint and 6 more.

Does the JSONPad documentation MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the JSONPad documentation MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the JSONPad documentation MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.