Fillout MCP by usefulapi
io.usefulapi/filloutusefulapi.iostreamable-httpv1.40.5Scanned
Read Fillout forms and submissions, export responses, and create submissions and webhooks.
9 tools: 3 can delete or cancel things and 6 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Fillout MCP by usefulapi can do
The Fillout MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (3 tools: fillout_create_submissions, fillout_create_webhook and fillout_remove_webhook). 6 tools only read.
1 tool reads private data (fillout_list_submissions); 2 tools bring in text other people can write (fillout_get_form and fillout_list_submissions).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.5.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Deletes or cancels 3Claude Code: deny
fillout_create_submissionsCreate up to 10 new submissions on a form, as if respondents had filled it in — e.g.No findings
Why it is in this group
- The name "fillout_create_submissions" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Create submissions
- destructiveHint: true
fillout_create_webhookSubscribe a URL to a form's new submissions: Fillout will POST each submission (same shape as a fillout_list_submissions entry) to it.No findings
Why it is in this group
- The name "fillout_create_webhook" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Create a submission webhook
- destructiveHint: true
fillout_remove_webhookStop a webhook from receiving submissions.No findings
Why it is in this group
- The name "fillout_remove_webhook" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Stop a webhook from receiving submissions. Recoverable: create it again with fillout_create_webhook (it gets a new id). Fillout: POST /webhook/delete.
Annotations the server declares
- title: Remove a submission webhook
- destructiveHint: true
Only reads 6Show 6 read-only tools
fillout_count_submissionsCount a form's submissions matching the same filters as fillout_list_submissions (date range, status, search) without pulling the answers — e.g.No findings
Why it is in this group
- The name "fillout_count_submissions" says "count": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Count submissions
- readOnlyHint: true
fillout_export_submissionsFetch 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.No findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Export submissions
- readOnlyHint: true
fillout_get_formFetch one form's metadata: every question (id, name, type), calculations, URL parameters, scheduling and payment fields, and quiz settings.Reads text others writeNo findings
Why it is in this group
- The name "fillout_get_form" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get form questions and metadata
- readOnlyHint: true
fillout_get_submissionFetch a single submission by id, with every answer.No findings
Why it is in this group
- The name "fillout_get_submission" says "get": a word for reading.
Description, as the server wrote it Fetch a single submission by id, with every answer. Fillout: GET /forms/{formId}/submissions/{submissionId}.
Annotations the server declares
- title: Get one submission
- readOnlyHint: true
fillout_list_formsList every form in the Fillout account — each form's name and formId.No findings
Why it is in this group
- The name "fillout_list_forms" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List forms
- readOnlyHint: true
fillout_list_submissionsList 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 fr…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "fillout_list_submissions" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: List submissions
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://fillout.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://fillout.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://fillout.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://fillout.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.5. Values in angle brackets are yours to fill in.
claude mcp add --transport http fillout https://fillout.usefulapi.io/mcpclaude mcp add --transport http fillout https://fillout.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__fillout__fillout_list_forms",
"mcp__fillout__fillout_get_form",
"mcp__fillout__fillout_list_submissions",
"mcp__fillout__fillout_get_submission",
"mcp__fillout__fillout_count_submissions",
"mcp__fillout__fillout_export_submissions"
],
"ask": [],
"deny": [
"mcp__fillout__fillout_create_submissions",
"mcp__fillout__fillout_create_webhook",
"mcp__fillout__fillout_remove_webhook"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fillout. Review it before you use it.
Capability tags behind 2 rules
- mcp__fillout__fillout_get_form untrusted-input
- mcp__fillout__fillout_list_submissions private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/fillout/verify?hash=43740a03c27bb9522ac904451e10834876b85ddd43262884eb6c7019cf2dec10" | jq -e '.changed == false'Pinned hash 43740a03c27b, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/fillout/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/fillout)Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.
Fillout MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Fillout MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 9 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Fillout MCP by usefulapi delete data?
- Yes. 3 tools can delete, cancel or revoke something: fillout_create_submissions, fillout_create_webhook and fillout_remove_webhook.
Can the Fillout MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Fillout MCP by usefulapi have?
- 9 tools: 3 destructive, 6 read. fillout_create_submissions, fillout_create_webhook, fillout_remove_webhook, fillout_list_forms, fillout_get_form, fillout_list_submissions, fillout_get_submission, fillout_count_submissions and 1 more.
Does the Fillout MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Fillout MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Fillout MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.