Is the Botrecipe Leads MCP server down?

mcp-registry/com.botrecipe/leads · v1.0.0

down
Last checked 2026-10-24 12:35 UTC · handshake 187ms

As of 2026-10-24 12:35 UTC, the Botrecipe Leads MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 62 minutes.

uptime (30d checks)
99.4%
checks observed
1,954
outages (90d)
1
tools
3

25 sales leads with a public funding, hiring or tech signal, source link and draft message each.

Point your MCP client at this streamable-http endpoint: https://leads.cloudforbots.com/mcp

Agent-readiness: C (75/100)

C (75/100): 1 error(s), 1 warning(s) across 3 tool(s); ~244 tokens of tool definitions.
Scores higher than 10% of 15,642 MCP servers Glimind has audited.
Its tool list costs an agent ~244 tokens per session — lighter than 99% of servers.
82 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability96

What to fix (4)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: signal_leads_offer, signal_leads_results, usage_and_upgrade

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 1 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 alerted

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/com.botrecipe/leads"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.botrecipe/leads"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Fleads.svg)](https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fleads?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fleads?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Fleads.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Fleads.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fleads?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6ec94a87b5426fd3…, first seen 2026-10-17, included at leaf 88 of 60,827. Version history · verify what your client received.

Working alternatives

Tools (3)

Compare: most reliable other servers · most reliable data servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Botrecipe Leads MCP server down right now?

As of 2026-10-24 12:35 UTC, the Botrecipe Leads MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 62 minutes.

How many tools does Botrecipe Leads MCP server provide?

Botrecipe Leads MCP server advertises 3 tools, including signal_leads_offer, signal_leads_results, usage_and_upgrade.

How do I install Botrecipe Leads MCP server?

Point your MCP client at this streamable-http endpoint: https://leads.cloudforbots.com/mcp

Is the Botrecipe Leads MCP server safe to connect to an AI agent?

Glimind scanned all 3 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.

Operator of Botrecipe Leads MCP server?

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.

Feedback
Help us improve