Agent Request Desk

Name: Agent Request Desk
Author: dev.agentrequest

MCP serverMCP

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

by dev.agentrequesthomepage ↗v0.3.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"agent-request-desk","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability45/45 checks ok

when	check	result	http	latency	detail
8 h ago	mcp initialize	ok	200	812 ms	server agent-request-desk 0.3.0 · protocol 2025-06-18 · 3 tools
16 h ago	mcp initialize	ok	200	57 ms	server agent-request-desk 0.3.0 · protocol 2025-06-18 · 3 tools
24 h ago	mcp initialize	ok	200	73 ms	server agent-request-desk 0.3.0 · protocol 2025-06-18 · 3 tools
32 h ago	mcp initialize	ok	200	78 ms	server agent-request-desk 0.3.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	61 ms	server agent-request-desk 0.3.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	771 ms	server agent-request-desk 0.3.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	92 ms	server agent-request-desk 0.3.0 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	103 ms	server agent-request-desk 0.3.0 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	141 ms	server agent-request-desk 0.3.0 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	88 ms	server agent-request-desk 0.3.0 · protocol 2025-06-18 · 3 tools

Tools observed via MCP handshake

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
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 l
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 n

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrydev.agentrequest/request-desk

first seen 14 d ago · fetched 3 d agoopen ↗

Field history (6 recent events)

14 d ago · declared · summary → "Find out where your AI agent gets stuck: blocked fetches and missing data, in a private report."
14 d ago · declared · description → "Find out where your AI agent gets stuck: blocked fetches and missing data, in a private report."
14 d ago · declared · publisherName → "dev.agentrequest"
14 d ago · declared · homepageUrl → "https://agentrequest.dev"
14 d ago · declared · version → "0.3.0"
14 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from