io.usefulapi/fillout
REMOTE · FILLOUT.USEFULAPI.IO · SCANNED OCT 3
Read Fillout forms and submissions, export responses, and create submissions and webhooks.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · fillout.usefulapi.io
claude mcp add --transport http io-usefulapi-fillout 'https://fillout.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-fillout": {
"url": "https://fillout.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-fillout": {
"type": "http",
"url": "https://fillout.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-fillout] url = "https://fillout.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-fillout": {
"type": "remote",
"url": "https://fillout.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-fillout --url 'https://fillout.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-fillout:
url: "https://fillout.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-fillout": {
"Transport": "http",
"Url": "https://fillout.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-fillout -t streamable-http -u 'https://fillout.usefulapi.io/mcp'
{
"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.
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.
- 3 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Oct 26 +42
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- 30 Sept 26 +10
- 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
- 29 Sept 26 18
First indexed and scored.
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 3 Oct 2026 · Probed https://fillout.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fillout.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://fillout.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://fillout.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://fillout.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://fillout.usefulapi.io/mcp |
| Authorisation server | https://fillout.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fillout.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://fillout.usefulapi.io/mcp | HTTPS enforced | 301 | https://fillout.usefulapi.io/mcp |
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 →
fillout_count_submissions Count submissions ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
fillout_create_submissions Create submissions ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| formId | string | yes | The form's public id (the formId from fillout_list_forms, also the id in the form's share URL). |
| submissions | array | yes | 1-10 submissions to create. |
No output schema declared.
No examples provided.
fillout_create_webhook Create a submission webhook ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| formId | string | yes | The form's public id (the formId from fillout_list_forms, also the id in the form's share URL). |
| url | string | yes | The HTTPS endpoint that should receive submissions. |
No output schema declared.
No examples provided.
fillout_export_submissions Export submissions ~268
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
fillout_get_form Get form questions and metadata ~93
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| formId | string | yes | The form's public id (the formId from fillout_list_forms, also the id in the form's share URL). |
No output schema declared.
No examples provided.
fillout_get_submission Get one submission ~100
Fetch a single submission by id, with every answer. Fillout: GET /forms/{formId}/submissions/{submissionId}.
| Name | Type | Req | Description |
|---|---|---|---|
| formId | string | yes | 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 | yes | The submission's id (submissionId). |
No output schema declared.
No examples provided.
fillout_list_forms List forms ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fillout_list_submissions List submissions ~293
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
fillout_remove_webhook Remove a submission webhook ~62
Stop a webhook from receiving submissions. Recoverable: create it again with fillout_create_webhook (it gets a new id). Fillout: POST /webhook/delete.
| Name | Type | Req | Description |
|---|---|---|---|
| webhookId | – | yes | The webhook id returned by fillout_create_webhook. |
No output schema declared.
No examples provided.
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.