# Agent Request Desk (remote · agentrequest.dev)

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

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `agentrequest.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dev-agentrequest-request-desk/agentrequest.md), [page](https://verifymcp.io/servers/dev-agentrequest-request-desk/agentrequest)

## Channel facts

- Endpoint: `https://agentrequest.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "dev-agentrequest-request-desk": {
      "type": "http",
      "url": "https://agentrequest.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-agentrequest-request-desk]
url = "https://agentrequest.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-agentrequest-request-desk": {
      "type": "remote",
      "url": "https://agentrequest.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-agentrequest-request-desk --url 'https://agentrequest.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-agentrequest-request-desk:
    url: "https://agentrequest.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-agentrequest-request-desk": {
      "Transport": "http",
      "Url": "https://agentrequest.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-agentrequest-request-desk -t streamable-http -u 'https://agentrequest.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-agentrequest-request-desk": {
      "type": "http",
      "url": "https://agentrequest.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 73, +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.

### 2026-11-03 (score 72, +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.

### 2026-11-01 (score 71, +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.

### 2026-10-30 (score 70, +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.

### 2026-10-28 (score 69, +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.

### 2026-10-26 (score 68, +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.

### 2026-10-23 (score 67, +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.

### 2026-10-21 (score 66, +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.

## MCP tools (3)

### `request_data` (~303 tokens)

Request data you could not find

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.

Input parameters:

- `agent_name` (string): Name of your agent or product, optional
- `description` (string, required): 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)

### `request_action` (~256 tokens)

Request an action you could not complete

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.

Input parameters:

- `agent_name` (string)
- `description` (string, required): 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

### `report_failure` (~196 tokens)

Report a blocked or failed fetch

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.

Input parameters:

- `agent_name` (string)
- `description` (string, required): What you were trying to get from it
- `error_message` (string)
- `failure_type` (string, required): 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, required): URL or domain that failed

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-agentrequest-request-desk/agentrequest#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 67
- 2026-10-24: 67
- 2026-10-23: 67
- 2026-10-22: 66
- 2026-10-21: 66
- 2026-10-20: 65
- 2026-10-19: 65
- 2026-10-18: 64

## Common questions

### 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.

## Links

- Remote endpoint: https://agentrequest.dev/mcp
- Website: https://agentrequest.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-agentrequest-request-desk/agentrequest.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-agentrequest-request-desk/agentrequest.json
- HTML version of this page: https://verifymcp.io/servers/dev-agentrequest-request-desk/agentrequest