# io.usefulapi/formstack (remote · formstack.usefulapi.io)

Browse Formstack forms, submissions and webhooks, search responses, and create submissions.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `formstack.usefulapi.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-formstack/formstack.md), [page](https://verifymcp.io/servers/io-usefulapi-formstack/formstack)

## Channel facts

- Endpoint: `https://formstack.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: this server exposes a tool marked destructive (formstack_create_submission) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2234 tokens (~111/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the io.usefulapi/formstack MCP server?

io.usefulapi/formstack is a hosted endpoint at https://formstack.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-formstack 'https://formstack.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-formstack": {
      "url": "https://formstack.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-formstack": {
      "type": "http",
      "url": "https://formstack.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-formstack]
url = "https://formstack.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-formstack": {
      "type": "remote",
      "url": "https://formstack.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-formstack --url 'https://formstack.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-formstack:
    url: "https://formstack.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-formstack": {
      "Transport": "http",
      "Url": "https://formstack.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-formstack -t streamable-http -u 'https://formstack.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-formstack": {
      "type": "http",
      "url": "https://formstack.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 63, +30)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation not fully verified: this server exposes a tool marked destructive (formstack_create_submission) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-10-02 (score 33, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-10-01 (score 28, 0)

- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-09-30 (score 28, +10)

- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [security] Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- [functional] Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (20)

### `formstack_list_forms` (~135 tokens)

List forms

List the forms in the account, with submission counts, live URL and folder. Filter by name or folder and sort. Formstack: GET /forms.

Input parameters:

- `folder` (integer): Only forms in this folder ID.
- `order` (string): Sort direction (default ASC).
- `order_by` (string): Column to order by, e.g. name, created, updated.
- `page_number` (integer): Page number, starting at 1.
- `page_size` (integer): Items per page, 10-500 (Formstack default 50).
- `search` (string): Match forms by name.

### `formstack_get_form` (~69 tokens)

Get one form

Fetch a form's details — name, URL, submission counts, settings — optionally with its full field list. Formstack: GET /forms/{formId}.

Input parameters:

- `form_id` (integer, required): The form ID.
- `with_fields` (boolean): Include the form's fields in the response.

### `formstack_list_form_fields` (~66 tokens)

List a form's fields

List every field on a form — id, label, type, required flag, options and logic. Use this to learn field IDs before searching or creating submissions. Formstack: GET /forms/{formId}/fields.

Input parameters:

- `form_id` (integer, required): The form ID.

### `formstack_list_form_submissions` (~326 tokens)

List a form's submissions

List a form's submissions, newest or oldest first, filtered by keyword, date range or specific field values. Set include_data to get the answers. Formstack: GET /forms/{formId}/submissions.

Input parameters:

- `data_format` (string): Shape of data: legacy (object keyed by field id) or standardized (array of field objects).
- `encryption_password` (string): Only for forms with encryption enabled: the form's encryption password, sent as the X-FS-Encryption-Password header.
- `expand_data` (boolean): Include expanded field data with parsed values.
- `field_filters` (array): Search specific fields by value (up to 10 criteria, AND-ed).
- `form_id` (integer, required): The form ID.
- `include_data` (boolean): Include each submission's field data.
- `keyword` (string): Match submissions by content across all fields.
- `max_time` (string): Only entries created on or before this date/time: YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (Eastern Time).
- `min_time` (string): Only entries created on or after this date/time: YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (Eastern Time).
- `order` (string): Sort direction (default ASC).
- `page_number` (integer): Page number, starting at 1.
- `page_size` (integer): Items per page, 10-500 (Formstack default 50).
- `pretty_name` (boolean): Include a human-readable name per submission (from its name/email field).

### `formstack_count_form_submissions` (~102 tokens)

Count a form's submissions

Count a form's submissions, with a per-day breakdown over a lookback window of up to 7 days. Formstack: GET /forms/{formId}/submissions/count.

Input parameters:

- `form_id` (integer, required): The form ID.
- `lookback_period` (integer): How many days to count backwards (maximum 7).
- `start_date` (string): Date to count from, e.g. 2026-09-01.

### `formstack_search_submissions` (~104 tokens)

Search submissions across all forms

Full-text search for submissions across every form in the account, e.g. by a person's email or name. Formstack: GET /submissions.

Input parameters:

- `order` (string): Sort direction (default ASC).
- `page_number` (integer): Page number, starting at 1.
- `page_size` (integer): Items per page, 10-500 (Formstack default 50).
- `search` (string, required): Search term to match against submission content.

### `formstack_get_submission` (~90 tokens)

Get one submission

Fetch a single submission with every field's label, type, display value and parsed value, plus payment, approval and workflow status. Formstack: GET /submissions/{submissionId}.

Input parameters:

- `encryption_password` (string): Only for forms with encryption enabled: the form's encryption password, sent as the X-FS-Encryption-Password header.
- `submission_id` (integer, required): The submission ID.

### `formstack_list_partial_submissions` (~244 tokens)

List a form's partial submissions

List entries respondents started but did not finish (Save & Resume / abandoned), with the same filters as submissions. Formstack: GET /form/{formId}/partialsubmission.

Input parameters:

- `expand_data` (boolean): Expand data with detailed field information.
- `field_filters` (array): Search specific fields by value (up to 10 criteria, AND-ed).
- `form_id` (integer, required): The form ID.
- `include_data` (boolean): Include each partial submission's data.
- `keyword` (string): Keyword to search.
- `max_time` (string): Only entries created on or before this date/time: YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (Eastern Time).
- `min_time` (string): Only entries created on or after this date/time: YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (Eastern Time).
- `order` (string): Sort direction (default ASC).
- `page_number` (integer): Page number, starting at 1.
- `page_size` (integer): Items per page, 10-500 (Formstack default 50).
- `pretty_name` (boolean): Include pretty names.

### `formstack_list_folders` (~59 tokens)

List folders

List the account's form folders and their subfolders. Formstack: GET /folders.

Input parameters:

- `page` (integer): Page number, starting at 1.
- `per_page` (integer): Folders per page (minimum 10).

### `formstack_get_folder` (~44 tokens)

Get one folder

Fetch a folder with its parent, permissions and direct subfolders. Formstack: GET /folders/{folderId}.

Input parameters:

- `folder_id` (integer, required): The folder ID.

### `formstack_list_webhooks` (~54 tokens)

List a form's webhooks

List the webhooks that push a form's submissions to external URLs, with their payload settings. Formstack: GET /forms/{formId}/webhooks.

Input parameters:

- `form_id` (integer, required): The form ID.

### `formstack_list_notification_emails` (~57 tokens)

List a form's notification emails

List the notification emails that alert your team when a form is submitted — recipients, subject, sender and logic. Formstack: GET /forms/{formId}/notifications.

Input parameters:

- `form_id` (integer, required): The form ID.

### `formstack_list_confirmation_emails` (~57 tokens)

List a form's confirmation emails

List the confirmation emails sent to the person who submits a form — sender, subject, message and delay. Formstack: GET /forms/{formId}/confirmations.

Input parameters:

- `form_id` (integer, required): The form ID.

### `formstack_list_submit_actions` (~60 tokens)

List a form's submit actions

List what happens after a form is submitted — default processing, a custom message, or a redirect URL — with conditional logic. Formstack: GET /forms/{formId}/submitactions.

Input parameters:

- `form_id` (integer, required): The form ID.

### `formstack_create_submission` (~123 tokens)

Create a submission

Submit an entry to a form on someone's behalf. This is a real submission: it counts toward the form and can fire its notification emails, webhooks and integrations. Formstack: POST /forms/{formId}/submissions.

Input parameters:

- `fields` (array, required): Field values to submit.
- `form_id` (integer, required): The form ID.
- `read` (boolean): Mark the submission as read on creation.
- `remote_addr` (string): Submitter's IP address to record.
- `user_agent` (string): Submitter's browser user agent to record.

### `formstack_update_submission` (~116 tokens)

Update a submission

Change field values on an existing submission, or mark it read/unread. Only the fields you pass are changed. Formstack: PUT /submissions/{submissionId}.

Input parameters:

- `encryption_password` (string): Only for forms with encryption enabled: the form's encryption password, sent as the X-FS-Encryption-Password header.
- `fields` (array): Field values to change.
- `read` (boolean): Mark the submission read (true) or unread (false).
- `submission_id` (integer, required): The submission ID.

### `formstack_create_prefill_url` (~108 tokens)

Create a prefilled form link

Generate a link to a live form with some fields already filled in — e.g. to send a customer a form with their name and account number pre-entered. Formstack stores the prefill and returns prefilledUrl. Formstack: POST /forms/{formId}/prefill.

Input parameters:

- `fields` (array, required): Field values to prefill.
- `form_id` (integer, required): The form ID.
- `incomplete_password` (string): Optional password protecting the prefilled entry.

### `formstack_update_form` (~160 tokens)

Update a form's settings

Rename a form, move it to a folder, change its submit-button text, timezone or language, or activate/deactivate it (with a message shown while inactive). Reversible. Formstack: PUT /forms/{formId}.

Input parameters:

- `disabled_message` (string): Message shown while the form is inactive.
- `folder` (integer): Folder ID to move the form into.
- `form_id` (integer, required): The form ID.
- `is_active` (boolean): Turn the live form on (true) or off (false).
- `language` (string): Form language.
- `name` (string): New form name.
- `submit_button_title` (string): Submit button text on the live form.
- `timezone` (string): Form timezone.

### `formstack_create_folder` (~57 tokens)

Create a folder

Create a folder for organising forms, at the root or inside a parent folder. Formstack: POST /folders.

Input parameters:

- `name` (string, required): Folder name.
- `parent` (integer): Parent folder ID (omit for root level).

### `formstack_create_webhook` (~203 tokens)

Create a webhook

Add a webhook that POSTs each new submission of a form to your URL. Formstack: POST /forms/{formId}/webhooks.

Input parameters:

- `content_type` (string): Payload encoding.
- `error_emails` (string): Comma-separated emails to notify on delivery failure.
- `file_transfer_type` (string): How uploaded files are delivered in the payload.
- `form_id` (integer, required): The form ID.
- `hmac_secret` (string): Secret used to HMAC-sign each payload.
- `include_field_type` (boolean): Include each field's type in the payload.
- `include_subfield_names` (boolean): Include subfield names in the payload.
- `name` (string): Webhook name.
- `post_data_field_keys` (string): How fields are keyed in the payload.
- `standardize_values` (boolean): Standardize field values for consistency.
- `url` (string, required): HTTPS URL that receives the submission data.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-formstack/formstack#diagnostics

## Score history

- 2026-10-04: 63
- 2026-10-03: 33
- 2026-10-02: 33
- 2026-10-01: 28
- 2026-09-30: 28
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/formstack MCP server?

io.usefulapi/formstack is an MCP server listed in the public MCP registry as io.usefulapi/formstack. Browse Formstack forms, submissions and webhooks, search responses, and create submissions. This page covers its hosted endpoint (https://formstack.usefulapi.io/mcp).

### Is the io.usefulapi/formstack MCP server safe to use?

io.usefulapi/formstack scores 63 out of 100 on VerifyMCP. 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 io.usefulapi/formstack MCP server expose?

io.usefulapi/formstack exposes 20 tools: formstack_list_forms, formstack_get_form, formstack_list_form_fields, formstack_list_form_submissions, formstack_count_form_submissions, and 15 more. Their descriptions and schemas cost roughly 2,234 tokens of context every time the server is loaded.

### Does the io.usefulapi/formstack MCP server require authentication?

No. We connected to io.usefulapi/formstack without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.usefulapi/formstack MCP server still maintained?

io.usefulapi/formstack is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://formstack.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-formstack/formstack.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-formstack/formstack.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-formstack/formstack