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

Read Fillout forms and submissions, export responses, and create submissions and webhooks.

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

## Components

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

## Channel facts

- Endpoint: `https://fillout.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-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1328 tokens (~147/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 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.

## Install

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

io.usefulapi/fillout is a hosted endpoint at https://fillout.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-fillout 'https://fillout.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-fillout": {
      "type": "http",
      "url": "https://fillout.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-03 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-02 (score 75, +42)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [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 Schema quality: fail
- [functional] First check of Destructive annotations: 100
- [functional] First check of Tool coverage: 100

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

- [security improvement] HTTPS: unverified → pass

### 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.

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

First indexed and scored.

## MCP tools (9)

### `fillout_list_forms` (~46 tokens)

List forms

List every form in the Fillout account — each form's name and formId. Start here to find the formId the other tools need. Fillout: GET /forms.

### `fillout_get_form` (~93 tokens)

Get form questions and metadata

Fetch one form's metadata: every question (id, name, type), calculations, URL parameters, scheduling and payment fields, and quiz settings. Use the question ids to read answers or to create submissions. Fillout: GET /forms/{formId}.

Input parameters:

- `formId` (string, required): The form's public id (the formId from fillout_list_forms, also the id in the form's share URL).

### `fillout_list_submissions` (~293 tokens)

List submissions

List one page of a form's submissions (answers to every question, calculations, URL parameters, scheduling, payments, quiz score, login email), filtered by date range, status or free-text search. Offset pagination: the response carries totalResponses and pageCount. Fillout: GET /forms/{formId}/submissions.

Input parameters:

- `afterDate` (string): Only submissions submitted after this ISO 8601 date-time, e.g. 2026-09-01T00:00:00Z.
- `beforeDate` (string): Only submissions submitted before this ISO 8601 date-time.
- `formId` (string, required): The form's public id (the formId from fillout_list_forms, also the id in the form's share URL).
- `includeEditLink` (boolean): Include an editLink for each submission.
- `includePreview` (boolean): Also include preview (test) responses.
- `limit` (integer): Submissions per page, 1-150 (Fillout default 50).
- `offset` (integer): Starting position (0-based) for this page.
- `search` (string): Only submissions containing this text.
- `sort` (string): Sort by submission time: 'asc' (default) or 'desc' for newest first.
- `status` (string): 'finished' (default) or 'in_progress' for unfinished / partial submissions.

### `fillout_get_submission` (~100 tokens)

Get one submission

Fetch a single submission by id, with every answer. Fillout: GET /forms/{formId}/submissions/{submissionId}.

Input parameters:

- `formId` (string, required): The form's public id (the formId from fillout_list_forms, also the id in the form's share URL).
- `includeEditLink` (boolean): Include an editLink for the submission.
- `submissionId` (string, required): The submission's id (submissionId).

### `fillout_count_submissions` (~213 tokens)

Count submissions

Count a form's submissions matching the same filters as fillout_list_submissions (date range, status, search) without pulling the answers — e.g. 'how many responses this week?' or 'how many partial submissions?'. Reads totalResponses from GET /forms/{formId}/submissions with limit=1.

Input parameters:

- `afterDate` (string): Only submissions submitted after this ISO 8601 date-time, e.g. 2026-09-01T00:00:00Z.
- `beforeDate` (string): Only submissions submitted before this ISO 8601 date-time.
- `formId` (string, required): The form's public id (the formId from fillout_list_forms, also the id in the form's share URL).
- `includePreview` (boolean): Also include preview (test) responses.
- `search` (string): Only submissions containing this text.
- `status` (string): 'finished' (default) or 'in_progress' for unfinished / partial submissions.

### `fillout_export_submissions` (~268 tokens)

Export submissions

Fetch many submissions in one call by walking the offset pagination (150 per page, paced under Fillout's 5 requests/second limit), up to max_submissions. Same filters as fillout_list_submissions. Use this for analysis across a whole response set; the result says whether it was truncated. Fillout: GET /forms/{formId}/submissions (repeated).

Input parameters:

- `afterDate` (string): Only submissions submitted after this ISO 8601 date-time, e.g. 2026-09-01T00:00:00Z.
- `beforeDate` (string): Only submissions submitted before this ISO 8601 date-time.
- `formId` (string, required): The form's public id (the formId from fillout_list_forms, also the id in the form's share URL).
- `includePreview` (boolean): Also include preview (test) responses.
- `max_submissions` (integer): Stop after this many submissions (default 500, max 3000).
- `search` (string): Only submissions containing this text.
- `sort` (string): 'asc' (default, oldest first) or 'desc'.
- `status` (string): 'finished' (default) or 'in_progress' for unfinished / partial submissions.

### `fillout_create_submissions` (~137 tokens)

Create submissions

Create up to 10 new submissions on a form, as if respondents had filled it in — e.g. to import responses collected elsewhere. Each submission needs its question answers (question ids from fillout_get_form); URL parameters, scheduling, payments, login email and timestamps are optional. Creates real records that trigger the form's integrations. Fillout: POST /forms/{formId}/submissions.

Input parameters:

- `formId` (string, required): The form's public id (the formId from fillout_list_forms, also the id in the form's share URL).
- `submissions` (array, required): 1-10 submissions to create.

### `fillout_create_webhook` (~116 tokens)

Create a submission webhook

Subscribe a URL to a form's new submissions: Fillout will POST each submission (same shape as a fillout_list_submissions entry) to it. Returns the webhook id — keep it, it is the only handle for removing the webhook later. Fillout: POST /webhook/create.

Input parameters:

- `formId` (string, required): The form's public id (the formId from fillout_list_forms, also the id in the form's share URL).
- `url` (string, required): The HTTPS endpoint that should receive submissions.

### `fillout_remove_webhook` (~62 tokens)

Remove a submission webhook

Stop a webhook from receiving submissions. Recoverable: create it again with fillout_create_webhook (it gets a new id). Fillout: POST /webhook/delete.

Input parameters:

- `webhookId` (required): The webhook id returned by fillout_create_webhook.

## Diagnostics

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

## Score history

- 2026-10-03: 76
- 2026-10-02: 75
- 2026-10-01: 33
- 2026-09-30: 28
- 2026-09-29: 18

## Common questions

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

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

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

io.usefulapi/fillout scores 76 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/fillout MCP server expose?

io.usefulapi/fillout exposes 9 tools: fillout_list_forms, fillout_get_form, fillout_list_submissions, fillout_get_submission, fillout_count_submissions, and 4 more. Their descriptions and schemas cost roughly 1,328 tokens of context every time the server is loaded.

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

Yes. io.usefulapi/fillout asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

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

io.usefulapi/fillout is still listed as active in the MCP registry. We last reached this channel on 3 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://fillout.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-fillout/fillout.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-fillout/fillout.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-fillout/fillout