furrow-forms MCP server
com.furrowforms/furrow-formsfurrowforms.comstreamable-httpv1.0.1Scanned
Form backend an agent runs end to end: provision forms, snippets, spam, signed webhooks.
29 tools: 4 can delete or cancel things, 14 change things and 11 only read.
- Reads private data · 3
- Reads text others write · 7
- Can send data out · 5
- 4 findings, 1 high
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here can delete or cancel things. Govern them.
- 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 furrow-forms MCP server can do
The furrow-forms MCP server is published by furrowforms.com, a domain the MCP Registry verified. It has 29 tools. It can delete or cancel things (4 tools: archive_client, rotate_project_inbox, archive_project and archive_form) and create or change data (14 tools: update_team, update_account, create_upgrade_link, create_client and 10 more). 11 tools only read.
3 tools read private data (get_project, get_form and get_submission); 7 tools bring in text other people can write (list_clients, list_projects, get_project and 4 more); 5 tools can send data out of your system (create_project, update_project, upsert_project_webhook and 2 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 4 findings, 1 of them high severity (long-description and sensitive-path). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 10, 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.
29 tools
Deletes or cancels 4Claude Code: deny
archive_clientUse to archive a client.No findings
Why it is in this group
- The name "archive_client" says "archive": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Use to archive a client. Do not use this as a hard delete. There is no unarchive tool in v1.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
archive_formUse to archive a form so public submit returns 404.No findings
Why it is in this group
- The name "archive_form" says "archive": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Use to archive a form so public submit returns 404. Do not use this as a hard delete.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
archive_projectUse to archive a website.No findings
Why it is in this group
- The name "archive_project" says "archive": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Use to archive a website. Archived projects reject public submit. Do not use this as a hard delete. There is no unarchive tool in v1.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
rotate_project_inboxUse when a project's private inbox URL may have leaked.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 destructive (destructiveHint: true).
Description, as the server wrote it Use when a project's private inbox URL may have leaked. Issues a new inbox key; every previously shared inbox link stops working immediately. get_project returns the new files_url.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
Changes things 14Claude Code: ask
bootstrap_siteUse this to stand up a client, one website (project), and its forms in a single call.Can send data out1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
Findings
- Info
The description is 2,655 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ppet. Do not use when you only need to patch an existing form — call update_form."
Description, as the server wrote it Use this to stand up a client, one website (project), and its forms in a single call. Before calling, ask the human who should receive notification emails (notify_emails has no default; empty means nobody is emailed), thank-you page vs on-page message, and whether to add Turnstile — see furrow://docs/workflow. name/slug are the client; optional project_name/project_slug default to the same. Free accounts cannot create a fourth active project — call create_upgrade_link if bootstrap_site returns plan_limit. Operator tokens (all workspaces) must pass team_id from list_teams. Team-scoped tokens may omit team_id and cannot target another workspace. Idempotent on client, project, and form slugs. Site settings (domains, Turnstile, notify emails, webhook, email templates, uploads) live on the project. Email templates support {{project.name}}, {{project.slug}}, {{form.name}}, {{form.slug}}, {{count}} (1-based clean submissions on this form, including the current one), and any submission field such as {{name}} or {{email}}. Use a fallback with {{name | "New submission"}}. Missing fields render empty and never error. Do not pass HTML; Furrow renders one owned layout. Plans are capacity, not a feature ladder. Free: one workspace, 100 clean submissions/month pooled on the team, 3 active (non-archived) projects, 30-day submission retention, and email.footer_mode / branding.mode stay furrow (other values return plan_limit). Yearly ($199/year): extra workspaces, 10,000 submissions/month, unlimited projects, 730-day retention, branding.mode furrow | off | agency. Expansion packs are $99/year each and add 5,000 submissions/month on a yearly account. MCP, webhooks, snippets, inheritance, Turnstile, and email templates stay available on free. Spam, honeypot, and rejected posts do not count. Use create_upgrade_link to hand a human a Stripe Checkout (or Customer Portal) URL. Pass product=expansion on a yearly team to add a pack. Checkbox groups, select multiple, and other multi-value HTML fields must use a [] suffix on the name (name="services[]") or only the last checked value is stored. Put services[] on field_contract.name too. JSON/fetch should send a real array without brackets ({ "services": ["a", "b"] }) and must not use Object.fromEntries(formData) — use formData.getAll("services"). Single checkbox, select, or combobox: no brackets. File inputs use multipart POST (name="resume[]" for multiple). Enable uploads on the project first. Downloads are the project inbox at files_url, with the form slug as a folder — never put that URL in a public snippet. Do not use when you only need to patch an existing form — call update_form.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: true
create_clientUse to add a client (company) by slug.No findings
Why it is in this group
- The name "create_client" says "create": a word for a change.
Description, as the server wrote it Use to add a client (company) by slug. Idempotent on slug unless strict is true. Operator tokens (all workspaces) must pass team_id from list_teams. Team-scoped tokens may omit team_id and cannot target another workspace. Prefer bootstrap_site when also creating a website and forms. Do not put Turnstile or webhooks on a client — those live on the project.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: true
create_formUse to add a form under an existing project_id.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 Use to add a form under an existing project_id. Idempotent on slug unless strict is true. Overrides are nullable; omit them to inherit project notify emails, webhook, redirect, require_turnstile, and email templates. Pass email.subject / email.intro to override notification copy for this form only. Pass webhook_url_override to send this form to a different URL. Field contract labels (label) are used on notification emails. Checkbox groups, select multiple, and other multi-value HTML fields must use a [] suffix on the name (name="services[]") or only the last checked value is stored. Put services[] on field_contract.name too. JSON/fetch should send a real array without brackets ({ "services": ["a", "b"] }) and must not use Object.fromEntries(formData) — use formData.getAll("services"). Single checkbox, select, or combobox: no brackets. File inputs use multipart POST (name="resume[]" for multiple). Enable uploads on the project first. Downloads are the project inbox at files_url, with the form slug as a folder — never put that URL in a public snippet.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: true
create_projectUse to add one website under an existing client_id.Can send data outNo findings
Why it is in this group
- The name "create_project" says "create": a word for a change.
What it can reach
- outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Use to add one website under an existing client_id. Idempotent on slug unless strict is true. Free accounts are limited to 3 active (non-archived) projects; yearly is unlimited. If create_project returns plan_limit, call create_upgrade_link and hand the human the Stripe URL. Prefer bootstrap_site when the client does not exist yet. Optional email sets notification templates (subject, from_name, intro, footer_mode, include_meta). Free accounts keep footer_mode furrow; other values return plan_limit. Set uploads_enabled on the project to accept files. Email templates support {{project.name}}, {{project.slug}}, {{form.name}}, {{form.slug}}, {{count}} (1-based clean submissions on this form, including the current one), and any submission field such as {{name}} or {{email}}. Use a fallback with {{name | "New submission"}}. Missing fields render empty and never error. Do not pass HTML; Furrow renders one owned layout. Plans are capacity, not a feature ladder. Free: one workspace, 100 clean submissions/month pooled on the team, 3 active (non-archived) projects, 30-day submission retention, and email.footer_mode / branding.mode stay furrow (other values return plan_limit). Yearly ($199/year): extra workspaces, 10,000 submissions/month, unlimited projects, 730-day retention, branding.mode furrow | off | agency. Expansion packs are $99/year each and add 5,000 submissions/month on a yearly account. MCP, webhooks, snippets, inheritance, Turnstile, and email templates stay available on free. Spam, honeypot, and rejected posts do not count. Use create_upgrade_link to hand a human a Stripe Checkout (or Customer Portal) URL. Pass product=expansion on a yearly team to add a pack. File inputs use multipart POST (name="resume[]" for multiple). Enable uploads on the project first. Downloads are the project inbox at files_url, with the form slug as a folder — never put that URL in a public snippet. Do not put Turnstile keys on a form.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: true
create_upgrade_linkUse when a free team is blocked on the 3-project, 100-submission, or one-workspace limit, or when a human should upgrade to yearly ($199/year) so you can keep adding projects, work…No findings
Why it is in this group
- The name "create_upgrade_link" says "create": a word for a change.
Description, as the server wrote it Use when a free team is blocked on the 3-project, 100-submission, or one-workspace limit, or when a human should upgrade to yearly ($199/year) so you can keep adding projects, workspaces, and storing new submissions. Returns a Stripe Checkout URL to hand the human. If the team is already yearly, omit product to get a Stripe Customer Portal URL, or pass product=expansion for a $99/year pack that adds 5,000 submissions/month. Do not change plan in the database — Stripe webhooks do that. Plans are capacity, not a feature ladder. Free: one workspace, 100 clean submissions/month pooled on the team, 3 active (non-archived) projects, 30-day submission retention, and email.footer_mode / branding.mode stay furrow (other values return plan_limit). Yearly ($199/year): extra workspaces, 10,000 submissions/month, unlimited projects, 730-day retention, branding.mode furrow | off | agency. Expansion packs are $99/year each and add 5,000 submissions/month on a yearly account. MCP, webhooks, snippets, inheritance, Turnstile, and email templates stay available on free. Spam, honeypot, and rejected posts do not count. Use create_upgrade_link to hand a human a Stripe Checkout (or Customer Portal) URL. Pass product=expansion on a yearly team to add a pack. Operator tokens (all workspaces) must pass team_id from list_teams. Team-scoped tokens may omit team_id and cannot target another workspace.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: false
move_clientUse when the human asks to move a client (company) and all its projects, forms, submissions, and files into another workspace they own.No findings
Why it is in this group
- The name "move_client" says "move": a word for a change.
Description, as the server wrote it Use when the human asks to move a client (company) and all its projects, forms, submissions, and files into another workspace they own. Public keys, snippets, inbox links, and webhook secrets stay the same, so the live site needs no change. Needs an owner of both teams (dashboard session or operator token; team-scoped tokens cannot). Refused when the destination has a client with the same slug (pass slug), when a free destination would pass 3 projects, or when the client has text alert numbers and the destination has no Twilio. Confirm the destination team name with the human first. Do not use this to rename or archive.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
test_smsUse after setting notify_phones to send one test text to each of the project's numbers through the team's Twilio account.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.
Description, as the server wrote it Use after setting notify_phones to send one test text to each of the project's numbers through the team's Twilio account. Returns per-number results with Twilio's error when one fails. Fails if the team has no Twilio account (update_account sms) or the project has no notify_phones. A successful result means Twilio accepted it; ask the human to confirm it arrived, since unregistered US senders are filtered by carriers after Twilio accepts. Error codes and fixes are in furrow://docs/text-alerts. Do not use this to test email or the webhook — call test_webhook for the webhook.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: false
test_webhookUse to POST a signed webhook.test event to the project's webhook URL.Can send data outNo findings
Why it is in this group
- The description's first verb is "post": a word for a change.
What it can reach
- outboundThe description's first verb is "post": it sends or publishes something to other people.
Description, as the server wrote it Use to POST a signed webhook.test event to the project's webhook URL. Available on free and yearly. Do not use this to inspect past deliveries — that is REST GET /api/projects/:id/webhook-deliveries. Fails if no webhook URL and secret are set.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: false
update_accountUse to rename the workspace, set branding, configure the AI spam filter, or connect the team's own Twilio account for new-lead text alerts.1 finding
Why it is in this group
- The name "update_account" says "update": a word for a change.
Findings
- Info
The description is 2,135 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...another workspace. Do not use this to change the plan — call create_upgrade_link."
Description, as the server wrote it Use to rename the workspace, set branding, configure the AI spam filter, or connect the team's own Twilio account for new-lead text alerts. Pass sms { account_sid, auth_token, from } to save Twilio (auth_token is write-only; omit it later to keep the saved one; sms: null disconnects). Numbers to text are notify_phones on the project. US senders must finish A2P 10DLC or toll-free verification in Twilio or carriers drop the texts. To set it up with a human who has never used Twilio, follow furrow://docs/text-alerts. Pass ai.typesafe_api_key to save this team's TypeSafe key (null clears it; the key is write-only). ai.notify_suspected_spam (default true) emails notify addresses with a Potential spam label for every spam catch — rule-based or Jev — except exact duplicates; set it false to silence both. Spam never sends a webhook. Free accounts keep branding.mode and email.footer_mode at furrow; asking for anything else returns plan_limit — tell the human the custom footer is a Yearly feature and offer create_upgrade_link. Yearly may set branding.mode to furrow, off, or agency (name + optional link + optional logo; Furrow keeps the layout, no raw HTML). Plans are capacity, not a feature ladder. Free: one workspace, 100 clean submissions/month pooled on the team, 3 active (non-archived) projects, 30-day submission retention, and email.footer_mode / branding.mode stay furrow (other values return plan_limit). Yearly ($199/year): extra workspaces, 10,000 submissions/month, unlimited projects, 730-day retention, branding.mode furrow | off | agency. Expansion packs are $99/year each and add 5,000 submissions/month on a yearly account. MCP, webhooks, snippets, inheritance, Turnstile, and email templates stay available on free. Spam, honeypot, and rejected posts do not count. Use create_upgrade_link to hand a human a Stripe Checkout (or Customer Portal) URL. Pass product=expansion on a yearly team to add a pack. Operator tokens (all workspaces) must pass team_id from list_teams. Team-scoped tokens may omit team_id and cannot target another workspace. Do not use this to change the plan — call create_upgrade_link.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: true
update_clientUse to rename a client.No findings
Why it is in this group
- The name "update_client" says "update": a word for a change.
Description, as the server wrote it Use to rename a client. Do not use this to change domains, Turnstile, or webhooks — call update_project.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: true
update_formUse to patch form overrides.No findings
Why it is in this group
- The name "update_form" says "update": a word for a change.
Description, as the server wrote it Use to patch form overrides. Pass null on an override to inherit again. Set email.subject or email.intro to override project notification copy for this form only; from_name, footer_mode, and include_meta stay on the project. Email templates support {{project.name}}, {{project.slug}}, {{form.name}}, {{form.slug}}, {{count}} (1-based clean submissions on this form, including the current one), and any submission field such as {{name}} or {{email}}. Use a fallback with {{name | "New submission"}}. Missing fields render empty and never error. Do not pass HTML; Furrow renders one owned layout. Set webhook_url_override to override the project webhook for this form. notify_cc_override / notify_bcc_override replace the project's copies ([] sends none). notify_phones_override replaces the project's text-alert numbers ([] silences texts for this form). Do not use this to change Turnstile keys — those live on the project. Checkbox groups, select multiple, and other multi-value HTML fields must use a [] suffix on the name (name="services[]") or only the last checked value is stored. Put services[] on field_contract.name too. JSON/fetch should send a real array without brackets ({ "services": ["a", "b"] }) and must not use Object.fromEntries(formData) — use formData.getAll("services"). Single checkbox, select, or combobox: no brackets. File inputs use multipart POST (name="resume[]" for multiple). Enable uploads on the project first. Downloads are the project inbox at files_url, with the form slug as a folder — never put that URL in a public snippet.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: true
update_projectUse to patch website settings.Can send data out1 finding
Why it is in this group
- The name "update_project" says "update": a word for a change.
What it can reach
- outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
Findings
- Info
The description is 2,192 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...t keys changes resolved settings on existing forms unless a form override is set."
Description, as the server wrote it Use to patch website settings. Nested email sets notification templates: email.subject, email.from_name, email.intro, email.footer_mode (furrow | minimal | off), email.include_meta. Optional branding updates the team (mode furrow | off | agency on yearly only; other modes return plan_limit on free). Set uploads_enabled and upload_allowed_types here — forms inherit them. notify_cc and notify_bcc copy every notification email (Bcc stays hidden from the client — use it for an agency's quiet copy); forms inherit them. notify_phones (E.164) get a short new-lead text per clean submission once the team has Twilio set up (update_account sms); forms inherit them. Email templates support {{project.name}}, {{project.slug}}, {{form.name}}, {{form.slug}}, {{count}} (1-based clean submissions on this form, including the current one), and any submission field such as {{name}} or {{email}}. Use a fallback with {{name | "New submission"}}. Missing fields render empty and never error. Do not pass HTML; Furrow renders one owned layout. Plans are capacity, not a feature ladder. Free: one workspace, 100 clean submissions/month pooled on the team, 3 active (non-archived) projects, 30-day submission retention, and email.footer_mode / branding.mode stay furrow (other values return plan_limit). Yearly ($199/year): extra workspaces, 10,000 submissions/month, unlimited projects, 730-day retention, branding.mode furrow | off | agency. Expansion packs are $99/year each and add 5,000 submissions/month on a yearly account. MCP, webhooks, snippets, inheritance, Turnstile, and email templates stay available on free. Spam, honeypot, and rejected posts do not count. Use create_upgrade_link to hand a human a Stripe Checkout (or Customer Portal) URL. Pass product=expansion on a yearly team to add a pack. File inputs use multipart POST (name="resume[]" for multiple). Enable uploads on the project first. Downloads are the project inbox at files_url, with the form slug as a folder — never put that URL in a public snippet. Null Turnstile or webhook fields clear them. Do not use this to create forms. Updating project keys changes resolved settings on existing forms unless a form override is set.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: true
update_teamUse to rename a team.No findings
Why it is in this group
- The name "update_team" says "update": a word for a change.
Description, as the server wrote it Use to rename a team. Operator tokens (all workspaces) must pass team_id from list_teams. Team-scoped tokens may omit team_id and cannot target another workspace. Do not use this to create another workspace — that is dashboard-only and requires yearly. For plan, usage, retention, and branding, call get_account / update_account. Do not use this to change clients or projects.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: true
upsert_project_webhookUse to set or replace the project webhook URL.Can send data outNo findings
Why it is in this group
- The name "upsert_project_webhook" says "upsert": a word for a change.
What it can reach
- outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Use to set or replace the project webhook URL. Available on free and yearly. A signing secret is generated once if the project has none. Forms inherit this unless webhook_url_override is set. Do not use this for a one-off delivery — call test_webhook.
Annotations the server declares
- readOnlyHint: false
- idempotentHint: true
Only reads 11Show 11 read-only tools
get_accountUse to read the team's plan, usage this month, limits, expansion_packs, retention_days, branding, and AI spam filter (ai.typesafe_key_set, ai.notify_suspected_spam), and text alert…No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it Use to read the team's plan, usage this month, limits, expansion_packs, retention_days, branding, and AI spam filter (ai.typesafe_key_set, ai.notify_suspected_spam), and text alerts (sms.configured, provider, account_sid, from). The TypeSafe key and Twilio Auth Token are never returned. Plans are capacity, not a feature ladder. Free: one workspace, 100 clean submissions/month pooled on the team, 3 active (non-archived) projects, 30-day submission retention, and email.footer_mode / branding.mode stay furrow (other values return plan_limit). Yearly ($199/year): extra workspaces, 10,000 submissions/month, unlimited projects, 730-day retention, branding.mode furrow | off | agency. Expansion packs are $99/year each and add 5,000 submissions/month on a yearly account. MCP, webhooks, snippets, inheritance, Turnstile, and email templates stay available on free. Spam, honeypot, and rejected posts do not count. Use create_upgrade_link to hand a human a Stripe Checkout (or Customer Portal) URL. Pass product=expansion on a yearly team to add a pack. Operator tokens (all workspaces) must pass team_id from list_teams. Team-scoped tokens may omit team_id and cannot target another workspace. Do not use this to list projects — call list_projects.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
get_clientUse to inspect one client.No findings
Why it is in this group
- The name "get_client" says "get": a word for reading.
Description, as the server wrote it Use to inspect one client. Do not use to list that client's sites — call list_projects with client_id.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
get_formUse to read a form plus resolved and inherited settings, including resolved.email and resolved.uploads.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_form" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "email": it reads mail.
- 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 Use to read a form plus resolved and inherited settings, including resolved.email and resolved.uploads. files_url is the private inbox folder for this form under the project inbox (do not put it in a public snippet). Turnstile always inherits from the project (inherited.turnstile is true). Form webhook_url_override is nullable; null means inherit the project webhook. Forms may override email.subject and email.intro only. Do not use to generate embed code — call get_snippet.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
get_projectUse to inspect one website's settings, domains, webhook URL, email templates, upload policy, plan, usage this month, limits, retention_days, and branding.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_project" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "inspect" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "inspect" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it Use to inspect one website's settings, domains, webhook URL, email templates, upload policy, plan, usage this month, limits, retention_days, and branding. Returns stored values plus resolved.email. Secrets are never returned. Plans are capacity, not a feature ladder. Free: one workspace, 100 clean submissions/month pooled on the team, 3 active (non-archived) projects, 30-day submission retention, and email.footer_mode / branding.mode stay furrow (other values return plan_limit). Yearly ($199/year): extra workspaces, 10,000 submissions/month, unlimited projects, 730-day retention, branding.mode furrow | off | agency. Expansion packs are $99/year each and add 5,000 submissions/month on a yearly account. MCP, webhooks, snippets, inheritance, Turnstile, and email templates stay available on free. Spam, honeypot, and rejected posts do not count. Use create_upgrade_link to hand a human a Stripe Checkout (or Customer Portal) URL. Pass product=expansion on a yearly team to add a pack. Do not use to list forms — call list_forms.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
get_snippetUse after the form exists to get copy-paste html, astro, or next code that posts to /s/:publicKey.Reads text others write1 finding
Why it is in this group
- The name "get_snippet" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "html": it reads web pages, which anyone can write.
Findings
- High
The description refers to ".env".
What this check looks forMatched text
description: "...ey is not a secret. Do not move it into .env / NEXT_PUBLIC_* / PUBLIC_* or ask the h..."
Description, as the server wrote it Use after the form exists to get copy-paste html, astro, or next code that posts to /s/:publicKey. Do not invent a submit URL — this tool returns it. Snippets are single-value inputs; write checkbox groups and multi-selects yourself. Checkbox groups, select multiple, and other multi-value HTML fields must use a [] suffix on the name (name="services[]") or only the last checked value is stored. Put services[] on field_contract.name too. JSON/fetch should send a real array without brackets ({ "services": ["a", "b"] }) and must not use Object.fromEntries(formData) — use formData.getAll("services"). Single checkbox, select, or combobox: no brackets. File inputs use multipart POST (name="resume[]" for multiple). Enable uploads on the project first. Downloads are the project inbox at files_url, with the form slug as a folder — never put that URL in a public snippet. After dropping the snippet, add visitor-facing success UI: a thank-you page plus default_redirect_url for classic HTML POST, or an on-page message when using fetch/{ok:true}. Do not leave visitors looking at JSON. See furrow://docs/submit-success. Hardcode submit_url as returned; the public key is not a secret. Do not move it into .env / NEXT_PUBLIC_* / PUBLIC_* or ask the human to set environment variables. See furrow://docs/testing.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
get_submissionUse to read one stored submission by id, including file metadata and files_url (the form inbox).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 "file": it reads files.
- untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Use to read one stored submission by id, including file metadata and files_url (the form inbox). Do not use this for live submit tests — POST to /s/:publicKey instead. Do not expect signed bucket URLs — download from the inbox.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
list_clientsUse to browse clients (companies).Reads text others writeNo findings
Why it is in this group
- The name "list_clients" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Use to browse clients (companies). Operator tokens (all workspaces) must pass team_id from list_teams. Team-scoped tokens may omit team_id and cannot target another workspace. Do not use to list websites — call list_projects with client_id. Archived clients are hidden unless status=all or archived.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
list_formsUse to list forms.No findings
Why it is in this group
- The name "list_forms" says "list": a word for reading.
Description, as the server wrote it Use to list forms. Pass project_id for one website or client_id for one company (team is inferred). Otherwise Operator tokens (all workspaces) must pass team_id from list_teams. Team-scoped tokens may omit team_id and cannot target another workspace. Do not use to read resolved inheritance — call get_form.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
list_projectsUse to browse websites.Reads text others writeNo findings
Why it is in this group
- The name "list_projects" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Use to browse websites. Pass client_id to list one client's sites (team is inferred). Without client_id, Operator tokens (all workspaces) must pass team_id from list_teams. Team-scoped tokens may omit team_id and cannot target another workspace. Do not use to read one project's settings — call get_project. Archived projects are hidden unless status=all or archived.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
list_submissionsUse to inspect recent posts.Reads text others writeNo findings
Why it is in this group
- The name "list_submissions" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "inspect" and "post": it reads posts, which other people can write.
Description, as the server wrote it Use to inspect recent posts. Available on free and yearly. Pass project_id or form_id to infer the team; omit both and Operator tokens (all workspaces) must pass team_id from list_teams. Team-scoped tokens may omit team_id and cannot target another workspace. Free teams prune submissions after 30 days; yearly after 730 days. Do not use to read a single submission — call get_submission.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
list_teamsUse to see workspaces this token can act on.No findings
Why it is in this group
- The name "list_teams" says "list": a word for reading.
Description, as the server wrote it Use to see workspaces this token can act on. A team-scoped frw_ token returns that team only. An operator token or an MCP OAuth login returns every team you belong to — pass team_id on list_clients, create_client, and bootstrap_site. Creating another workspace is dashboard-only after signing in and requires a yearly plan; free accounts stay on one team. Do not use this to list clients — call list_clients.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: 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.
105 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 3 private-data tools breaks every one.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write7
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out5
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__furrow-forms__get_form",
"mcp__furrow-forms__get_project",
"mcp__furrow-forms__get_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:39 UTC, unchanged since Oct 29, 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
- 18
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.furrowforms.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.furrowforms.com/api/auth
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 18 tools that change things (4 destructive, 14 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.furrowforms.com/mcp: tools/list returned 29 tools to an anonymous client, including archive_client (destructive), rotate_project_inbox (destructive), archive_project (destructive), archive_form (destructive), update_team (write) and 13 more
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 16 to 18
Findings
Matches of fixed checks, with the text they matched.
- Highget_snippet
The description refers to ".env".
What this check looks forMatched text
description: "...ey is not a secret. Do not move it into .env / NEXT_PUBLIC_* / PUBLIC_* or ask the h..."
- Infoupdate_account
The description is 2,135 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...another workspace. Do not use this to change the plan — call create_upgrade_link."
- Infoupdate_project
The description is 2,192 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...t keys changes resolved settings on existing forms unless a form override is set."
- Infobootstrap_site
The description is 2,655 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ppet. Do not use when you only need to patch an existing form — call update_form."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 5 changed.+1 added~5 changedView diff
- Added:move_clientChanges things
- Changed:bootstrap_siteChanges thingsinputSchema
- Changed:create_formChanges thingsinputSchema
- Changed:create_projectChanges thingsinputSchema
- Changed:update_formChanges thingsdescriptioninputSchema
- Changed:update_projectChanges thingsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 16 -> 18.View diff
- Tools that change things, listed without credentials: 16 to 18
Tools1 added, 10 changed.+1 added~10 changedView diff
- Added:test_smsChanges things
- Changed:bootstrap_siteChanges thingsdescriptioninputSchema
- Changed:create_formChanges thingsinputSchema
- Changed:create_projectChanges thingsdescriptioninputSchema
- Changed:create_upgrade_linkChanges thingsdescription
- Changed:get_accountOnly readsdescription
- Changed:get_projectOnly readsdescription
- Changed:get_snippetOnly readsdescription
- Changed:update_accountChanges thingsdescriptioninputSchema
- Changed:update_formChanges thingsdescriptioninputSchema
- Changed:update_projectChanges thingsdescriptioninputSchema
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http furrow-forms https://api.furrowforms.com/mcpclaude mcp add --transport http furrow-forms https://api.furrowforms.com/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__furrow-forms__list_teams",
"mcp__furrow-forms__get_account",
"mcp__furrow-forms__list_clients",
"mcp__furrow-forms__get_client",
"mcp__furrow-forms__list_projects",
"mcp__furrow-forms__get_project",
"mcp__furrow-forms__list_forms",
"mcp__furrow-forms__get_form",
"mcp__furrow-forms__list_submissions",
"mcp__furrow-forms__get_submission",
"mcp__furrow-forms__get_snippet"
],
"ask": [
"mcp__furrow-forms__update_team",
"mcp__furrow-forms__update_account",
"mcp__furrow-forms__create_upgrade_link",
"mcp__furrow-forms__create_client",
"mcp__furrow-forms__update_client",
"mcp__furrow-forms__move_client",
"mcp__furrow-forms__create_project",
"mcp__furrow-forms__update_project",
"mcp__furrow-forms__create_form",
"mcp__furrow-forms__update_form",
"mcp__furrow-forms__upsert_project_webhook",
"mcp__furrow-forms__test_webhook",
"mcp__furrow-forms__test_sms",
"mcp__furrow-forms__bootstrap_site"
],
"deny": [
"mcp__furrow-forms__archive_client",
"mcp__furrow-forms__rotate_project_inbox",
"mcp__furrow-forms__archive_project",
"mcp__furrow-forms__archive_form"
]
}
}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 furrow-forms. Review it before you use it.
Capability tags behind 12 rules
- mcp__furrow-forms__list_clients untrusted-input
- mcp__furrow-forms__list_projects untrusted-input
- mcp__furrow-forms__get_project private-data, untrusted-input
- mcp__furrow-forms__get_form private-data, untrusted-input
- mcp__furrow-forms__list_submissions untrusted-input
- mcp__furrow-forms__get_submission private-data, untrusted-input
- mcp__furrow-forms__get_snippet untrusted-input
- mcp__furrow-forms__create_project outbound
- mcp__furrow-forms__update_project outbound
- mcp__furrow-forms__upsert_project_webhook outbound
- mcp__furrow-forms__test_webhook outbound
- mcp__furrow-forms__bootstrap_site outbound
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.furrowforms/furrow-forms/verify?hash=904e41c9e892b70a77cc5c3c874442938fb42f1d977bda47212e7f8f0ed1bdce" | jq -e '.changed == false'Pinned hash 904e41c9e892, from Nov 10, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.furrowforms/furrow-forms/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.furrowforms/furrow-forms)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:55 UTC.
furrow-forms MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the furrow-forms MCP server safe?
- No scan can promise that. What its definitions show: 29 tools, 18 of which can change, send or delete something, and 4 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the furrow-forms MCP server delete data?
- Yes. 4 tools can delete, cancel or revoke something: archive_client, rotate_project_inbox, archive_project and archive_form.
Can the furrow-forms MCP server 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 furrow-forms MCP server have?
- 29 tools: 4 destructive, 14 write, 11 read. archive_client, rotate_project_inbox, archive_project, archive_form, update_team, update_account, create_upgrade_link, create_client and 21 more.
Does the furrow-forms MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the furrow-forms MCP server send data to outside services?
- 5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_project, update_project, upsert_project_webhook, test_webhook and bootstrap_site.
Has the furrow-forms MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.