Is the Botrecipe Accesscheck MCP server down?

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

healthy
Last checked 2026-10-22 14:38 UTC · handshake 169ms

As of 2026-10-22 14:38 UTC, the Botrecipe Accesscheck MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 62 minutes.

uptime (30d checks)
99.7%
checks observed
1,467
outages (90d)
1
tools
4

Check if a website will block your AI agent and find its llms.txt, MCP or OpenAPI door.

Install Botrecipe Accesscheck MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http botrecipe-accesscheck-mcp-server https://accesscheck.cloudforbots.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "botrecipe-accesscheck-mcp-server": {
      "type": "http",
      "url": "https://accesscheck.cloudforbots.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 2 warning(s) across 4 tool(s); ~425 tokens of tool definitions.
Scores higher than 13% of 15,543 MCP servers Glimind has audited.
Its tool list costs an agent ~425 tokens per session — lighter than 95% of servers.
74 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions55
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

4 of 4 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: check_agent_access, check_many, find_agent_alternative, usage_and_upgrade

2 parameter(s) across 2 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 →

Tools: check_many, find_agent_alternative

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 →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.botrecipe%2Faccesscheck/fixes

check_agent_access 1 change
{
  "name": "check_agent_access",
  "description": "Before an agent browses or fetches a site, check if it will get in. Fetches the URL as an AI agent and as a browser, detects bot challenges (CAPTCHAs, DataDome, PerimeterX and other bot walls), reads robots.txt rules for GPTBot/ChatGPT-User/ClaudeBot/Claude-User/PerplexityBot and others, and looks for agent doors (llms.txt, MCP, OpenAPI). Returns verdict: open | challenged | blocked | robots_disallowed | unreachable, plus advice. Read-only. Use it before an automated web task, not for pages you ",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "Page or domain, e.g. https://example.com/pricing"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_many 1 change
{
  "name": "check_many",
  "description": "Run check_agent_access on up to 10 URLs at once (counts as 1 call). Use it to pick which sources an agent can actually use.",
  "inputSchema": {
    "type": "object",
    "required": [
      "urls"
    ],
    "properties": {
      "urls": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 10
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
find_agent_alternative 1 change
{
  "name": "find_agent_alternative",
  "description": "Find a machine-friendly way into a site instead of scraping its HTML: llms.txt, /.well-known/mcp.json, agents.json, openapi.json, ai-plugin.json, and MCP URLs listed in llms.txt. Read-only.",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/accesscheck"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.botrecipe/accesscheck"}) 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%2Faccesscheck.svg)](https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Faccesscheck?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Faccesscheck?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Faccesscheck.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Faccesscheck.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Faccesscheck?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:e02bd58d2cdbbe74…, first seen 2026-10-17, included at leaf 289 of 46,504. Version history · verify what your client received.

Tools (4)

Compare: most reliable web servers · most reliable other 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 Accesscheck MCP server down right now?

As of 2026-10-22 14:38 UTC, the Botrecipe Accesscheck MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 62 minutes.

How many tools does Botrecipe Accesscheck MCP server provide?

Botrecipe Accesscheck MCP server advertises 4 tools, including check_agent_access, check_many, find_agent_alternative, usage_and_upgrade.

How do I install Botrecipe Accesscheck MCP server?

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

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

Glimind scanned all 4 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 Accesscheck 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