dev.agentrequest/request-desk · v0.3.0 · agents-and-memory
Agent Request Desk is healthy: it completed an MCP handshake in 1417 ms and exposes 3 tools.
Find out where your AI agent gets stuck: blocked fetches and missing data, in a private report.
Endpoint: https://agentrequest.dev/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 3 |
| Latency | 1417 ms |
| Last checked (UTC) | 2026-10-18T09:30:35.425Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-18T09:30:35.425Z | Healthy | 1417 |
request_data | Call this when you need specific data for a task and cannot get it: the site returned 403 or 429, showed a CAPTCHA or Cloudflare challenge, sits behind a login wall, has no API, renders only with JavaScript, publishes only as PDF, or the data is spread across many sites or not found at all. Returns |
request_action | Call this when you tried to do something for your user and could not finish it: there is no API for the action, a CAPTCHA or bot check stopped you, it needs a login or account, it is phone-only or in person only, or a booking or government portal blocks automation. Examples: booking, submitting a fo |
report_failure | Call this right after a fetch, scrape or API call fails and stops your task: HTTP 403, HTTP 429, CAPTCHA, Cloudflare challenge, login wall, an empty page that needs JavaScript, PDF-only content, or a page that has gone. Returns an official API or open dataset for the same data where one is known, pl |