# MongoDB MCP Server vs ReqRes MCP server (slim)

> MongoDB scores 80.2 (A) to ReqRes's 48.8 (D) for document databases. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/mongodb-mcp-vs-reqres-mcp.md (~4,650 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/mongodb-mcp-vs-reqres-mcp.json · canonical https://www.anchorterminal.com/compare/mongodb-mcp-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)

MongoDB MCP Server scores 80.2 (A) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 6 of 7 scored categories. Both do document databases.

- MongoDB MCP Server: A 80.2, rank #13 of 1510 · https://www.anchorterminal.com/tools/mongodb-mcp.min.md
- ReqRes MCP server: D 48.8, rank #1114 of 1510 · https://www.anchorterminal.com/tools/reqres-mcp.min.md
- MongoDB MCP Server, good for Agents that query or administer MongoDB and Atlas, with read-only and confirmation controls an operator can rely on. Ahead on Reliability, 88 against 30; Schema & documentation, 81 against 61; Security & auth, 81 against 33; Payments & pricing, 60 against 50; Maintenance & community, 94 against 50; Transparency & trust, 84 against 47. Also Agent-ready, a grade of BB or better; Runs on your own machine; Open source.
- ReqRes MCP server, good for Coding agents that need a throwaway or starter backend for a prototype, with no account to set up. Also No key needed to call it; A hosted endpoint, with nothing to install.

| Category | MongoDB MCP Server | ReqRes MCP server |
| --- | --- | --- |
| Reliability (16%) | 88 | 30 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 61 |
| Agent ergonomics (13%) | 75 | 76 |
| Security & auth (14%) | 81 | 33 |
| Payments & pricing (10%) | 60 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 94 | 50 |
| Transparency & trust (7%) | 84 | 47 |

| Fact (where they differ) | MongoDB MCP Server | ReqRes MCP server |
| --- | --- | --- |
| Vendor | MongoDB | ReqRes |
| Hosted endpoint | no (local only) | `https://reqres.in/mcp` |
| Transports | stdio, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | None |
| Pricing | Free | Freemium |
| Licence | Apache-2.0 | none |
| Tools exposed | 53 | 7 |
| Read-only variant documented | yes | no |
| MCP registry | `io.github.mongodb-js/mongodb-mcp-server` | `in.reqres/reqres` |
| Last release | 2026-10-29 | none |
| Terms last updated | no date given | not read yet |
| Privacy policy last updated | 2025-11-04 | 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 | 3.5/5 (8) | none |

Why the edge:
- Reliability, MongoDB MCP Server +58: MongoDB MCP Server 88 (Scored as a local stdio package (it also runs over HTTP). Official npm package mongodb-mcp-server, 3.2.2 as the npm latest on 1 November, and a Docker image, with Node `^20.19.0 || ^22.13.0 || >= 24.0.0` stated in `engines` (20). CI runs unit and integration tests on Ubuntu, macOS and Windows with Node 22, plus Node 24 and 26 on Ubuntu, alongside accuracy and end-to-end suites. The latest Code Health runs on main concluded Success on 1 October per the 4 October check (run results weren't readable on 17 October or 1 November), and the test job is still marked `continue-on-error` in a clone on 1 November, so a failing test leg wouldn't fail the run. 20 of 25. Ten open issues on 1 November, five of them bug reports (#1269 OIDC connect, #1427 output schemas declared as draft-07, #1490 a false COLLSCAN on sharded clusters, #1540 space-separated `--disabledTools` values ignored, #1643 aggregations that keep running after a cancel), three of them labelled stale with no activity. Most issues opened since 20 October are newer requests (20). Semver with major versions for breaking changes. MongoDB's docs keep dated release notes, still ending at 3.0.5 of 1 October on 1 November and listing neither 3.1.0 nor 3.2.x. The GitHub v3.2.1 release (28 October) has full notes, including the `maxTimeMS` deprecation, but the v3.0.0 release body is still empty per the 4 October check, and 3.2.2 is on npm without a tag or release (13). Version 3.2.2 (15).); 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.)
- Security & auth, MongoDB MCP Server +48: MongoDB MCP Server 81 (Database tools use a MongoDB user's own roles. Atlas tools use Atlas service accounts (client ID and secret) with per-operation roles listed in the README, connecting to an Atlas cluster creates a temporary database user that expires after 4 hours, and the managed server uses OAuth. Secrets can go on the command line, which the README warns against (25). `--readOnly` removes create, update and delete tools, `--indexCheck` rejects collection scans and server-side JavaScript is off by default. Confirmation is on by default for eight risky tools, but a client without elicitation runs them unconfirmed, and read-only isn't the default (18). Documents and query results come back wrapped in per-call UUID tags with a warning not to follow instructions inside them, on by default. Version 3.1.0 (15 October) adds `--disableUntrustedDataWarning`, default false, which returns results without the tags (13). Logs go to disk and to the MCP client by default, and Atlas keeps its own activity feed (10). MongoDB publishes a vulnerability disclosure policy, and its trust page lists ISO/IEC 27001:2022 and SOC reports for Atlas, per the 4 October check. The repository still has no SECURITY.md on 1 November ("This project has not set up a SECURITY.md file yet") and publishes no advisories, OSV listed none on 17 October, and mongodb.com/.well-known/security.txt answered with the site's HTML page, not a security.txt, per the 17 October check, not re-read on 1 November (15).); 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.)
- Maintenance & community, MongoDB MCP Server +44: MongoDB MCP Server 94 (npm latest 3.2.2 on 29 October 2026, after v3.2.1 on 28 October (30). Thirteen stable releases from v2.0.0 (published 4 August) through 3.2.2 in the 90 days to 1 November (20). Commits on main most days (23 since v3.1.0, the latest on 30 October), a stale bot that labels inactive issues, and ten open issues on 1 November, five opened since 20 October (20). Listed in the official MCP registry as io.github.mongodb-js/mongodb-mcp-server, a GitHub-verified namespace. After the 21 October fix to the publish step, the registry's latest entry on 1 November is 3.2.1, published 28 October, one patch behind npm's 3.2.2, so the 2 held back since 4 October for the stale 2.1.0 entry are restored (15). Dependabot, CodeQL and a dependency-health workflow, and releases upload an SBOM. The failed Docker release (#1312) was closed as not planned by the stale bot on 3 September without a fix, and 3.2.2 shipped a day after 3.2.1 because two library packages failed to import (9).); 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.)
- Transparency & trust, MongoDB MCP Server +37: MongoDB MCP Server 84 (Apache-2.0 (30). The README says where logs and exports live, that exports expire after 5 minutes and that both may hold sensitive data, and MongoDB's privacy policy (last updated 4 November 2025) covers usage data from its products (22). Deprecated options are marked in the configuration table (`connectionScope`, `healthCheckHost`, and since 3.2.1 `maxTimeMS` and the two count caps in favour of `timeoutMs`) and Node 20 support is flagged for removal, but without dates (12). Telemetry is on by default and the README documents three opt-outs (`MDB_MCP_TELEMETRY=disabled`, `--telemetry disabled`, `DO_NOT_TRACK=1`). It says only "usage data". The source shows tool name, duration, result and a device id, and 3.1.0 fixes events emitted after close being dropped (15).); 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.)
- Schema & documentation, MongoDB MCP Server +20: MongoDB MCP Server 81 (Every tool takes a typed zod schema, and read tools such as `find` declare output schemas (25). MongoDB serves an llms.txt for the MCP server docs at mongodb.com/docs/mcp-server/llms.txt, live on 17 October and linked from the release notes page read on 1 November (10). Some descriptions say when to use them (`list-connections` says "Use this to find a connectionId established earlier", the streams tools list the requests they fit), but most database tools get one line ("Run a find query against a MongoDB collection"). Issues #1375 (66 parameters without descriptions) and #1402 (tools that confuse agents) are no longer in the open list on 1 November, and the README descriptions are unchanged since 17 October (12). Sort directions are enums and `limit` and `responseBytesLimit` have defaults. Filters and projections are free-form EJSON, which MQL needs (10). README and docs carry config examples. Errors come back as `Error running <tool>: <message>` with `isError` set (10). Semver, GitHub releases, dated release notes in the docs from 1.8.1 to 3.0.5 and a server.json for the registry (14, less 1 because the docs page still lists neither 3.1.0 nor 3.2.x on 1 November and 3.2.2 has no GitHub release).); 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.)
- Payments & pricing, MongoDB MCP Server +10: MongoDB MCP Server 60 (The server is free and open source, and runs against any MongoDB with no signup, so 20 + 20 + 20. No payment protocol (0). Atlas itself is billed by MongoDB with public plan pricing. On 4 October the pricing page listed Free at $0 with 512 MB, Flex up to $30 a month and Dedicated from $56.94 a month.); ReqRes MCP server 50 (No machine payment protocol (0). Plan prices public (10). Free plan (20). An agent creates a project with no person (20). 0 + 10 + 20 + 20 = 50.)