ReqRes MCP server
in.reqres/reqresreqres.instreamable-httpv1.0.0Scanned
Hosted backend for AI agents: create projects with persistent collections and keys, no signup.
12 tools: 2 can delete or cancel things, 1 do something that can't be undone, 5 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ReqRes MCP server can do
The ReqRes MCP server is published by reqres.in, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (2 tools: update_record and delete_record), do things that cannot be undone, such as sending, paying or publishing (patch_record) and create or change data (5 tools: create_project, create_collection, create_record, create_app_user and 1 more). 4 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 1.0.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.
12 tools
Deletes or cancels 2Claude Code: deny
delete_recordDelete a record from a collection.No findings
Why it is in this group
- The name "delete_record" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a record from a collection.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
update_recordReplace all of a record's fields: fields you leave out are removed.No findings
Why it is in this group
- The name "update_record" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Replace all of a record's fields: fields you leave out are removed. To change some fields and keep the rest, use patch_record.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Can't be undone 1Claude Code: ask
patch_recordMerge the given fields into a record and keep the rest, e.g.No findings
Why it is in this group
- The name "patch_record" says "patch": a word for a change.
- The description's first verb is "merge": a word for a change that another call does not undo.
Description, as the server wrote it Merge the given fields into a record and keep the rest, e.g. {"done": true} to tick off a task. Use this for most edits.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Changes things 5Claude Code: ask
create_app_userAdd an end user to the project (for apps where each user sees only their own records).No findings
Why it is in this group
- The name "create_app_user" says "create": a word for a change.
Description, as the server wrote it Add an end user to the project (for apps where each user sees only their own records). No email is sent. Then call create_app_user_session to act as that user.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
create_app_user_sessionGet a 6-hour session token for an app user without email.No findings
Why it is in this group
- The name "create_app_user_session" says "create": a word for a change.
Description, as the server wrote it Get a 6-hour session token for an app user without email. Send it as Authorization: Bearer <session_token> to https://reqres.in/app/collections/{collection}/records, where the user only sees their own records. Real users sign in with an emailed code via /api/app-users/login.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_collectionCreate a collection: a new resource (like a table) with its own REST endpoint at /api/collections/{slug}/records.No findings
Why it is in this group
- The name "create_collection" says "create": a word for a change.
Description, as the server wrote it Create a collection: a new resource (like a table) with its own REST endpoint at /api/collections/{slug}/records. Use one per kind of thing the app stores (tasks, users, orders). Free projects allow 3.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_projectCreate a real hosted backend (a REST API with a persistent database) in one call, with no account or API key.No findings
Why it is in this group
- The name "create_project" says "create": a word for a change.
Description, as the server wrote it Create a real hosted backend (a REST API with a persistent database) in one call, with no account or API key. Use it when the user needs to store data, persist an app or prototype, or give a frontend a live API. Returns a manage key, a read-only public key, a starter "products" collection, the base URL and a claim_url. Show the user the claim_url: signing in through it keeps the project; otherwise it is deleted after 72 hours. Free limits: 250 requests a day, 3 collections, 100 records.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_recordSave a record (a JSON object) in a collection so it persists.No findings
Why it is in this group
- The name "create_record" says "create": a word for a change.
Description, as the server wrote it Save a record (a JSON object) in a collection so it persists. Pass the fields as data; the API returns it with an id.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_recordRead one record by id.No findings
Why it is in this group
- The name "get_record" says "get": a word for reading.
Description, as the server wrote it Read one record by id.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_collectionsList the collections in the project.No findings
Why it is in this group
- The name "list_collections" says "list": a word for reading.
Description, as the server wrote it List the collections in the project.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_logsSee recent requests to the project (method, path, status, timing), newest first.No findings
Why it is in this group
- The name "list_logs" says "list": a word for reading.
Description, as the server wrote it See recent requests to the project (method, path, status, timing), newest first. Use it to debug why an app's calls fail.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_recordsRead the records stored in a collection (paginated).No findings
Why it is in this group
- The name "list_records" says "list": a word for reading.
Description, as the server wrote it Read the records stored in a collection (paginated).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
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 untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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:55 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
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (2 destructive, 1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://reqres.in/mcp: tools/list returned 12 tools to an anonymous client, including update_record (destructive), delete_record (destructive), patch_record (irreversible), create_project (write), create_collection (write) and 3 more
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 5 to 8
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.
Tools5 added, 1 changed.+5 added~1 changedView diff
- Added:create_app_userChanges things
- Added:create_app_user_sessionChanges things
- Added:get_recordOnly reads
- Added:list_logsOnly reads
- Added:patch_recordCan't be undone
- Changed:update_recordDeletes or cancelstitledescription
PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 8.View diff
- Tools that change things, listed without credentials: 5 to 8
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http reqres https://reqres.in/mcpclaude mcp add --transport http reqres https://reqres.in/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": [
"mcp__reqres__list_collections",
"mcp__reqres__list_records",
"mcp__reqres__get_record",
"mcp__reqres__list_logs"
],
"ask": [
"mcp__reqres__create_project",
"mcp__reqres__create_collection",
"mcp__reqres__create_record",
"mcp__reqres__patch_record",
"mcp__reqres__create_app_user",
"mcp__reqres__create_app_user_session"
],
"deny": [
"mcp__reqres__update_record",
"mcp__reqres__delete_record"
]
}
}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 reqres. Review it before you use it.
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/in.reqres/reqres/verify?hash=48a636a9ab4bb88805adfda95c7e2ce6e01c3e750be40555af66fea971a66baf" | jq -e '.changed == false'Pinned hash 48a636a9ab4b, from Nov 15, 2026, 13:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/in.reqres/reqres/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/in.reqres/reqres)Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.
ReqRes MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ReqRes MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 8 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 ReqRes MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: update_record and delete_record.
Can the ReqRes MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: patch_record.
What tools does the ReqRes MCP server have?
- 12 tools: 2 destructive, 1 irreversible, 5 write, 4 read. update_record, delete_record, patch_record, create_project, create_collection, create_record, create_app_user, create_app_user_session and 4 more.
Does the ReqRes MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ReqRes MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ReqRes MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.