All servers · Build & deploy · Documents & retrieval · Travel & booking

Agent Request Desk

dev.agentrequest/request-desk · v0.3.0

New (7 days)

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Not declared (tools carry no read/destructive hints)
Capabilities declared	tools
Tool definitions	3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0%

Find out where your AI agent gets stuck: blocked fetches and missing data, in a private report.

streamable-http · https://agentrequest.dev/mcp

claude mcp add --transport http request-desk https://agentrequest.dev/mcp

{
  "mcpServers": {
    "request-desk": {
      "url": "https://agentrequest.dev/mcp"
    }
  }
}

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

Website · JSON · Text for agents · Registry updated 2026-10-18