ReqRes MCP server
7 tools · Last check that passed 27 Oct 2026, 01:50 UTC
ReqRes's own remote MCP server lets an agent create a hosted test backend with no account, and then create, read, update and delete its collections and records. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 7 tools
| Tool | Counted as |
|---|---|
delete_record | Deletes |
update_record | Deletes |
create_collection | Changes things |
create_project | Changes things |
create_record | Changes things |
list_collections | Said to only read |
list_records | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://reqres.in/mcp.
Recent changes
22 Oct 2026, 09:48 UTC, after a check on 21 Oct 2026, 09:35 UTC
Can do more The server's own labels changed on create_collection, create_project, create_record, delete_record, list_collections and 2 more. Counted as able to do more: update_record (make changes that cannot be undone).
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when ReqRes's tools change.
One email when ReqRes's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- An agent can create a project with no account or API key, and ReqRes deletes a project that is not claimed within 72 hours. ReqRes's MCP documentation
- Free projects are limited to 250 requests a day, 3 collections and 100 records. ReqRes's MCP documentation
How to limit it
With ReqRes's own settings, as its documentation describes them. Stackduke has not tested them.
- ReqRes describes its public key as for read-only testing and its manage key as for setup, so we recommend giving the agent the public key when it only needs to read. ReqRes's documentation
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.