@formhaus/mcp

MCPcommunity

v0.2.1io.github.ignsmMITUpdated 1d agonpm GitHub

MCP server for authoring and checking Formhaus form definitions: validation, path simulation and capabilities.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

3GitHub stars

1d agoLast update

Package

Authorio.github.ignsm

LicenseMIT

Version0.2.1

Sourcenpm+mcp-registry

npm@formhaus/mcp

GitHubignsm/formhaus

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface10 tools · none privileged

Security scan✓ Cleanv0.3.0 · todayHow well does this scan work?

EvalsNone

IndexedOct 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged

Statically extracted from the published packagev0.3.0 · 3h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

update_form_settingsNo description published

This tool published no description. Forge does not invent one.

get_webhookNo description published

This tool published no description. Forge does not invent one.

reveal_webhook_secretNo description published

This tool published no description. Forge does not invent one.

publish_formNo description published

This tool published no description. Forge does not invent one.

list_formsNo description published

This tool published no description. Forge does not invent one.

get_submissionsNo description published

This tool published no description. Forge does not invent one.

validate_definitionNo description published

This tool published no description. Forge does not invent one.

simulate_pathNo description published

This tool published no description. Forge does not invent one.

capabilitiesLists what a Formhaus definition supports: field types, field props, validation rules, condition operators, step and route semantics, actions and adapters. To upgrade a 0.10 project, read the formhaus://migrate/0.11 resource.

Lists what a Formhaus definition supports: field types, field props, validation rules, condition operators, step and route semantics, actions and adapters. To upgrade a 0.10 project, read the formhaus://migrate/0.11 resource.

No input schema was published for this tool.

example_definitionsWithout id, lists the bundled example definitions. With id, returns that definition.

Without id, lists the bundled example definitions. With id, returns that definition.

No input schema was published for this tool.

2 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for authoring and checking Formhaus form definitions: validation, path simulation and capabilities.

Keywords

mcpmcp-servermodel-context-protocolclaudecursorai-agentsformsform-definitionjson-formvalidationformhaus

Alternatives

Comparing tool surfaces…

Tools exposed

10 tools · none privileged · observed 2026-10-12 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

update_form_settings
get_webhook
reveal_webhook_secret
publish_form
list_forms
get_submissions
validate_definition
simulate_path
capabilities
example_definitions

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-12 — observed resolution, not a publisher declaration.

60 packages resolved · 4 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

ajv8.20.04 dependencies
- fast-deep-equal3.1.3
- fast-uri3.1.8
- json-schema-traverse1.0.0
- require-from-string2.0.2
zod4.6.6
@formhaus/core0.11.0
@modelcontextprotocol/sdk1.32.117 dependencies
- ajv8.20.0shown above
- zod4.6.6shown above
- cors2.8.6+1 not drawn1 dependency
  - object-assign4.1.1
- hono4.13.13
- jose6.2.12
- express5.3.0+28 not drawn
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5
- pkce-challenge5.0.1
- @hono/node-server2.1.4
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.1+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 50
below the depth cap: 5

es-define-property ^1.0.1 — required by qs@6.16.0package cap reached
wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.