Skip to content
MCPSTAMP
MCP server report

Furrow forms MCP server

com.furrowforms/furrow-forms

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 94 of 100 (grade A), higher than 70.5% of the 33,003 registry servers that responded over HTTPS that day. Ready for Claude, Gemini and MCP Registry. Not ready for ChatGPT.

Measured facts

Score
94A
Sign-in
OAuth
Tools listed
29
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Not ready Blocked by Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT).
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

3 checks to fix

  1. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 29/29 tools miss an explicit hint: list_teams, update_team, get_account, update_account, create_upgrade_link and 24 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  2. Warning

    Tool descriptions

    tool_descriptions

    Measured 3 over 2000 chars: update_account, update_project, bootstrap_site

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

  3. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured JSON-RPC error -32000 instead of -32601

    Return JSON-RPC error code -32601 (Method not found) for unknown methods.

24 checks passed

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, GET answers SSE or 405, initialize latency, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Human-readable title on every tool.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Furrow forms

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fapi.furrowforms.com%2Fmcp)](https://www.mcpstamp.com/r/com-furrowforms-furrow-forms/)

HTML

<a href="https://www.mcpstamp.com/r/com-furrowforms-furrow-forms/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fapi.furrowforms.com%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Form backend an agent runs end to end: provision forms, snippets, spam, signed webhooks.
Registry name
com.furrowforms/furrow-forms
Remote URL
https://api.furrowforms.com/mcp
Version
1.0.1
Source
github.com/useburrow/furrow-forms
Website
furrowforms.com/ai
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade A servers

All grade A servers · All server reports · State of MCP readiness, November 2026