Ext Ops Panel
Open dashboard
Comparison

Formhaus vs JSONPad

Formhaus is an MCP server published by ignsm. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). JSONPad is an MCP server published by jsonpad.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceFormhausJSONPad
Official MCP Registry Listed
Version: 0.3.2
Downloads/month (npm): 921
Downloads/week (npm): 921
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (npm): 163
Downloads/week (npm): 19
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Formhaus vs JSONPad
FactFormhausJSONPad
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)3No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)2026-10-14Not published
Where it runs (differs)On your machine (@formhaus/mcp)Remote server (mcp.jsonpad.io/api)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/ignsm/formhausNot stated
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Formhaus

In its own words, on Official MCP Registry:

Validate Formhaus form definitions and simulate multi-step paths against the real engine.

JSONPad

In its own words, on Official MCP Registry:

Build and run a JSONPad backend: lists, items, indexes, write rules, schema sync, history, flows.

How to run each

Formhaus As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio formhaus -- npx -y @formhaus/mcp

JSONPad As a remote MCP server

Claude Code
claude mcp add --transport http jsonpad https://mcp.jsonpad.io/api --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: JSONPAD_API_TOKEN (secret), Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Formhaus publish no settings it asks for, so we do not compare settings.

What it can do: Formhaus · What it can do: JSONPad · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built