Remote MCP · Endpoint

Agent Access Check MCP server

No. Agent Access Check answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://accesscheck.botrecipe.com/mcp

The last check completed an MCP handshake.

Registry name
com.botrecipe/accesscheck
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
249 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Before fetching a site: will it let an AI agent in (CAPTCHA, robots), and where is its agent door?
Listing
From the official MCP registry (active).
Recent checks of Agent Access Check
CheckedResultHandshake
19 minutes agoHandshake completed249 ms
9 days agoHandshake completed232 ms
9 days agoHandshake completed179 ms
11 days agoHandshake completed136 ms
12 days agoHandshake completed221 ms
13 days agoHandshake completed478 ms
14 days agoHandshake completed391 ms
15 days agoHandshake completed119 ms
16 days agoHandshake completed247 ms
19 days agoHandshake completed162 ms
21 days agoHandshake completed329 ms
24 days agoHandshake completed124 ms
26 days agoHandshake completed144 ms
28 days agoHandshake completed167 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Agent Access Check and makes no claim about it beyond what these checks measured.