Agent Request Desk MCP server
dev.agentrequest/request-deskagentrequest.devstreamable-httpv0.3.0Scanned
Find out where your AI agent gets stuck: blocked fetches and missing data, in a private report.
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Agent Request Desk MCP server can do
The Agent Request Desk MCP server is published by agentrequest.dev, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: request_data, request_action and report_failure), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (report_failure).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 1, 2026, version 0.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 3Claude Code: ask
report_failureCall 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…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "call": a word for a change.
What it can reach
- untrusted-inputThe description's first sentence says "scrape": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
request_actionCall 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 …No findings
Why it is in this group
- The name "request_action" says "request": a word for a change.
Description, as the server wrote it 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.
request_dataCall 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, re…No findings
Why it is in this group
- The name "request_data" says "request": a word for a change.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:51 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 402
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 402.
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 402
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 402; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 402
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http request-desk https://agentrequest.dev/mcpclaude mcp add --transport http request-desk https://agentrequest.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__request-desk__request_data",
"mcp__request-desk__request_action",
"mcp__request-desk__report_failure"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as request-desk. Review it before you use it.
Capability tags behind 1 rule
- mcp__request-desk__report_failure untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.agentrequest/request-desk/verify?hash=a4429cfc02a8f77f58eb8e35c3b097fe8912053e0fbd2a31c361ce0d0726d497" | jq -e '.changed == false'Pinned hash a4429cfc02a8, from Nov 1, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.agentrequest/request-desk/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.agentrequest/request-desk)Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.
Agent Request Desk MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Agent Request Desk MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Agent Request Desk MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Agent Request Desk MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Agent Request Desk MCP server have?
- 3 tools: 3 write. request_data, request_action and report_failure.
Does the Agent Request Desk MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Agent Request Desk MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Agent Request Desk MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 1, 2026.