Skip to content
MCPSTAMP
MCP server report

FavCRM MCP server

io.favcrm/favcrm

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 81 of 100 (grade B), higher than 26.3% 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
81B
Sign-in
OAuth
Tools listed
237
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Not ready Blocked by Protected resource metadata (RFC 9728).
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

7 checks to fix

  1. Fails

    Protected resource metadata (RFC 9728)

    auth_prm

    Blocks ChatGPT.

    Measured Not found: https://api.favcrm.io/.well-known/oauth-protected-resource/mcp -> 404; https://api.favcrm.io/.well-known/oauth-protected-resource -> 404. Authorizati

    Serve RFC 9728 metadata at /.well-known/oauth-protected-resource (plus the path-suffixed form) with "resource" and "authorization_servers".

  2. Fails

    401 carries WWW-Authenticate resource_metadata

    auth_challenge

    Measured unknown method: HTTP 401 without WWW-Authenticate

    On 401, send WWW-Authenticate: Bearer resource_metadata="<protected resource metadata URL>".

  3. Fails

    Server instructions

    instructions

    Measured No instructions in the initialize result

    Add an "instructions" string to the initialize result: what the server covers, for whom, and its limits.

  4. Warning

    Client registration (DCR or Client ID Metadata Documents)

    auth_registration

    Measured No registration_endpoint and no client_id_metadata_document_supported

    Add a Dynamic Client Registration endpoint (RFC 7591) or set client_id_metadata_document_supported: true; otherwise every store needs a manually issued client id.

  5. Warning

    Tool descriptions

    tool_descriptions

    Measured 60 under 60 chars: get_member_profile, list_tags, update_tag, delete_tag, detach_tags and 55 more

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

  6. Warning

    initialize latency

    latency

    Measured 1560 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

  7. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured HTTP 401 instead of a JSON-RPC error

    Route the method first and answer unknown methods with JSON-RPC error -32601 before the auth check, or return a JSON-RPC error body with the 401.

18 checks passed, 2 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, GET answers SSE or 405, serverInfo name and version, tools capability declared, Sign-in method the store supports (OAuth or none), Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, PKCE S256 advertised, 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, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool.

Not run. Resource metadata "resource" equals the server URL, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT). These need an OAuth sign-in flow the check could not reach.

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 FavCRM

Markdown

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

HTML

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

About this server

Agentic CRM for service businesses - bookings, customers, WhatsApp, loyalty, invoicing.
Registry name
io.favcrm/favcrm
Remote URL
https://api.favcrm.io/mcp
Version
1.0.0
Source
github.com/favcrm/mcp
Website
favcrm.io
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 B servers

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