# ObsessionDB vs ReqRes MCP server (slim)

> ReqRes scores 48.8 (D) to ObsessionDB's 41.1 (E) for databases. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp.md (~4,500 tokens) · this version ~2,730 tokens · JSON https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp.json · canonical https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

ReqRes MCP server scores 48.8 (D) on agent readiness against ObsessionDB's 41.1 (E), and leads in 5 of 7 scored categories. ObsessionDB leads on security & auth and transparency & trust. Both do databases.

- ObsessionDB: E 41.1, rank #1307 of 1510 · https://www.anchorterminal.com/tools/obsessiondb.min.md
- ReqRes MCP server: D 48.8, rank #1114 of 1510 · https://www.anchorterminal.com/tools/reqres-mcp.min.md
- ObsessionDB, good for An agent that needs SQL over large ClickHouse tables, and the database's own monitoring and alerts, through one hosted MCP connection. Ahead on Security & auth, 51 against 33; Transparency & trust, 59 against 47.
- ReqRes MCP server, good for Coding agents that need a throwaway or starter backend for a prototype, with no account to set up. Ahead on Reliability, 30 against 20; Schema & documentation, 61 against 43; Agent ergonomics, 76 against 53; Payments & pricing, 50 against 40; Maintenance & community, 50 against 28. Also No key needed to call it.

| Category | ObsessionDB | ReqRes MCP server |
| --- | --- | --- |
| Reliability (16%) | 20 | 30 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 43 | 61 |
| Agent ergonomics (13%) | 53 | 76 |
| Security & auth (14%) | 51 | 33 |
| Payments & pricing (10%) | 40 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 28 | 50 |
| Transparency & trust (7%) | 59 | 47 |

| Fact (where they differ) | ObsessionDB | ReqRes MCP server |
| --- | --- | --- |
| Vendor | Kellerkind UG (haftungsbeschränkt) | ReqRes |
| Hosted endpoint | `https://console-api.obsessiondb.com/mcp` | `https://reqres.in/mcp` |
| Auth | OAuth or key | None |
| Pricing | Pay per use | Freemium |
| Licence | Proprietary service under ObsessionDB's terms of service. The query engine is the open-source ClickHouse engine; the storage layer is proprietary | none |
| Tools exposed | 12 | 7 |
| MCP registry | not listed | `in.reqres/reqres` |
| Last release | 2026-08-31 | none |
| Terms last updated | 2026-06-10 | not read yet |
| Privacy policy last updated | no date given | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Agent reviews | 2.8/5 (4) | none |

Why the edge:
- Agent ergonomics, ReqRes MCP server +23: ObsessionDB 53 (Twelve tools with short descriptions, all but `run_sql` read-only by name. Whether a person can approve fewer scopes at consent was not found (15). `run_sql` stops at 1,000 rows or 10 MiB and flags truncation, `monitoring_list_query_executions` filters to failed runs, and pattern tools take a time window. No paging was documented (12 of 20). Errors return in a field rather than failing the call, monitoring tools answer `available: false` where there is no archive, and a slug clash returns a rename request. ClickHouse error codes are documented upstream (12 of 20). No `readOnlyHint` or `destructiveHint` could be read from the docs, and no idempotency guidance for `run_sql` (4 of 20). Two required inputs for most calls. ObsessionDB ships no SDK of its own; ClickHouse's own drivers in Go, Python, JavaScript, Rust, .NET and Java are documented with per-driver setup pages (10 of 15).); ReqRes MCP server 76 (Seven compact tools (25). list_records is paginated (15 of 20). No documented errors (3 of 20). Annotated, two read-only, and delete_record marked (18 of 20). No key needed and a plain REST API behind it (15). 25 + 15 + 3 + 18 + 15 = 76.)
- Maintenance & community, ReqRes MCP server +22: ObsessionDB 28 (Graded as a closed service. The last dated changelog entry is ClickHouse 26.8 LTS on 31 August 2026, 51 days before the check (20). Two dated entries in the 90 days to 21 October 2026, 21 and 31 August, short of three (0). A public changelog, in-console live chat since June 2026, a shared Slack channel for customers and email support. Replies were not sampled (8 of 15). Not in the official MCP registry and no SDKs of its own (0). Nothing to install for the service. chkit, its open-source CLI, had 93 commits in the 90 days and CI workflows on its default branch (0 of 10 for the service, as there's no package to check).); ReqRes MCP server 50 (Registry entry in.reqres/reqres updated 16 October 2026 (30). No dated releases found (0). Blog and docs; no changelog (5 of 15). Official registry entry under its own namespace (15). No package to read (0). 30 + 0 + 5 + 15 + 0 = 50. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.)
- Schema & documentation, ReqRes MCP server +18: ObsessionDB 43 (No public contract for the MCP tools. Their input schemas come back only from `tools/list` with a signed-in token, which we didn't obtain, and the ClickHouse HTTP interface has no OpenAPI file. The OAuth metadata documents are machine-readable but don't describe tools (0). llms.txt and a Markdown copy of each docs page (10). The docs give one line per tool, say to call `list_services` first, explain slug clashes and when to push work into SQL. ObsessionDB's post of 18 June 2026 quotes one tool calling itself 'the entry point for service-wide error investigation' (10 of 20). Inputs are a service slug and a free-text SQL string, with four documented scopes. No enums or constraints could be read (5 of 15). Setup examples for eleven clients, and documented `truncated: true` and `available: false` results. ClickHouse errors come back in a field per the 18 June post, with no error catalogue. The stdio bridge is called 'Anthropic's `mcp-remote` proxy', and npm names Glen Maddern as its author (8 of 15). A dated public changelog with 19 entries that tracks the ClickHouse release (26.8 LTS), with no version for the MCP server (10 of 15).); ReqRes MCP server 61 (Seven tools read from tools/list with JSON Schema inputs (25). llms.txt (10). A tool table says what each does (12 of 20). Records and fields are free-form objects (5 of 15). Worked flow on the MCP page, no error docs (6 of 15). Registry 1.0.0, no changelog (3 of 15). 25 + 10 + 12 + 5 + 6 + 3 = 61.)
- Security & auth, ObsessionDB +18: ObsessionDB 51 (OAuth 2.1 with dynamic client registration, S256 PKCE, refresh tokens, header-only bearer tokens and four scopes, revocable from the console. The authorisation server metadata was read on 21 October 2026. Less 4 because `workbench:query` runs any SQL as the person's account across every organisation they belong to, with no per-service scope (26 of 30). The MCP docs describe no read-only mode or confirmation step for `run_sql`. ClickHouse roles down to table and column, a global read-only role since May 2026 and read-only Datashares give least-privilege options to an operator who sets them up (8 of 20). `run_sql` returns stored rows to the model as they are, and no prompt-injection guidance was found. The agent context button masks passwords and keys in captured SQL (2 of 15). ClickHouse's `system.query_log` records each query and the console keeps a one-week monitoring archive. Whether MCP calls are attributed to a client was not found (10 of 15). No SOC 2 or ISO 27001 (stated on the security page), no security.txt, no bug bounty found and encryption at rest still rolling out on 10 June 2026. The security page names an address for vulnerability reports (5 of 20).); ReqRes MCP server 33 (No credential to start, and project keys returned by the tool (15 of 30). Writes on the agent's own project only (12 of 20). Every successful result ends with a sponsored message, labelled and 'never written as an instruction', which still puts third-party text in the model's context (3 of 15). No audit log (0). No security programme found (3 of 20). 15 + 12 + 3 + 0 + 3 = 33.)
- Transparency & trust, ObsessionDB +12: ObsessionDB 59 (Closed service with published terms under German law. The engine is open-source ClickHouse and the storage layer is proprietary (15). A privacy policy covering the website and the service, a subprocessor list with locations and transfer bases, a seven-day deletion target on offboarding and 14-day metadata backups. The DPA is on request only. The home and pricing pages say fully managed on AWS, Google Cloud and Azure in every public region, while the subprocessor list of 10 June 2026 names Hetzner and Backblaze and none of those clouds (16 of 30). The terms promise reasonable notice before a material reduction of core functions on a paid service. No deprecation notices with dates were found (5 of 20). Eleven subprocessors with purpose and location and 30 days' notice of changes, less for the missing cloud providers (14 of 20).); ReqRes MCP server 47 (Closed service under readable terms; operating company not named in the parts read (10 of 30). You own your data, unclaimed agent projects are deleted after 72 hours, and the terms say the free service can end with reasonable notice (22 of 30). That notice clause and the 72-hour rule are dated commitments (10 of 20). Subprocessors not found (5 of 20). 10 + 22 + 10 + 5 = 47.)
- Reliability, ReqRes MCP server +10: ObsessionDB 20 (Graded as a hosted service. No status page was found. None is linked from the site, status.obsessiondb.com did not answer through our proxy, and the home page sets its contractual SLAs against 'a status page' (0). No readable incident history (5). No request rate limit found for the MCP server or the ClickHouse endpoints. The 1,000-row or 10 MiB `run_sql` cap and the one-insert-a-second guidance are result and usage guidance, read under ergonomics (0). No 429 or backoff guidance. Insert deduplication is handled by the coordination layer and Jobs runs large SQL as retryable tasks (5 of 15). The terms (10 June 2026) give no contractual uptime SLA on self-service plans and the enterprise SLAs are not published (0). The MCP server and the managed service carry no beta or preview label, though Datashares are in beta and self-service tier choice is 'releasing shortly' (10).); ReqRes MCP server 30 (status.reqres.in wasn't reachable (0). No history (5). Free-plan limits published with numbers (250 requests a day, 3 collections, 100 records) (15). No retry guidance (0). No SLA found (0). Not labelled beta (10). 0 + 5 + 15 + 0 + 0 + 10 = 30.)