Agent Request Desk
REMOTE · AGENTREQUEST.DEV
Find out where your AI agent gets stuck: blocked fetches and missing data, in a private report.
Available components
Last scanned (5 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 755 tokens (~251/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://agentrequest.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.agentrequest.dev | CN=YR1,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | RSA 2048 | SHA256-RSA | 5b92b7fb75b0bce4c3c34c28d7adc8ccf83 |
| SANs: *.agentrequest.dev, agentrequest.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentrequest.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| agentrequest.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentrequest.dev/mcp | Verified | 200 | |
| http (plaintext) | http://agentrequest.dev/mcp | HTTPS enforced | 308 | https://agentrequest.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
report_failure Report a blocked or failed fetch ~196
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, plus a log id. Does not bypass CAPTCHAs or bot protection. Free, takes seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | – |
| description | string | yes | What you were trying to get from it |
| error_message | string | – | – |
| failure_type | string | yes | e.g. 403, 429, captcha, cloudflare, login_wall, js_render, pdf, timeout |
| private | boolean | – | Set true to have your description, purpose and error text used for matching but not stored |
| target | string | yes | URL or domain that failed |
No output schema declared.
No examples provided.
request_action Request an action you could not complete ~256
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 form, contacting a business, filing with a portal, sending post. Returns any existing route that already handles it, plus a log id. Requests are pooled and the most requested actions get built. Free, no key.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | – |
| description | string | yes | The action you were trying to take |
| failure_type | string | – | Why it failed: no_api, captcha, login_required, bot_blocked, phone_only, human_verification, payment, other |
| max_price_usd | number | – | Most you (or your operator) would pay per request in USD if this existed, e.g. 0.01 |
| private | boolean | – | Set true to have your description, purpose and error text used for matching but not stored |
| purpose | string | – | What the user wanted to achieve |
| target | string | – | Service, site or organisation involved |
No output schema declared.
No examples provided.
request_data Request data you could not find ~303
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 pointers to existing sources (official APIs, open datasets, MCP servers) that may already serve the need, plus a log id. Requests are pooled across agents and the most wanted data gets sourced. Free, no key. Do not include personal data about private individuals.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | Name of your agent or product, optional |
| description | string | yes | What data you needed, as specifically as possible |
| format | string | – | Shape you wanted it in, e.g. JSON list, CSV, single value |
| freshness | string | – | How fresh it must be, e.g. real-time, daily, monthly |
| max_price_usd | number | – | Most you (or your operator) would pay per request in USD if this existed, e.g. 0.01 |
| private | boolean | – | Set true to have your description, purpose and error text used for matching but not stored |
| purpose | string | – | What task the data was for, in a few words |
| target | string | – | Site, organisation or source you tried, if any (domain or name) |
No output schema declared.
No examples provided.
How do I install the Agent Request Desk MCP server?
Agent Request Desk is a hosted endpoint at https://agentrequest.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentrequest.dev
claude mcp add --transport http dev-agentrequest-request-desk 'https://agentrequest.dev/mcp'
What is the Agent Request Desk MCP server?
Agent Request Desk is an MCP server listed in the public MCP registry as dev.agentrequest/request-desk. Find out where your AI agent gets stuck: blocked fetches and missing data, in a private report. This page covers its hosted endpoint (https://agentrequest.dev/mcp).
Is the Agent Request Desk MCP server safe to use?
Agent Request Desk scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Request Desk MCP server expose?
Agent Request Desk exposes 3 tools: request_data, request_action, report_failure. Their descriptions and schemas cost roughly 755 tokens of context every time the server is loaded.
Does the Agent Request Desk MCP server require authentication?
No. We connected to Agent Request Desk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Request Desk MCP server still maintained?
Agent Request Desk is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.