Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Hosted backend for AI agents: create projects with persistent collections and keys, no signup.
2 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 3 | 1 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using ReqRes
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http reqres https://reqres.in/mcpCapabilities
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.
DiscoveredGet 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.
DiscoveredCreate 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.
DiscoveredCreate 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.
DiscoveredSave a record (a JSON object) in a collection so it persists. Pass the fields as data; the API returns it with an id.
DiscoveredDelete a record from a collection.
DiscoveredRead one record by id.
DiscoveredList the collections in the project.
DiscoveredSee recent requests to the project (method, path, status, timing), newest first. Use it to debug why an app's calls fail.
DiscoveredRead the records stored in a collection (paginated).
DiscoveredMerge the given fields into a record and keep the rest, e.g. {"done": true} to tick off a task. Use this for most edits.
DiscoveredReplace all of a record's fields: fields you leave out are removed. To change some fields and keep the rest, use patch_record.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 195 ms | 12 |