
ReqRes MCP server
Which MCP servers are ReqRes's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-17
- Registry namein.reqres/reqresverified in the MCP registry
The registry name sits under reqres.in. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-17
- Tools7
- Server calls itselfreqres
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-17 the server answered initialize and tools/list without a sign-in. First answer in 156 ms.
- Whether its tools do the product's job has not been judged yet.
Once connected
- create_project, create_collection, create_record, update_record, delete_record change data without a sign-in: anyone with the address can call them.
- Parameters are untyped or undescribed in 3 of 7 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score78 of 100answers 100 · definitions 93 · context 100 · connects 100 · lowered by the warning signs below
- Answered100% of days17 of 17 daily checks
- Median first answer323 ms
- Space in an agent's context≈ 1,006 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsA · 93 of 100
- Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 3 of 7
What an agent can do with it
- cannot · test login and register flows, including wrong-password and missing-field failures
- not sure · run CRUD test suites against persistent sample collections
- not sure · prototype frontend features against a hosted backend with no server setup
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: create_project, create_collection, create_record, update_record, delete_record
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
create_projectCreate 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…
list_collectionsList the collections in the project.
create_collectionCreate 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.
list_recordsRead the records stored in a collection (paginated).
create_recordSave a record (a JSON object) in a collection so it persists. Pass the fields as data; the API returns it with an id.
update_recordReplace a record's fields.
delete_recordDelete a record from a collection.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"reqres": {
"type": "http",
"url": "https://reqres.in/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http reqres https://reqres.in/mcpclaude.ai, ChatGPT and other clients: add https://reqres.in/mcp as a custom connector in the settings.
OpenAPI spec
42 paths, read 2026-10-17. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.