Remote MCP · Endpoint

Agent Request Desk MCP server

Yes, as of 34 minutes ago: the server returned an HTTP error.

DownLast checked 34 minutes ago

Server URL

https://agentrequest.dev/mcp

The last check failed: the server returned an HTTP error.

Registry name
dev.agentrequest/request-desk
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Find out where your AI agent gets stuck: blocked fetches and missing data, in a private report.
Listing
From the official MCP registry (active).
Recent checks of Agent Request Desk
CheckedResultHandshake
34 minutes agoFailed - the server returned an HTTP error—
9 days agoHandshake completed146 ms
10 days agoHandshake completed176 ms
11 days agoHandshake completed153 ms
12 days agoHandshake completed156 ms
14 days agoHandshake completed184 ms
14 days agoHandshake completed145 ms
15 days agoHandshake completed197 ms
17 days agoHandshake completed200 ms
19 days agoHandshake completed153 ms
21 days agoHandshake completed477 ms
24 days agoHandshake completed203 ms
26 days agoHandshake completed158 ms
28 days agoHandshake completed215 ms

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

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