Remote MCP · Endpoint

Agent Access Door Check MCP server

No. Agent Access Door Check answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://textforagents.com/products/agent-access-door-check/mcp

The last check completed an MCP handshake.

Registry name
com.textforagents/agent-access-door-check
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
43 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Before your agent sets out, ask whether the site will let it in
Listing
From the official MCP registry (active).
Recent checks of Agent Access Door Check
CheckedResultHandshake
1 hour agoHandshake completed43 ms
3 days agoHandshake completed55 ms
12 days agoHandshake completed64 ms
12 days agoHandshake completed53 ms
14 days agoHandshake completed37 ms
15 days agoHandshake completed18 ms
16 days agoHandshake completed15 ms
17 days agoHandshake completed15 ms
18 days agoHandshake completed39 ms
19 days agoHandshake completed42 ms
22 days agoHandshake completed49 ms
25 days agoHandshake completed74 ms
27 days agoHandshake completed39 ms

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

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 Door Check and makes no claim about it beyond what these checks measured.