Formbricks MCP by usefulapi
io.usefulapi/formbricksusefulapi.iostreamable-httpv1.40.4Scanned
Read survey responses and manage contacts, webhooks, teams and organisation users.
17 tools: 4 can delete or cancel things, 1 change things and 12 only read.
- Reads private data · 6
- Reads text others write · 3
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
5 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 Formbricks MCP by usefulapi can do
The Formbricks MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 17 tools. It can delete or cancel things (4 tools: formbricks_create_webhook, formbricks_delete_webhook, formbricks_create_contact and formbricks_delete_response) and create or change data (1 tool: formbricks_health). 12 tools only read.
6 tools read private data (formbricks_list_responses, formbricks_list_contact_attribute_keys, formbricks_get_contact_attribute_key and 3 more); 3 tools bring in text other people can write (formbricks_get_webhook, formbricks_get_survey_contact_link and formbricks_list_organization_users).
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.4.
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.
17 tools
Deletes or cancels 4Claude Code: deny
formbricks_create_contactCreate a contact in a workspace from a set of attributes, e.g.No findings
Why it is in this group
- The name "formbricks_create_contact" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a contact in a workspace from a set of attributes, e.g. email and userId. Formbricks v2: POST /management/contacts.
Annotations the server declares
- title: Create a contact
- destructiveHint: true
formbricks_create_webhookRegister a webhook that fires on survey events.No findings
Why it is in this group
- The name "formbricks_create_webhook" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Register a webhook that fires on survey events. Formbricks v2: POST /management/webhooks.
Annotations the server declares
- title: Create a webhook
- destructiveHint: true
formbricks_delete_responseDelete one survey response.No findings
Why it is in this group
- The name "formbricks_delete_response" says "delete": a word for removing or ending something.
- The description says "Irreversible".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete one survey response. Irreversible — use it to honour a data-deletion request. Formbricks v2: DELETE /management/responses/{id}.
Annotations the server declares
- title: Delete a response
- destructiveHint: true
formbricks_delete_webhookRemove a webhook.No findings
Why it is in this group
- The name "formbricks_delete_webhook" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Remove a webhook. Formbricks v2: DELETE /management/webhooks/{id}.
Annotations the server declares
- title: Delete a webhook
- destructiveHint: true
Changes things 1Claude Code: ask
formbricks_healthCheck that the Formbricks API is reachable.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Check that the Formbricks API is reachable. Formbricks v2: GET /health.
Annotations the server declares
- title: Check API health
- readOnlyHint: true
Only reads 12Show 12 read-only tools
formbricks_get_contact_attribute_keyFetch a single contact attribute key.Reads private dataNo findings
Why it is in this group
- The name "formbricks_get_contact_attribute_key" says "get": a word for reading.
What it can reach
- private-dataThe name "formbricks_get_contact_attribute_key" says "get" and "contact": it reads contacts.
- private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
Description, as the server wrote it Fetch a single contact attribute key. Formbricks v2: GET /management/contact-attribute-keys/{id}.
Annotations the server declares
- title: Get one contact attribute key
- readOnlyHint: true
formbricks_get_responseFetch a single survey response with its answers, metadata and completion state.No findings
Why it is in this group
- The name "formbricks_get_response" says "get": a word for reading.
Description, as the server wrote it Fetch a single survey response with its answers, metadata and completion state. Formbricks v2: GET /management/responses/{id}.
Annotations the server declares
- title: Get one response
- readOnlyHint: true
formbricks_get_survey_contact_linkGet the personalised survey URL for one contact — the link you send so their response is attributed to them.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "formbricks_get_survey_contact_link" says "get": a word for reading.
What it can reach
- private-dataThe name "formbricks_get_survey_contact_link" says "get" and "contact": it reads contacts.
- private-dataThe description's first sentence says "get" and "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Get the personalised survey URL for one contact — the link you send so their response is attributed to them. Formbricks v2: GET /management/surveys/{surveyId}/contact-links/contacts/{contactId}/.
Annotations the server declares
- title: Get a personal survey link for a contact
- readOnlyHint: true
formbricks_get_survey_segment_linksGet personalised survey URLs for every contact in a segment — how you run a targeted send.Reads private dataNo findings
Why it is in this group
- The name "formbricks_get_survey_segment_links" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "contact": it reads contacts.
Description, as the server wrote it Get personalised survey URLs for every contact in a segment — how you run a targeted send. Formbricks v2: GET /management/surveys/{surveyId}/contact-links/segments/{segmentId}.
Annotations the server declares
- title: Get personal survey links for a segment
- readOnlyHint: true
formbricks_get_webhookFetch a single webhook with its URL, triggers and bound surveys.Reads text others writeNo findings
Why it is in this group
- The name "formbricks_get_webhook" 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 a single webhook with its URL, triggers and bound surveys. Formbricks v2: GET /management/webhooks/{id}.
Annotations the server declares
- title: Get one webhook
- readOnlyHint: true
formbricks_list_contact_attribute_keysList the contact attribute keys defined in an environment — the schema of what you know about a contact.Reads private dataNo findings
Why it is in this group
- The name "formbricks_list_contact_attribute_keys" says "list": a word for reading.
What it can reach
- private-dataThe name "formbricks_list_contact_attribute_keys" says "list" and "contact": it reads contacts.
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
Description, as the server wrote it List the contact attribute keys defined in an environment — the schema of what you know about a contact. Formbricks v2: GET /management/contact-attribute-keys.
Annotations the server declares
- title: List contact attribute keys
- readOnlyHint: true
formbricks_list_organization_usersList the users in an organisation, optionally looked up by id or email.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "formbricks_list_organization_users" 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 "email": it reads inbound email, which other people can write.
Description, as the server wrote it List the users in an organisation, optionally looked up by id or email. Formbricks v2: GET /organizations/{organizationId}/users.
Annotations the server declares
- title: List organisation users
- readOnlyHint: true
formbricks_list_responsesList survey responses, optionally narrowed to one survey, one contact or a date window.Reads private dataNo findings
Why it is in this group
- The name "formbricks_list_responses" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
Description, as the server wrote it List survey responses, optionally narrowed to one survey, one contact or a date window. This is the main read: the answers people gave. Formbricks v2: GET /management/responses.
Annotations the server declares
- title: List survey responses
- readOnlyHint: true
formbricks_list_rolesList the roles that can be assigned to organisation users.No findings
Why it is in this group
- The name "formbricks_list_roles" says "list": a word for reading.
Description, as the server wrote it List the roles that can be assigned to organisation users. Formbricks v2: GET /roles.
Annotations the server declares
- title: List roles
- readOnlyHint: true
formbricks_list_teamsList the teams in an organisation.No findings
Why it is in this group
- The name "formbricks_list_teams" says "list": a word for reading.
Description, as the server wrote it List the teams in an organisation. Formbricks v2: GET /organizations/{organizationId}/teams.
Annotations the server declares
- title: List teams
- readOnlyHint: true
formbricks_list_webhooksList the webhooks configured to fire on survey events, optionally filtered to specific surveys.No findings
Why it is in this group
- The name "formbricks_list_webhooks" says "list": a word for reading.
Description, as the server wrote it List the webhooks configured to fire on survey events, optionally filtered to specific surveys. Formbricks v2: GET /management/webhooks.
Annotations the server declares
- title: List webhooks
- readOnlyHint: true
formbricks_whoamiReturn the project and environment the configured x-api-key belongs to — the fastest way to find the workspace and environment ids the other tools need.No findings
Why it is in this group
- The name "formbricks_whoami" says "whoami": a word for reading.
Description, as the server wrote it Return the project and environment the configured x-api-key belongs to — the fastest way to find the workspace and environment ids the other tools need. Formbricks v2: GET /me.
Annotations the server declares
- title: Identify the configured key
- 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 data6
- 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 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: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://formbricks.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://formbricks.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: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://formbricks.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://formbricks.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.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http formbricks https://formbricks.usefulapi.io/mcpclaude mcp add --transport http formbricks https://formbricks.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__formbricks__formbricks_whoami",
"mcp__formbricks__formbricks_list_responses",
"mcp__formbricks__formbricks_get_response",
"mcp__formbricks__formbricks_list_webhooks",
"mcp__formbricks__formbricks_get_webhook",
"mcp__formbricks__formbricks_list_contact_attribute_keys",
"mcp__formbricks__formbricks_get_contact_attribute_key",
"mcp__formbricks__formbricks_get_survey_contact_link",
"mcp__formbricks__formbricks_get_survey_segment_links",
"mcp__formbricks__formbricks_list_teams",
"mcp__formbricks__formbricks_list_organization_users",
"mcp__formbricks__formbricks_list_roles"
],
"ask": [
"mcp__formbricks__formbricks_health"
],
"deny": [
"mcp__formbricks__formbricks_create_webhook",
"mcp__formbricks__formbricks_delete_webhook",
"mcp__formbricks__formbricks_create_contact",
"mcp__formbricks__formbricks_delete_response"
]
}
}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 formbricks. Review it before you use it.
Capability tags behind 7 rules
- mcp__formbricks__formbricks_list_responses private-data
- mcp__formbricks__formbricks_get_webhook untrusted-input
- mcp__formbricks__formbricks_list_contact_attribute_keys private-data
- mcp__formbricks__formbricks_get_contact_attribute_key private-data
- mcp__formbricks__formbricks_get_survey_contact_link private-data, untrusted-input
- mcp__formbricks__formbricks_get_survey_segment_links private-data
- mcp__formbricks__formbricks_list_organization_users 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/formbricks/verify?hash=9ee242cc6c612cb732e2a0532f15891e1e9b27a893a5f1fe790a4e220cc6298a" | jq -e '.changed == false'Pinned hash 9ee242cc6c61, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/formbricks/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/formbricks)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Formbricks MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Formbricks MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 17 tools, 5 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 Formbricks MCP by usefulapi delete data?
- Yes. 4 tools can delete, cancel or revoke something: formbricks_create_webhook, formbricks_delete_webhook, formbricks_create_contact and formbricks_delete_response.
Can the Formbricks 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 Formbricks MCP by usefulapi have?
- 17 tools: 4 destructive, 1 write, 12 read. formbricks_create_webhook, formbricks_delete_webhook, formbricks_create_contact, formbricks_delete_response, formbricks_health, formbricks_whoami, formbricks_list_responses, formbricks_get_response and 9 more.
Does the Formbricks MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Formbricks 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 Formbricks MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.