Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.usefulapi/formbricks

REMOTE · FORMBRICKS.USEFULAPI.IO · SCANNED OCT 3

Read survey responses and manage contacts, webhooks, teams and organisation users.

77 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1443 tokens (~84/item across 17 items; 17 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 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

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the io.usefulapi/formbricks MCP server?

io.usefulapi/formbricks is a hosted endpoint at https://formbricks.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 · formbricks.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-formbricks 'https://formbricks.usefulapi.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-formbricks": {
      "url": "https://formbricks.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-formbricks": {
      "type": "http",
      "url": "https://formbricks.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-usefulapi-formbricks]
url = "https://formbricks.usefulapi.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-formbricks": {
      "type": "remote",
      "url": "https://formbricks.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-formbricks --url 'https://formbricks.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-formbricks:
    url: "https://formbricks.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-formbricks": {
      "Transport": "http",
      "Url": "https://formbricks.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-formbricks -t streamable-http -u 'https://formbricks.usefulapi.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-usefulapi-formbricks": {
      "type": "http",
      "url": "https://formbricks.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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 +44
    • 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 Destructive annotations: 100 functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
  • 2 Oct 26 +15
    • HTTPS: unverified → pass ▲ security
    • 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.

Diagnostics

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://formbricks.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 formbricks.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://formbricks.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://formbricks.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://formbricks.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://formbricks.usefulapi.io/mcp
Authorisation server https://formbricks.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://formbricks.usefulapi.io/mcp Verified 200
http (plaintext) http://formbricks.usefulapi.io/mcp HTTPS enforced 301 https://formbricks.usefulapi.io/mcp
MCP tools · 17 exposed · ~1,443 tokens

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 →

Tool Tokens
formbricks_create_contact ~100

Create a contact in a workspace from a set of attributes, e.g. email and userId. Formbricks v2: POST /management/contacts.

NameTypeReqDescription
attributesobjectyesAttribute key/value pairs, e.g. {"email":"a@example.com","userId":"u_1"}.
environmentIdstring–Restrict to one environment.
workspaceIdstringyesThe workspace to create the contact in.

No output schema declared.

No examples provided.

formbricks_create_webhook ~131

Register a webhook that fires on survey events. Formbricks v2: POST /management/webhooks.

NameTypeReqDescription
environmentIdstring–Restrict to one environment.
namestringyesA label for the webhook.
surveyIdsarrayyesSurveys the webhook covers. Pass an empty array for all surveys.
triggersarrayyesEvents to fire on, e.g. ["responseCreated", "responseFinished"].
urlstringyesThe HTTPS URL Formbricks should POST to.
workspaceIdstringyesThe workspace the webhook belongs to.

No output schema declared.

No examples provided.

formbricks_delete_response ~56

Delete one survey response. Irreversible — use it to honour a data-deletion request. Formbricks v2: DELETE /management/responses/{id}.

NameTypeReqDescription
response_idstringyesThe response to delete.

No output schema declared.

No examples provided.

formbricks_delete_webhook ~42

Remove a webhook. Formbricks v2: DELETE /management/webhooks/{id}.

NameTypeReqDescription
webhook_idstringyesThe webhook to delete.

No output schema declared.

No examples provided.

formbricks_get_contact_attribute_key ~50

Fetch a single contact attribute key. Formbricks v2: GET /management/contact-attribute-keys/{id}.

NameTypeReqDescription
key_idstringyesThe attribute key's id.

No output schema declared.

No examples provided.

formbricks_get_response ~51

Fetch a single survey response with its answers, metadata and completion state. Formbricks v2: GET /management/responses/{id}.

NameTypeReqDescription
response_idstringyesThe response's id.

No output schema declared.

No examples provided.

formbricks_get_survey_contact_link ~87

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}/.

NameTypeReqDescription
contact_idstringyesThe contact the link is for.
survey_idstringyesThe survey to link to.

No output schema declared.

No examples provided.

formbricks_get_survey_segment_links ~110

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}.

NameTypeReqDescription
limitinteger–Page size, 1-100.
segment_idstringyesThe segment of contacts.
skipinteger–How many records to skip (offset paging).
survey_idstringyesThe survey to link to.

No output schema declared.

No examples provided.

formbricks_get_webhook ~51

Fetch a single webhook with its URL, triggers and bound surveys. Formbricks v2: GET /management/webhooks/{id}.

NameTypeReqDescription
webhook_idstringyesThe webhook's id.

No output schema declared.

No examples provided.

formbricks_health ~30

Check that the Formbricks API is reachable. Formbricks v2: GET /health.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

formbricks_list_contact_attribute_keys ~133

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.

NameTypeReqDescription
environmentIdstring–Restrict to this environment.
limitinteger–Page size, 1-100.
orderstring–Sort direction.
skipinteger–How many records to skip (offset paging).
sortBystring–Field to sort on, e.g. createdAt or updatedAt.
workspaceIdstring–Restrict to this workspace.

No output schema declared.

No examples provided.

formbricks_list_organization_users ~110

List the users in an organisation, optionally looked up by id or email. Formbricks v2: GET /organizations/{organizationId}/users.

NameTypeReqDescription
emailstring–Only the user with this email.
idstring–Only the user with this id.
limitinteger–Page size, 1-100.
organization_idstringyesThe organisation's id.
skipinteger–How many records to skip (offset paging).

No output schema declared.

No examples provided.

formbricks_list_responses ~189

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.

NameTypeReqDescription
contactIdstring–Only responses from this contact.
endDatestring–ISO-8601 upper bound on the date field.
filterDateFieldstring–Which date field the window applies to.
limitinteger–Page size, 1-100.
orderstring–Sort direction.
skipinteger–How many records to skip (offset paging).
sortBystring–Field to sort on, e.g. createdAt or updatedAt.
startDatestring–ISO-8601 lower bound on the date field.
surveyIdstring–Only responses to this survey.

No output schema declared.

No examples provided.

formbricks_list_roles ~32

List the roles that can be assigned to organisation users. Formbricks v2: GET /roles.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

formbricks_list_teams ~105

List the teams in an organisation. Formbricks v2: GET /organizations/{organizationId}/teams.

NameTypeReqDescription
limitinteger–Page size, 1-100.
orderstring–Sort direction.
organization_idstringyesThe organisation's id.
skipinteger–How many records to skip (offset paging).
sortBystring–Field to sort on, e.g. createdAt or updatedAt.

No output schema declared.

No examples provided.

formbricks_list_webhooks ~116

List the webhooks configured to fire on survey events, optionally filtered to specific surveys. Formbricks v2: GET /management/webhooks.

NameTypeReqDescription
limitinteger–Page size, 1-100.
orderstring–Sort direction.
skipinteger–How many records to skip (offset paging).
sortBystring–Field to sort on, e.g. createdAt or updatedAt.
surveyIdsarray–Only webhooks bound to these survey ids.

No output schema declared.

No examples provided.

formbricks_whoami ~50

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.usefulapi/formbricks MCP server?

io.usefulapi/formbricks is an MCP server listed in the public MCP registry as io.usefulapi/formbricks. Read survey responses and manage contacts, webhooks, teams and organisation users. This page covers its hosted endpoint (https://formbricks.usefulapi.io/mcp).

Is the io.usefulapi/formbricks MCP server safe to use?

io.usefulapi/formbricks scores 77 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/formbricks MCP server expose?

io.usefulapi/formbricks exposes 17 tools: formbricks_health, formbricks_whoami, formbricks_list_responses, formbricks_get_response, formbricks_list_webhooks, and 12 more. Their descriptions and schemas cost roughly 1,443 tokens of context every time the server is loaded.

Does the io.usefulapi/formbricks MCP server require authentication?

Yes. io.usefulapi/formbricks 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/formbricks MCP server still maintained?

io.usefulapi/formbricks 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.