formslist-mcp

MCPcommunity
v0.3.1UnknownMITUpdated 1d agonpmGitHub

FormsList MCP server: agents create live form endpoints with no signup, configure them and read submissions.

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 →
57Downloads/wk
1d agoLast update
Reads these credentials
  • FORMSLIST_API_KEYAPI keyoptional

    Optional. instant_provision returns one automatically; set it to manage existing forms.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseMIT
Version0.3.1
Sourcenpm+mcp-registry
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 surface8 tools · none privileged
Security scan✓ Cleanv0.3.1 · todayHow well does this scan work?
EvalsNone
IndexedSep 27, 2026

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

Tools

8 tools · none privileged
Statically extracted from the published packagev0.3.1 · 16h 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.

instant_provisionCreate a working form endpoint instantly for any email — no account needed.

Create a working form endpoint instantly for any email — no account needed.

No input schema was published for this tool.

create_formCreate a new form in the authenticated FormsList account. Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.

Create a new form in the authenticated FormsList account. Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.

No input schema was published for this tool.

list_formsList all forms in the authenticated FormsList account. Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.

List all forms in the authenticated FormsList account. Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.

No input schema was published for this tool.

get_formGet details of a single form (settings, endpoint, submission counts). Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.

Get details of a single form (settings, endpoint, submission counts). Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.

No input schema was published for this tool.

get_submissionsGet submissions for a form, paginated. Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.

Get submissions for a form, paginated. Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.

No input schema was published for this tool.

configure_autoresponseEnable, disable, or configure the auto-response email sent to people who submit a form.

Enable, disable, or configure the auto-response email sent to people who submit a form.

No input schema was published for this tool.

update_formUpdate a form's settings: name, notification recipients, active state, and server-side

Update a form's settings: name, notification recipients, active state, and server-side

No input schema was published for this tool.

get_embed_snippetBuild a ready-to-paste HTML form snippet (plus an AJAX fetch example) that posts to a FormsList

Build a ready-to-paste HTML form snippet (plus an AJAX fetch example) that posts to a FormsList

No input schema was published for this tool.

8 of 8 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

FormsList MCP server: agents create live form endpoints with no signup, configure them and read submissions.

Keywords
ai-agentsclaudecontact-formcursorform-backendformsformslistformspree-alternativemcpmcp-servermodel-context-protocol
Alternatives
Comparing tool surfaces…

Dependency tree

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

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

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

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

+42 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.