mcp-registry/io.favcrm/favcrm · v1.0.0
As of 2026-10-18 13:42 UTC, the Favcrm MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Agentic CRM for service businesses — bookings, customers, WhatsApp, loyalty, invoicing.
Claude Code
claude mcp add --transport http favcrm-mcp-server https://api.favcrm.io/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"favcrm-mcp-server": {
"type": "http",
"url": "https://api.favcrm.io/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
Loading this server's tool list costs an agent ~60,028 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
4 tool definition(s) exceed ~1,200 tokens each (largest: replace_post_block, ~4,659).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~10,826 tokens every session. How to fix →
237 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
8 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Handshake + tools/list takes ~3,065 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 1 tool(s) removed and 10 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.favcrm/favcrm"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.favcrm/favcrm"}) over MCP.
replace_post_block ~4,659 tokenscreate_post ~3,082 tokensupdate_post ~2,964 tokensappend_post_block ~2,521 tokenslist_notification_logs ~1,059 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.favcrm%2Ffavcrm?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.favcrm%2Ffavcrm?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.favcrm%2Ffavcrm.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.favcrm%2Ffavcrm.svg :target: https://glimind.com/server/mcp-registry%2Fio.favcrm%2Ffavcrm?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:fc3d0c0d2d5bda2c…, first seen 2026-10-17, included at leaf 8058 of 22,122. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable knowledge servers · most reliable data servers · most reliable productivity servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 13:42 UTC, the Favcrm MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Favcrm MCP server advertises 238 tools, including accept_team_invite_request, accept_team_invite_verify, add_knowledge_text, append_post_block, archive_survey.
Point your MCP client at this streamable-http endpoint: https://api.favcrm.io/mcp
Glimind scanned all 237 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.