Formpit MCP server
com.formpit/formpitformpit.comstreamable-httpv1.0.1Scanned
Form backend with an inbox: create form endpoints, read submissions and reply by email.
7 tools: 1 do something that can't be undone, 2 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 3
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Formpit MCP server can do
The Formpit MCP server is published by formpit.com, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (reply_to_submission) and create or change data (2 tools: create_form and set_status), but cannot delete data. 4 tools only read.
1 tool reads private data (get_submission); 3 tools bring in text other people can write (get_submission, reply_to_submission and get_usage); 1 tool can send data out of your system (reply_to_submission). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.1.
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.
7 tools
Can't be undone 1Claude Code: ask
reply_to_submissionEmail a reply to the person who sent a submission.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "reply_to_submission" says "reply": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "reply_to_submission" says "reply": it sends or publishes something to other people.
Description, as the server wrote it Email a reply to the person who sent a submission. This sends a real email to a real person: show the user the exact text and get their explicit go-ahead before calling. The reply only ever goes to the address the visitor entered, and their answer comes back into the same Formpit conversation. Marks the submission as replied.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 2Claude Code: ask
create_formCreate a Formpit form for an HTML form on any website, including static sites with no backend (contact form, waitlist, feedback, quote request).No findings
Why it is in this group
- The name "create_form" says "create": a word for a change.
Description, as the server wrote it Create a Formpit form for an HTML form on any website, including static sites with no backend (contact form, waitlist, feedback, quote request). Returns the endpoint to use as the form's action and a ready-to-paste HTML snippet. Submissions are emailed to the account owner and land in their Formpit inbox, with spam filtering.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
set_statusMark a submission as new, replied or closed.No findings
Why it is in this group
- The name "set_status" says "set": a word for a change.
Description, as the server wrote it Mark a submission as new, replied or closed.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_submissionRead one submission in full: every field the visitor sent, notes, tags and the email conversation so far.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_submission" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "note": it reads notes.
- untrusted-inputThe description's first sentence says "read" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Read one submission in full: every field the visitor sent, notes, tags and the email conversation so far.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_usageShow the plan, submissions used this month and replies sent in the last 24 hours.Reads text others writeNo findings
Why it is in this group
- The name "get_usage" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "show" and "reply": it reads comments, which other people can write.
Description, as the server wrote it Show the plan, submissions used this month and replies sent in the last 24 hours.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_formsList the forms on this Formpit account with their endpoints and how many submissions are unanswered.No findings
Why it is in this group
- The name "list_forms" says "list": a word for reading.
Description, as the server wrote it List the forms on this Formpit account with their endpoints and how many submissions are unanswered.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_submissionsList submissions for one form, newest first.No findings
Why it is in this group
- The name "list_submissions" says "list": a word for reading.
Description, as the server wrote it List submissions for one form, newest first. Defaults to unanswered ("new") ones.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
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.
3 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__formpit__reply_to_submission"
]
}
}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, 18:21 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://formpit.com/mcp: tools/list returned 7 tools to an anonymous client, including reply_to_submission (irreversible), create_form (write), set_status (write)
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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http formpit https://formpit.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http formpit https://formpit.com/mcp --header 'Authorization: <your-authorization>'Run 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__formpit__list_forms",
"mcp__formpit__list_submissions",
"mcp__formpit__get_submission",
"mcp__formpit__get_usage"
],
"ask": [
"mcp__formpit__create_form",
"mcp__formpit__reply_to_submission",
"mcp__formpit__set_status"
],
"deny": []
}
}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 formpit. Review it before you use it.
Capability tags behind 3 rules
- mcp__formpit__get_submission private-data, untrusted-input
- mcp__formpit__reply_to_submission untrusted-input, outbound
- mcp__formpit__get_usage 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/com.formpit/formpit/verify?hash=b44d2ca04e9966022b20d293553313c517c27feabfc6eaeb9ad318157fa7318a" | jq -e '.changed == false'Pinned hash b44d2ca04e99, from Nov 13, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.formpit/formpit/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.formpit/formpit)Source: MCP Registry. Synced Nov 13, 2026, 10:17 UTC.
Formpit MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Formpit MCP server safe?
- No scan can promise that. What its definitions show: 7 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 Formpit MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Formpit MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: reply_to_submission.
What tools does the Formpit MCP server have?
- 7 tools: 1 irreversible, 2 write, 4 read. reply_to_submission, create_form, set_status, list_forms, list_submissions, get_submission and get_usage.
Does the Formpit MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Formpit MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): reply_to_submission.
Has the Formpit MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.