Home / MCP registry index / io.usefulapi/formbricks
Formbricks MCP by usefulapi
io.usefulapi/formbricks in the official MCP registry.
Endpoint https://formbricks.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read survey responses and manage contacts, webhooks, teams and organisation users.
We read its 17 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
formbricks_health formbricks_whoami formbricks_list_responses formbricks_get_response formbricks_list_webhooks formbricks_get_webhook formbricks_list_contact_attribute_keys formbricks_get_contact_attribute_key formbricks_get_survey_contact_link formbricks_get_survey_segment_links formbricks_list_teams formbricks_list_organization_users formbricks_list_roles formbricks_create_webhook formbricks_delete_webhook formbricks_create_contact formbricks_delete_response
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-formbricks)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.