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.

FoxForm

REMOTE · MCP.FOXFORM.APP · SCANNED SEP 21

Build, publish and read scored forms and quizzes where the score picks the next screen.

Available components

+3 this week 85 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 Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3474 tokens (~347/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 74% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the FoxForm MCP server?

FoxForm is a hosted endpoint at https://mcp.foxform.app/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 · mcp.foxform.app

# add to Claude Code
claude mcp add --transport http vitorrocha-panda-foxform 'https://mcp.foxform.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "vitorrocha-panda-foxform": {
      "url": "https://mcp.foxform.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vitorrocha-panda-foxform": {
      "type": "http",
      "url": "https://mcp.foxform.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.vitorrocha-panda-foxform]
url = "https://mcp.foxform.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vitorrocha-panda-foxform": {
      "type": "remote",
      "url": "https://mcp.foxform.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vitorrocha-panda-foxform --url 'https://mcp.foxform.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  vitorrocha-panda-foxform:
    url: "https://mcp.foxform.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vitorrocha-panda-foxform": {
      "Transport": "http",
      "Url": "https://mcp.foxform.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add vitorrocha-panda-foxform -t streamable-http -u 'https://mcp.foxform.app/mcp'
// mcp.json
{
  "mcpServers": {
    "vitorrocha-panda-foxform": {
      "type": "http",
      "url": "https://mcp.foxform.app/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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

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 21 Sept 2026 · Probed https://mcp.foxform.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.foxform.app CN=Amazon RSA 2048 M04,O=Amazon,C=US 22 Jun 2026 5 Jan 2027 RSA 2048 SHA256-RSA ec9b48ddc76df8d769669130f191196
SANs: mcp.foxform.app, mcp-staging.foxform.app
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.foxform.app. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
foxform.app. 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 resource_metadata="https://mcp.foxform.app/.well-known/oauth-protected-resource", scope="forms:read forms:write"

Bearer resource_metadata="https://mcp.foxform.app/.well-known/oauth-protected-resource", scope="forms:read forms:write"

Protected resource metadata

Document https://mcp.foxform.app/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.foxform.app/mcp
Authorisation server https://mcp.foxform.app

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.foxform.app/mcp Verified 200
http (plaintext) http://mcp.foxform.app/mcp HTTPS enforced
MCP tools · 10 exposed · ~3,474 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
foxform_create_form ~839

Create a new form, including per-screen conditional logic. Requires a WRITE-scoped API key. Args: - title (string): form title (required) - description (string, optional) - theme (string, optional): one of midnight|ocean|sunset|forest|lavender|minimal (default sunset = Ember) - questions (array, optional): array of screen objects ({ id, type, title, required, variableName?, choices?, logic?, ... }); omit to start empty - thank_you_message (string, optional) Returns: { form } with the created form (including its id and slug). The form starts as a draft — call foxform_publish_form to make it live. Screen fields are validated: unknown fields are REJECTED instead of being stored and ignored, and branching rules are cross-checked against the screen ids in the same payload. CONDITIONAL LOGIC (branching), per screen — stored in `questions[].logic`: logic.conditionalNavigationV2 = { enabled: true, groups: [ // groups are OR-joined; FIRST matching group wins { id: "grp-1", conditions: [ // conditions inside a group are AND-joined { id: "cond-1", left: "{{quer_testar}}", operator: "equal_to", right: "Ainda não" } ], then: { type: "specific_screen", targetScreenId: "s-motivos" } } ] } - `then.type`: 'next_screen' | 'previous_screen' | 'specific_screen' (needs targetScreenId = another screen's `id`) | 'end_form'. Add `then.url` (+ optional `openNewTab`) to redirect to an external URL instead. - `operator`: 'equal_to' | 'not_equal_to' | 'greater_than' | 'greater_or_equal_than' | 'less_than' | 'less_or_equal_than' | 'contains'. - `left`/`right` are EXPRESSION strings: a literal ("10", "Ainda não"), a variable ("{{score}}", "{{minha_var}}" = the screen's `variableName`), or arithmetic ("calc({{peso}}/(({{altura}}/100)*({{altura}}/100)))"). - Comparing an ANSWER: use `left: "{{<variableName of the deciding screen>}}"` and `right` = the option's `label` OR its…

NameTypeReqDescription
descriptionstringOptional description
questionsarrayScreen objects; omit for an empty form. Conditional logic goes in each screen's `logic` (see the tool description).
thank_you_messagestring
themestringTheme key (default sunset/Ember)
titlestringyesForm title

No output schema declared.

No examples provided.

foxform_export_responses ~73

Export all responses for a form as CSV text (one row per response, columns = questions). Large exports are truncated — use foxform_list_responses with pagination for very large datasets. Args: - form_id (string) Returns: raw CSV text.

NameTypeReqDescription
form_idstringyesForm ID

No output schema declared.

No examples provided.

foxform_get_form ~837

Fetch a single form by ID, including its full question list, per-screen conditional logic and settings. Args: - form_id (string): the form's ID (from foxform_list_forms) - response_format ('markdown' | 'json') Returns { form, public_url }: the full form object (id, title, description, slug, status, theme, questions[], thank_you_message, timestamps) plus `public_url` — the public link (`https://forms.foxform.app/<slug>`), which is live only when status is 'published'. Use `public_url` verbatim; never build the URL yourself (the public domain is forms.foxform.app, not foxform.app). Each screen in `questions[]` carries its own `logic` (branching / conditional display) and, for choice screens, `choices[]`/`images[]` with their `points` and `value`. The markdown output summarises every rule; use response_format 'json' to get the exact stored objects (that's the shape foxform_update_form expects back). CONDITIONAL LOGIC (branching), per screen — stored in `questions[].logic`: logic.conditionalNavigationV2 = { enabled: true, groups: [ // groups are OR-joined; FIRST matching group wins { id: "grp-1", conditions: [ // conditions inside a group are AND-joined { id: "cond-1", left: "{{quer_testar}}", operator: "equal_to", right: "Ainda não" } ], then: { type: "specific_screen", targetScreenId: "s-motivos" } } ] } - `then.type`: 'next_screen' | 'previous_screen' | 'specific_screen' (needs targetScreenId = another screen's `id`) | 'end_form'. Add `then.url` (+ optional `openNewTab`) to redirect to an external URL instead. - `operator`: 'equal_to' | 'not_equal_to' | 'greater_than' | 'greater_or_equal_than' | 'less_than' | 'less_or_equal_than' | 'contains'. - `left`/`right` are EXPRESSION strings: a literal ("10", "Ainda não"), a variable ("{{score}}", "{{minha_var}}" = the screen's `variableName`), or arithmetic ("calc({{peso}}/(({{altura}}/100)*({{altura}}/100)))…

NameTypeReqDescription
form_idstringyesForm ID
response_formatstringOutput format: 'markdown' (human-readable) or 'json' (machine-readable)

No output schema declared.

No examples provided.

foxform_get_form_analytics ~146

Aggregated analytics for a form: overview KPIs (total responses, form views, response rate, avg response time), the responses-over-time timeline, and per-question stats. Args: - form_id (string) - response_format ('markdown' | 'json') Returns: { overview, timeline: [{date,count}], questions: [...], response_time_distribution?, views_timeline? }. Note: form_views / response_rate are null until the form has tracked views (forward-only).

NameTypeReqDescription
form_idstringyesForm ID
response_formatstringOutput format: 'markdown' (human-readable) or 'json' (machine-readable)

No output schema declared.

No examples provided.

foxform_get_response ~97

Fetch one response by its ID (from foxform_list_responses). Args: - response_id (string) - response_format ('markdown' | 'json') Returns the full response object (id, form_id, answers, submitted_at, metadata).

NameTypeReqDescription
response_formatstringOutput format: 'markdown' (human-readable) or 'json' (machine-readable)
response_idstringyesResponse ID

No output schema declared.

No examples provided.

foxform_list_forms ~248

List the forms owned by the authenticated FoxForm account, newest first. Args: - page (number): 1-based page number (default 1) - limit (number): page size, 1-100 (default 20) - response_format ('markdown' | 'json'): output format (default markdown) Returns: { total, page, limit, count, forms: [{ id, title, status, slug, public_url, questions_count, updated_at }] } The public link of a form is `public_url` (`https://forms.foxform.app/<slug>`) — always use this exact value, do NOT build the URL yourself (the public domain is forms.foxform.app, not foxform.app). `public_url` is only live when `status` is 'published'. Use this first to discover form IDs, then call foxform_get_form / foxform_get_form_analytics.

NameTypeReqDescription
limitintegerPage size (1-100)
pageinteger1-based page number
response_formatstringOutput format: 'markdown' (human-readable) or 'json' (machine-readable)

No output schema declared.

No examples provided.

foxform_list_responses ~173

List submitted responses for a form, newest first. Args: - form_id (string): the form's ID - page (number): 1-based page (default 1) - limit (number): page size, 1-100 (default 20) - response_format ('markdown' | 'json') Returns: { total, page, limit, count, responses: [{ id, submitted_at, answers }] }. For aggregate metrics use foxform_get_form_analytics; for a full dump use foxform_export_responses.

NameTypeReqDescription
form_idstringyesForm ID
limitinteger
pageinteger
response_formatstringOutput format: 'markdown' (human-readable) or 'json' (machine-readable)

No output schema declared.

No examples provided.

foxform_publish_form ~143

Publish a form so it's live at its public URL and can accept responses. Requires a WRITE-scoped API key. Args: - form_id (string) Returns: { form, public_url } — the published form (status 'published') and its live public link `https://forms.foxform.app/<slug>`. When sharing the link with the user, use `public_url` EXACTLY as returned; do NOT build the URL yourself (the public domain is forms.foxform.app, NOT foxform.app or the API/app domain). (May fail with a plan-limit error on Free accounts.)

NameTypeReqDescription
form_idstringyesForm ID

No output schema declared.

No examples provided.

foxform_unpublish_form ~57

Unpublish a form (takes it offline; stops accepting responses). Requires a WRITE-scoped API key. Args: - form_id (string) Returns: a confirmation message.

NameTypeReqDescription
form_idstringyesForm ID

No output schema declared.

No examples provided.

foxform_update_form ~861

Update an existing form's fields, including each screen's conditional logic (branching). Requires a WRITE-scoped API key. Only the fields you pass are changed. Args: - form_id (string): the form to update (required) - title (string, optional) - description (string, optional) - theme (string, optional) - questions (array, optional): replaces the FULL screen list — there is no per-screen patch. To add logic to one screen: call foxform_get_form with response_format 'json', edit that screen's `logic`, and send the whole array back. - thank_you_message (string, optional) Returns: { form } with the updated form. Screen fields are validated: unknown fields are REJECTED instead of being stored and ignored (the API accepts arbitrary keys but no renderer reads them), `then.targetScreenId` must be the id of a screen in the same payload, and `{{variables}}` that no screen exposes come back as warnings. CONDITIONAL LOGIC (branching), per screen — stored in `questions[].logic`: logic.conditionalNavigationV2 = { enabled: true, groups: [ // groups are OR-joined; FIRST matching group wins { id: "grp-1", conditions: [ // conditions inside a group are AND-joined { id: "cond-1", left: "{{quer_testar}}", operator: "equal_to", right: "Ainda não" } ], then: { type: "specific_screen", targetScreenId: "s-motivos" } } ] } - `then.type`: 'next_screen' | 'previous_screen' | 'specific_screen' (needs targetScreenId = another screen's `id`) | 'end_form'. Add `then.url` (+ optional `openNewTab`) to redirect to an external URL instead. - `operator`: 'equal_to' | 'not_equal_to' | 'greater_than' | 'greater_or_equal_than' | 'less_than' | 'less_or_equal_than' | 'contains'. - `left`/`right` are EXPRESSION strings: a literal ("10", "Ainda não"), a variable ("{{score}}", "{{minha_var}}" = the screen's `variableName`), or arithmetic ("calc({{peso}}/(({{altura}}/100)*({{altura}}/100…

NameTypeReqDescription
descriptionstring
form_idstringyesForm ID
questionsarrayReplaces the full screen list. Conditional logic goes in each screen's `logic` (see the tool description).
thank_you_messagestring
themestring
titlestring

No output schema declared.

No examples provided.

Common questions

What is the FoxForm MCP server?

FoxForm is an MCP server listed in the public MCP registry as io.github.vitorrocha-panda/foxform. Build, publish and read scored forms and quizzes where the score picks the next screen. This page covers its hosted endpoint (https://mcp.foxform.app/mcp).

Is the FoxForm MCP server safe to use?

FoxForm scores 85 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 FoxForm MCP server expose?

FoxForm exposes 10 tools: foxform_list_forms, foxform_get_form, foxform_list_responses, foxform_get_response, foxform_get_form_analytics, and 5 more. Their descriptions and schemas cost roughly 3,474 tokens of context every time the server is loaded.

Does the FoxForm MCP server require authentication?

Yes. FoxForm 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 FoxForm MCP server still maintained?

FoxForm is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.