FormsList
NPM · FORMSLIST-MCP · 2 COMPONENTS
Form backend for AI agents: create live form endpoints, configure them, read submissions.
Available components
Last scanned (3 hours ago)
Scores higher than 48% of npm servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 39 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 977 tokens (~122/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/formslist-mcp@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
configure_autoresponse ~151
Enable, disable, or configure the auto-response email sent to people who submit a form. Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY. Auto-responses are a paid-plan feature: if the account's plan does not include them, the result contains the upgrade message and upgrade_url to relay to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| body_html | string | – | HTML body of the auto-response email |
| enabled | boolean | yes | Whether the auto-response email is enabled |
| form_id | string | yes | The form ID |
| from_name | string | – | Sender display name for the auto-response email |
| subject | string | – | Subject line of the auto-response email |
No output schema declared.
No examples provided.
create_form ~61
Create a new form in the authenticated FormsList account. Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description of the form |
| name | string | yes | Name of the form |
No output schema declared.
No examples provided.
get_embed_snippet ~113
Build a ready-to-paste HTML form snippet (plus an AJAX fetch example) that posts to a FormsList endpoint. Pure local generation — no API key, no network. Pass either the full endpoint URL (https://formslist.com/f/<hash>) or just the form hash.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_or_hash | string | yes | Full FormsList endpoint URL (…/f/<hash>) or just the form hash |
| fields | array | – | Form field names to include (default: name, email, message) |
No output schema declared.
No examples provided.
get_form ~52
Get details of a single form (settings, endpoint, submission counts). Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| form_id | string | yes | The form ID |
No output schema declared.
No examples provided.
get_submissions ~72
Get submissions for a form, paginated. Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| form_id | string | yes | The form ID |
| page | integer | – | Page number (default 1) |
| per_page | integer | – | Results per page |
No output schema declared.
No examples provided.
instant_provision ~125
Create a working form endpoint instantly for any email — no account needed. The owner claims it later via the claim_url. Returns the endpoint URL, claim_url, a ready-to-paste html_snippet, a curl_example, and a scoped api_key. This server remembers that key, so every other tool here (list_forms, get_submissions, configure_autoresponse, ...) works immediately afterwards without any human setup.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address of the future form owner (receives submission notifications) | |
| form_name | string | – | Optional name for the form |
No output schema declared.
No examples provided.
list_forms ~37
List all forms in the authenticated FormsList account. Requires an API key — call instant_provision first, or set FORMSLIST_API_KEY.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_form ~203
Update a form's settings: name, notification recipients, active state, and server-side field validation. Requires an API key (call instant_provision first, or set FORMSLIST_API_KEY). Paid-plan fields (redirect_url, allowed_domains) return an upgrade message and upgrade_url to relay to the user instead of failing.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_domains | array | – | PAID: origins allowed to post |
| email_notifications | boolean | – | Turn submission emails on or off |
| form_id | string | yes | The form ID |
| is_active | boolean | – | false makes the endpoint return 404 |
| name | string | – | New display name |
| notification_emails | array | – | Who receives each submission by email. An ARRAY, e.g. ["owner@site.com"] |
| redirect_url | string | – | PAID: where visitors land after submitting |
| validation_rules | – | – | Server-side validation; failing submissions get 422 with per-field errors. null clears. |
No output schema declared.
No examples provided.
How do I install the FormsList MCP server?
FormsList runs locally as an npm package, launched with npx -y formslist-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · formslist-mcp
claude mcp add com-formslist-mcp -- npx -y formslist-mcp
What is the FormsList MCP server?
FormsList is an MCP server listed in the public MCP registry as com.formslist/mcp. Form backend for AI agents: create live form endpoints, configure them, read submissions. This page covers its npm package (formslist-mcp).
Is the FormsList MCP server safe to use?
FormsList scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 FormsList MCP server expose?
FormsList exposes 8 tools: instant_provision, create_form, list_forms, get_form, get_submissions, and 3 more. Their descriptions and schemas cost roughly 814 tokens of context every time the server is loaded.
Is the FormsList MCP server still maintained?
FormsList is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the FormsList MCP server under?
FormsList declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.