{ "data": { "a": { "slug": "reqres-mcp", "name": "ReqRes MCP server", "vendor": "ReqRes", "vendorUrl": "https://reqres.in", "kind": "mcp", "category": "data", "summary": "ReqRes' hosted MCP server lets a coding agent create a real hosted REST backend with no account, persistent JSON collections and API keys, then read and write its records. Unclaimed projects are deleted after 72 hours.", "url": "https://www.anchorterminal.com/tools/reqres-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/reqres-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/reqres-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/reqres-mcp.json", "dns": "reqres-mcp.grade.anchorterminal.com", "transports": [ "streamable-http" ], "remoteUrl": "https://reqres.in/mcp", "packages": [], "auth": "none", "authNotes": "No authentication. create_project returns a manage key and a public key for the new project, and a claim link that moves it to a ReqRes account.", "pricing": "freemium", "pricingNotes": "Free plan, 250 requests a day, 3 collections and 100 records a project, with a daily cap on new projects; paid plans raise it to 10,000 requests a day and more (prices on the pricing page). Tool results end with a sponsored line unless ?sponsor=0 is added (checked 2026-11-07).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://reqres.in/mcp", "llmsTxt": "https://reqres.in/llms.txt", "registryName": "in.reqres/reqres", "capabilities": [ "db.document", "code.backend", "data.store" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "no-auth", "freemium", "free-tier", "llms-txt", "mcp-registry", "annotated-tools", "sponsored-results" ], "graded": true, "anchor": { "graded": true, "score": 48.8, "grade": "D", "agentReady": false, "rank": 1114, "ranked": true, "rankOf": 1510, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 50, "payments": 50, "reliability": 30, "schema": 61, "security": 33, "transparency": 47 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-07" }, "negative": 0, "verdict": "ReqRes' MCP server is the quickest way for a coding agent to stand up a real hosted backend, with no account, seven annotated tools and paginated records. Every result carries a sponsored line by default, the free tier is small, and unclaimed projects vanish after 72 hours.", "bestFor": "Coding agents that need a throwaway or starter backend for a prototype, with no account to set up.", "strengths": [ "A hosted backend from one call, with no account", "Seven compact annotated tools with paginated records", "A claim link moves the project to an account with data intact", "llms.txt and a plain REST API behind the tools" ], "weaknesses": [ "A sponsored line in every successful result unless ?sponsor=0", "Unclaimed projects are deleted after 72 hours", "Free plan of 250 requests a day", "Status page unreachable and no changelog" ], "agentNotes": [ "Add ?sponsor=0 to the server URL to keep ads out of context", "Give the user the claim link so the project survives 72 hours", "Use the public key in frontend code and keep the manage key server-side" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 48.8 } ], "editorialScores": { "ergonomics": 76, "maintenance": 50, "payments": 50, "reliability": 30, "schema": 61, "security": 33, "transparency": 47 }, "provenanceScore": 46, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http reqres 'https://reqres.in/mcp?sponsor=0'", "config": { "mcpServers": { "reqres": { "url": "https://reqres.in/mcp?sponsor=0" } } } }, "letme": { "capability": "https://letme.dev/db.document", "tool": "https://letme.dev/reqres-mcp" }, "area": "developer", "provenance": { "legalEntity": "ReqRes", "domain": "reqres.in", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": true, "terms": "https://reqres.in/terms", "privacy": "https://reqres.in/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "The operating company wasn't named in the parts of the terms and privacy policy read." ], "score": 46 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/reqres-mcp.json", "live": { "slug": "reqres-mcp", "probe": { "target": "https://reqres.in/mcp", "method": "mcp-initialize", "lastAt": "2026-11-07T23:26:51.623285274Z", "lastOk": true, "lastStatus": 200, "lastMs": 74, "lastNote": "initialize answered", "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 92, "p95ms24h": 188, "samples24h": 48, "samples30d": 48, "days": [ { "date": "2026-11-07", "probes": 48, "ok": 48 } ] }, "updatedAt": "2026-11-07T23:26:51.623285274Z" } }, "answer": "Snowflake-managed MCP server scores 52.7 (D) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 3 of 7 scored categories. ReqRes MCP server leads on agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "snowflake-managed", "name": "Snowflake-managed MCP server", "vendor": "Snowflake Inc.", "vendorUrl": "https://www.snowflake.com", "kind": "mcp", "category": "data", "summary": "Snowflake's managed MCP server is an object created in a Snowflake account that exposes Cortex Agents, Cortex Search, Cortex Analyst, SQL execution and custom functions, each as an MCP tool, over HTTP, with OAuth and role-based access control.", "url": "https://www.anchorterminal.com/tools/snowflake-managed", "markdownUrl": "https://www.anchorterminal.com/tools/snowflake-managed.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/snowflake-managed.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json", "dns": "snowflake-managed.grade.anchorterminal.com", "license": "Proprietary service under Snowflake's terms of service", "transports": [ "streamable-http" ], "packages": [], "auth": "mixed", "authNotes": "OAuth 2.0 is the documented default. An administrator creates a Snowflake OAuth security integration (confidential, or public with PKCE) and gives its client ID and secret to the MCP client, because dynamic client registration is not supported. Since 22 July 2026 a schema, database or account can bind its MCP servers to an External OAuth integration such as Okta or Microsoft Entra ID. Scopes of the form `session:role:\u003crole_name\u003e` pick the session's primary role. Programmatic access tokens are also accepted, expire after 15 days by default and 365 at most, and Snowflake recommends OAuth over them. There is no self-serve key an agent can mint for itself.", "pricing": "usage", "pricingNotes": "No charge is listed for the MCP server itself. Tools bill at the rates of what they call. SQL and custom tools use warehouse compute in Platform Credits, from $2.00 a credit on demand for Standard edition in US regions. Cortex Agents and Cortex Search bill in AI Credits at $2.00 each with global routing. A 30-day trial needs only an email address, with Cortex tools disabled until a card is added (checked 2026-10-09).", "priceSummary": "$2 / credit", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP server docs, the AI pricing page or the Service Consumption Table (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp", "llmsTxt": "https://docs.snowflake.com/llms.txt", "capabilities": [ "db.sql", "knowledge.search", "analytics.query" ], "tags": [ "official", "hosted", "mcp", "oauth", "read-only-mode", "database", "enterprise", "llms-txt", "status-page", "soc2", "usage-priced", "free-trial" ], "lastRelease": "2026-08-20", "graded": true, "anchor": { "graded": true, "score": 52.7, "grade": "D", "agentReady": false, "rank": 978, "ranked": true, "rankOf": 1510, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 46, "maintenance": 35, "payments": 35, "reliability": 50, "schema": 61, "security": 77, "transparency": 84 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -3, "negativeNotes": [ "20 August 2026. `tools/call` responses changed from a single JSON body to an SSE stream as an unbundled behaviour change that accounts could not disable, outside the eight-week bundle process, and clients reading one JSON body broke. The only dated notice recorded is the behaviour change note dated 20 August, the day the change took effect, so it takes the same-day -3 (the 9 October check charged -2). Per the 9 October check, not re-read on 4 November (https://docs.snowflake.com/en/release-notes/bcr-bundles/un-bundled/bcr-2405)." ], "verdict": "Tools are governed by Snowflake roles, the SQL tool is read-only by default, and sign-in runs through Snowflake OAuth or a company identity provider. No rate limits or tool-call error codes were found in the reviewed documentation, and a person must create the account, the server object and the OAuth integration before an agent can connect.", "bestFor": "A company that already keeps its data in Snowflake and wants outside MCP clients to query it under existing roles, best through one Cortex Agent tool.", "strengths": [ "Each tool needs its own grant. `USAGE` on the MCP server does not give access to the agent, search service, semantic view, function or procedure behind a tool", "The SQL execution tool defaults to `read_only: true` and takes a `query_timeout` and a named warehouse", "OAuth with PKCE for public clients, role scopes, an allowed-roles list and, since 22 July 2026, binding to an external identity provider with RFC 9728 metadata", "Generally available since 4 November 2025, under a 99.9 per cent monthly availability SLA with service credits", "Per-credit prices by region and edition are public in the Service Consumption Table, and the docs publish llms.txt and Markdown copies of every page" ], "weaknesses": [ "No rate limits for the MCP endpoint and no JSON-RPC error codes were found in the reviewed documentation", "No dynamic client registration. An administrator creates a security integration and hands the client ID and secret to each MCP client", "On 20 August 2026 `tools/call` responses changed from one JSON body to an SSE stream, outside a behaviour change bundle, with no way to disable it and no earlier dated notice found", "Resources, prompts, roots, notifications, sampling, version negotiation and lifecycle phases are unsupported, and SQL and custom tool responses are cut at 250 KB", "status.snowflake.com shows two incidents marked critical (25 and 27 September 2026) and one marked major (6 October) in the 15 days its front page lists", "Cortex tools stay disabled on a trial account until a credit card is added" ], "agentNotes": [ "Send `Accept: application/json, text/event-stream` and read `tools/call` results as an SSE stream that ends with `data: [DONE]`", "Write the account hostname with hyphens, not underscores, or some clients fail to connect", "Check the user's `DEFAULT_ROLE` and `DEFAULT_WAREHOUSE` first. Clients that request `session:role:all` get the default role, and a missing warehouse stops the session starting", "Keep SQL results narrow. Responses over 250 KB are truncated with no paging, and agent tool responses can pass 200 KB", "Treat `invalid_client` from `/oauth/token-request` as a possible network policy block as well as a wrong credential" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 52.7 } ], "editorialScores": { "ergonomics": 46, "maintenance": 35, "payments": 35, "reliability": 50, "schema": 61, "security": 77, "transparency": 68 }, "provenanceScore": 99, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "config": { "mcpServers": { "snowflake": { "auth": { "CLIENT_ID": "${env:MCP_CLIENT_ID}", "CLIENT_SECRET": "${env:MCP_CLIENT_SECRET}" }, "url": "https://\u003caccount_url\u003e/api/v2/databases/\u003cdatabase\u003e/schemas/\u003cschema\u003e/mcp-servers/\u003cname\u003e" } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/snowflake-managed" }, "area": "developer", "unitPrices": [ { "item": "Platform Credit, Standard edition, on demand", "unit": "credit", "usd": 2, "note": "AWS US East. $3.00 on Enterprise. Higher in other regions. Used by SQL and custom tools through a warehouse" }, { "item": "AI Credit, global routing", "unit": "credit", "usd": 2, "note": "$2.20 with regional routing. Used by Cortex Agents and Cortex Search" } ], "provenance": { "legalEntity": "Snowflake Inc.", "domain": "snowflake.com", "domainRegistered": "1995-07-08", "endpointOnVendorDomain": true, "terms": "https://www.snowflake.com/en/legal/terms-of-service/self-service-on-demand-terms-of-service/", "privacy": "https://www.snowflake.com/en/legal/privacy/privacy-policy/", "statusPage": "https://status.snowflake.com", "changelog": "https://docs.snowflake.com/en/release-notes/new-features", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The Privacy Notice (updated 1 July 2026) names Snowflake Inc., Suite 3A, 106 East Babcock Street, Bozeman, Montana 59715, and says it does not apply to Customer Data, which the customer agreement and the DPA govern.", "The terms link is the Self-Service On Demand Terms of Service (updated 16 April 2026), which a self-serve account accepts. Contract customers sign the Master Terms at https://www.snowflake.com/en/legal/terms-of-service/.", "Each MCP server answers on the customer's account URL, which the docs give as https://\u003corgname\u003e-\u003caccount_name\u003e.snowflakecomputing.com, a second Snowflake domain.", "security.txt at www.snowflake.com/.well-known/security.txt names security@snowflake.com and a HackerOne policy, and expires on 17 August 2027.", "RDAP for snowflake.com gives a registration date of 1995-07-08." ], "score": 99 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/snowflake-managed.json", "live": { "slug": "snowflake-managed", "vendorStatus": { "page": "https://status.snowflake.com", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-11-07T23:20:05.149209514Z" }, "securityTxt": { "url": "https://snowflake.com/.well-known/security.txt", "state": "valid", "expires": "2027-08-17T19:00:00.000Z", "checkedAt": "2026-11-07T16:00:39.831604087Z" }, "llmsTxt": { "url": "https://docs.snowflake.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:58.213669404Z" }, "domain": { "domain": "snowflake.com", "registered": "1995-07-08", "source": "https://rdap.verisign.com/com/v1/domain/snowflake.com", "checkedAt": "2026-11-01T14:11:27.42351034Z" }, "pages": [ { "url": "https://docs.snowflake.com/en/release-notes/new-features", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:08:04.843173451Z", "changedAt": "2026-11-07T14:08:04.843173451Z", "fingerprint": "91d64a1e3041" }, { "url": "https://www.snowflake.com/en/legal/privacy/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:34:55.792924408Z", "changedAt": "2026-11-06T13:55:24.956430204Z", "fingerprint": "36988bbe7385" }, { "url": "https://www.snowflake.com/en/legal/terms-of-service/self-service-on-demand-terms-of-service/", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:34:57.839669214Z", "changedAt": "2026-11-06T13:55:27.763689662Z", "fingerprint": "42d8071a6e9d" } ], "updatedAt": "2026-11-07T23:20:05.149209514Z" } }, "edges": [ { "by": 44, "category": "security", "leads": "snowflake-managed", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "OAuth 2.0 with PKCE, role scopes, an allowed-roles list, binding to an external identity provider and RFC 9728 metadata. Programmatic access tokens expire (15 days by default, 365 at most), can be rotated and need a network policy by default. No dynamic client registration (28). Each tool needs its own grant, the SQL tool defaults to read-only, and the docs advise a separate least-privileged server for direct SQL. No confirmation step for writes is documented (15). The docs warn about tool poisoning, tool shadowing and recursive loops and cap recursion at 10. Nothing covers instructions arriving in query or search results (6). Account Usage has query, login and access history and a Cortex Agent usage view. No log of MCP tool calls was found (10). security.txt valid to 17 August 2027 with a HackerOne policy, SOC 2 Type II, ISO 27001, HITRUST and FedRAMP per the Security Addendum. The HackerOne page was not read (18). Per the 9 October check, not re-read on 4 November." }, "scores": { "a": 33, "b": 77 } }, { "by": 37, "category": "transparency", "leads": "snowflake-managed", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "Closed service with clear published terms, an acceptable use policy and a consumption table (15). A DPA and Security Addendum of 11 January 2026 with 72-hour incident notice and customer-chosen regions. The DPA says leftover data is deleted promptly after termination without a day count, and the Privacy Notice excludes Customer Data (22). A written behaviour change policy with an eight-week bundle period and dated notes, though the August 2026 MCP change shipped outside it (15). Four sub-processors and 28 affiliates listed with locations and 28 days' notice of additions. AI model providers are not named on the list (16). Per the 9 October check, not re-read on 4 November." }, "scores": { "a": 47, "b": 84 } }, { "by": 30, "category": "ergonomics", "leads": "reqres-mcp", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "The tool list is whatever the operator declares, up to 50 a server, and Snowflake recommends one Cortex Agent tool per server with further servers for other uses (18). The search tool takes `columns` and `limit`. SQL and custom tool responses are cut at 250 KB with no paging, and agent tool responses carry every intermediate step and can pass 200 KB (8). Errors are documented as a symptom table, and `invalid_client` covers both wrong credentials and a network policy block (6). The SQL tool is read-only by default. No `readOnlyHint` or `destructiveHint` annotations and no idempotency support are documented (6). Few required arguments and standard MCP clients work with no SDK, but each client needs a hand-made OAuth integration and some clients can't choose a role (8). Per the 9 October check, not re-read on 4 November." }, "scores": { "a": 76, "b": 46 } }, { "by": 20, "category": "reliability", "leads": "snowflake-managed", "name": "Reliability", "reasons": { "a": "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.", "b": "Graded as a hosted service. Snowflake's site terms (14 April 2025) bar robots, spiders and scrapers on snowflake.com, so the docs, the status page and www.snowflake.com were not re-read on 4 November and the 9 October readings stand. Statuspage at status.snowflake.com with components by cloud region, and no component for Cortex or the MCP server was recorded (15, the value for a vendor status page with no component for the product). Only the front page's 15 days to 9 October were read, with two incidents marked critical (one region for 68 minutes on 25 September 2026, other regions for 35 minutes on 27 September), one marked major (Snowsight connectivity, 6 October) and one minor (8 October). The rest of the window from 6 August is unread and gets no credit, so the incident line is held at the recorded 10. No rate limit for the MCP endpoint found (0). The REST API's OpenAPI files describe 429 and retry with backoff, but the MCP page gives no retry or idempotency guidance (5, partial value held). 99.9 per cent monthly SLA with service credits (10). Generally available since 4 November 2025 (10). 15+10+0+5+10+10 = 50." }, "scores": { "a": 30, "b": 50 } }, { "by": 15, "category": "payments", "leads": "reqres-mcp", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "No x402, MPP or L402 (0). Per-credit prices by region and edition and per-unit AI rates are public in the Service Consumption Table of 2 October 2026, though the MCP server has no line of its own (20). A 30-day trial needs only an email address, and Cortex tools stay off until a card is added (15). A person signs up in a browser and an administrator creates the server and the OAuth integration (0). Per the 9 October check, not re-read on 4 November." }, "scores": { "a": 50, "b": 35 } }, { "by": 15, "category": "maintenance", "leads": "reqres-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Per the 9 October check, not re-read on 4 November (snowflake.com's site terms bar robots). The last dated change to the MCP server is the SSE note of 20 August 2026, 76 days before 4 November, and platform release notes ran to 9 October (20). Of the three dated MCP entries recorded (22 July, 7 August and 20 August 2026), two fall in the 90 days from 6 August, and newer entries couldn't be looked for (0, cause time). A public changelog and a support route through cases and the community, whose answers were not sampled (10). The managed server is not in the official MCP registry, which lists only the separate open-source `io.github.Snowflake-Labs/mcp` (0). Nothing to install. The REST API specification repository was last updated on 10 September 2026 (5). 20+0+10+0+5 = 35." }, "scores": { "a": 50, "b": 35 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "ReqRes", "b": "Snowflake Inc.", "name": "Vendor" }, { "a": "https://reqres.in/mcp", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "None", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under Snowflake's terms of service", "name": "Licence" }, { "a": "7", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "in.reqres/reqres", "b": "not listed", "name": "MCP registry" }, { "a": "none", "b": "2026-08-20", "name": "Last release" }, { "a": "not read yet", "b": "2026-04-16", "name": "Terms last updated" }, { "a": "not read yet", "b": "2026-07-01", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Snowflake-managed MCP server scores 52.7 (D) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 3 of 7 scored categories. ReqRes MCP server leads on agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, ReqRes MCP server or Snowflake-managed MCP server?" }, { "answer": "ReqRes MCP server needs no key. Snowflake-managed MCP server takes an API key or an OAuth sign-in.", "question": "Do ReqRes MCP server and Snowflake-managed MCP server need an API key?" }, { "answer": "ReqRes MCP server has a hosted endpoint at https://reqres.in/mcp. No hosted endpoint is listed for Snowflake-managed MCP server.", "question": "Can an agent call ReqRes MCP server and Snowflake-managed MCP server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 76 against 46", "Payments \u0026 pricing, 50 against 35", "Maintenance \u0026 community, 50 against 35" ], "also": [ "No key needed to call it", "A hosted endpoint, with nothing to install", "No incidents deducted, where Snowflake-managed MCP server loses 3 points for them" ], "goodFor": "Coding agents that need a throwaway or starter backend for a prototype, with no account to set up.", "slug": "reqres-mcp", "watchFor": "A sponsored line in every successful result unless ?sponsor=0" }, { "aheadOn": [ "Reliability, 50 against 30", "Security \u0026 auth, 77 against 33", "Transparency \u0026 trust, 84 against 47" ], "also": null, "goodFor": "A company that already keeps its data in Snowflake and wants outside MCP clients to query it under existing roles, best through one Cortex Agent tool.", "slug": "snowflake-managed", "watchFor": "No rate limits for the MCP endpoint and no JSON-RPC error codes were found in the reviewed documentation" } ], "history": { "reqres-mcp": null, "snowflake-managed": [ { "causes": [ "correction", "time" ], "date": "2026-11-04", "delta": -3.7, "from": 56.4, "fromGrade": "C", "to": 52.7, "toGrade": "D" } ] }, "job": { "capability": "db.database", "name": "Databases" }, "others": [ { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.json", "title": "ClickHouse MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/dbhub-vs-snowflake-managed.json", "title": "DBHub vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/dbhub-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-snowflake-managed.json", "title": "MCP Toolbox for Databases vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.json", "title": "Neon MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed.json", "title": "ObsessionDB vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed.json", "title": "PlanetScale MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed.json", "title": "Postgres MCP Pro vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.json", "title": "PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/snowflake-managed-vs-supabase-mcp.json", "title": "Snowflake-managed MCP server vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/snowflake-managed-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-reqres-mcp.json", "title": "ClickHouse MCP Server vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/dbhub-vs-reqres-mcp.json", "title": "DBHub vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/dbhub-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-snowflake-managed.json", "title": "MongoDB MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.json", "title": "Neon MCP Server vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp.json", "title": "ObsessionDB vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-mcp.json", "title": "PlanetScale MCP Server vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp.json", "title": "Postgres MCP Pro vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.json", "title": "Redis MCP vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/reqres-mcp-vs-supabase-mcp.json", "title": "ReqRes MCP server vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/reqres-mcp-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-reqres-mcp.json", "title": "MCP Toolbox for Databases vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-reqres-mcp.json", "title": "MongoDB MCP Server vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp.json", "title": "Redis MCP vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp" } ], "panel": null, "scores": [ { "by": 20, "edge": "snowflake-managed", "key": "reliability", "name": "Reliability", "reqres-mcp": 30, "snowflake-managed": 50, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 0, "edge": "", "key": "schema", "name": "Schema \u0026 documentation", "reqres-mcp": 61, "snowflake-managed": 61, "weight": 13 }, { "by": 30, "edge": "reqres-mcp", "key": "ergonomics", "name": "Agent ergonomics", "reqres-mcp": 76, "snowflake-managed": 46, "weight": 13 }, { "by": 44, "edge": "snowflake-managed", "key": "security", "name": "Security \u0026 auth", "reqres-mcp": 33, "snowflake-managed": 77, "weight": 14 }, { "by": 15, "edge": "reqres-mcp", "key": "payments", "name": "Payments \u0026 pricing", "reqres-mcp": 50, "snowflake-managed": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 15, "edge": "reqres-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "reqres-mcp": 50, "snowflake-managed": 35, "weight": 7 }, { "by": 37, "edge": "snowflake-managed", "key": "transparency", "name": "Transparency \u0026 trust", "reqres-mcp": 47, "snowflake-managed": 84, "weight": 7 } ], "summary": "Snowflake-managed MCP server scores 52.7 (D) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 3 of 7 scored categories. ReqRes MCP server leads on agent ergonomics, payments \u0026 pricing and maintenance \u0026 community. Both do databases.", "tasks": null, "tutorials": [], "verdicts": { "reqres-mcp": "ReqRes' MCP server is the quickest way for a coding agent to stand up a real hosted backend, with no account, seven annotated tools and paginated records. Every result carries a sponsored line by default, the free tier is small, and unclaimed projects vanish after 72 hours.", "snowflake-managed": "Tools are governed by Snowflake roles, the SQL tool is read-only by default, and sign-in runs through Snowflake OAuth or a company identity provider. No rate limits or tool-call error codes were found in the reviewed documentation, and a person must create the account, the server object and the OAuth integration before an agent can connect." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed", "json": "https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed.min.md" }, "markdown": "Snowflake-managed MCP server scores 52.7 (D) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 3 of 7 scored categories. ReqRes MCP server leads on agent ergonomics, payments \u0026 pricing and maintenance \u0026 community. Both do databases.\n\n- ReqRes MCP server: grade D, 48.8/100, rank #1114 of 1510. Markdown https://www.anchorterminal.com/tools/reqres-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/reqres-mcp.json\n- Snowflake-managed MCP server: grade D, 52.7/100, rank #978 of 1510. Markdown https://www.anchorterminal.com/tools/snowflake-managed.md · JSON https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json\n- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md\n- All 111 databases comparisons: https://www.anchorterminal.com/compare/data/index.md\n\n## Which one, for what\n\n### ReqRes MCP server (D)\n\nGood for: Coding agents that need a throwaway or starter backend for a prototype, with no account to set up.\n\nAhead on:\n- Agent ergonomics, 76 against 46\n- Payments \u0026 pricing, 50 against 35\n- Maintenance \u0026 community, 50 against 35\n\nAlso in its favour:\n- No key needed to call it\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where Snowflake-managed MCP server loses 3 points for them\n\nWatch for: A sponsored line in every successful result unless ?sponsor=0\n\n### Snowflake-managed MCP server (D)\n\nGood for: A company that already keeps its data in Snowflake and wants outside MCP clients to query it under existing roles, best through one Cortex Agent tool.\n\nAhead on:\n- Reliability, 50 against 30\n- Security \u0026 auth, 77 against 33\n- Transparency \u0026 trust, 84 against 47\n\nWatch for: No rate limits for the MCP endpoint and no JSON-RPC error codes were found in the reviewed documentation\n\n\n## Why the edge\n\n### Security \u0026 auth: Snowflake-managed MCP server +44\n\n- 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.\n- Snowflake-managed MCP server (77): OAuth 2.0 with PKCE, role scopes, an allowed-roles list, binding to an external identity provider and RFC 9728 metadata. Programmatic access tokens expire (15 days by default, 365 at most), can be rotated and need a network policy by default. No dynamic client registration (28). Each tool needs its own grant, the SQL tool defaults to read-only, and the docs advise a separate least-privileged server for direct SQL. No confirmation step for writes is documented (15). The docs warn about tool poisoning, tool shadowing and recursive loops and cap recursion at 10. Nothing covers instructions arriving in query or search results (6). Account Usage has query, login and access history and a Cortex Agent usage view. No log of MCP tool calls was found (10). security.txt valid to 17 August 2027 with a HackerOne policy, SOC 2 Type II, ISO 27001, HITRUST and FedRAMP per the Security Addendum. The HackerOne page was not read (18). Per the 9 October check, not re-read on 4 November.\n\n### Transparency \u0026 trust: Snowflake-managed MCP server +37\n\n- 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.\n- Snowflake-managed MCP server (84): Closed service with clear published terms, an acceptable use policy and a consumption table (15). A DPA and Security Addendum of 11 January 2026 with 72-hour incident notice and customer-chosen regions. The DPA says leftover data is deleted promptly after termination without a day count, and the Privacy Notice excludes Customer Data (22). A written behaviour change policy with an eight-week bundle period and dated notes, though the August 2026 MCP change shipped outside it (15). Four sub-processors and 28 affiliates listed with locations and 28 days' notice of additions. AI model providers are not named on the list (16). Per the 9 October check, not re-read on 4 November.\n\n### Agent ergonomics: ReqRes MCP server +30\n\n- 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.\n- Snowflake-managed MCP server (46): The tool list is whatever the operator declares, up to 50 a server, and Snowflake recommends one Cortex Agent tool per server with further servers for other uses (18). The search tool takes `columns` and `limit`. SQL and custom tool responses are cut at 250 KB with no paging, and agent tool responses carry every intermediate step and can pass 200 KB (8). Errors are documented as a symptom table, and `invalid_client` covers both wrong credentials and a network policy block (6). The SQL tool is read-only by default. No `readOnlyHint` or `destructiveHint` annotations and no idempotency support are documented (6). Few required arguments and standard MCP clients work with no SDK, but each client needs a hand-made OAuth integration and some clients can't choose a role (8). Per the 9 October check, not re-read on 4 November.\n\n### Reliability: Snowflake-managed MCP server +20\n\n- 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.\n- Snowflake-managed MCP server (50): Graded as a hosted service. Snowflake's site terms (14 April 2025) bar robots, spiders and scrapers on snowflake.com, so the docs, the status page and www.snowflake.com were not re-read on 4 November and the 9 October readings stand. Statuspage at status.snowflake.com with components by cloud region, and no component for Cortex or the MCP server was recorded (15, the value for a vendor status page with no component for the product). Only the front page's 15 days to 9 October were read, with two incidents marked critical (one region for 68 minutes on 25 September 2026, other regions for 35 minutes on 27 September), one marked major (Snowsight connectivity, 6 October) and one minor (8 October). The rest of the window from 6 August is unread and gets no credit, so the incident line is held at the recorded 10. No rate limit for the MCP endpoint found (0). The REST API's OpenAPI files describe 429 and retry with backoff, but the MCP page gives no retry or idempotency guidance (5, partial value held). 99.9 per cent monthly SLA with service credits (10). Generally available since 4 November 2025 (10). 15+10+0+5+10+10 = 50.\n\n### Payments \u0026 pricing: ReqRes MCP server +15\n\n- 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.\n- Snowflake-managed MCP server (35): No x402, MPP or L402 (0). Per-credit prices by region and edition and per-unit AI rates are public in the Service Consumption Table of 2 October 2026, though the MCP server has no line of its own (20). A 30-day trial needs only an email address, and Cortex tools stay off until a card is added (15). A person signs up in a browser and an administrator creates the server and the OAuth integration (0). Per the 9 October check, not re-read on 4 November.\n\n### Maintenance \u0026 community: ReqRes MCP server +15\n\n- 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.\n- Snowflake-managed MCP server (35): Per the 9 October check, not re-read on 4 November (snowflake.com's site terms bar robots). The last dated change to the MCP server is the SSE note of 20 August 2026, 76 days before 4 November, and platform release notes ran to 9 October (20). Of the three dated MCP entries recorded (22 July, 7 August and 20 August 2026), two fall in the 90 days from 6 August, and newer entries couldn't be looked for (0, cause time). A public changelog and a support route through cases and the community, whose answers were not sampled (10). The managed server is not in the official MCP registry, which lists only the separate open-source `io.github.Snowflake-Labs/mcp` (0). Nothing to install. The REST API specification repository was last updated on 10 September 2026 (5). 20+0+10+0+5 = 35.\n\n## Score by category\n\n| Category | Weight | ReqRes MCP server | Snowflake-managed MCP server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 30 | 50 | Snowflake-managed MCP server +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 61 | even |\n| Agent ergonomics | 13% (16.2 this run) | 76 | 46 | ReqRes MCP server +30 |\n| Security \u0026 auth | 14% (17.5 this run) | 33 | 77 | Snowflake-managed MCP server +44 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 35 | ReqRes MCP server +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 50 | 35 | ReqRes MCP server +15 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 47 | 84 | Snowflake-managed MCP server +37 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **48.8 · D** | **52.7 · D** | |\n\n## Facts side by side\n\n| Fact | ReqRes MCP server | Snowflake-managed MCP server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | ReqRes | Snowflake Inc. |\n| Hosted endpoint | `https://reqres.in/mcp` | no (local only) |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | None | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | none | Proprietary service under Snowflake's terms of service |\n| Tools exposed | 7 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | `in.reqres/reqres` | not listed |\n| Last release | none | 2026-08-20 |\n| Terms last updated | not read yet | 2026-04-16 |\n| Privacy policy last updated | not read yet | 2026-07-01 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | yes |\n\n## How the scores have moved\n\n### ReqRes MCP server\n\nNo score change since it was listed.\n\n### Snowflake-managed MCP server\n\n- -3.7 on 4 November 2026 (C to D): correction, time\n\n## Verdicts\n\n**ReqRes MCP server.** ReqRes' MCP server is the quickest way for a coding agent to stand up a real hosted backend, with no account, seven annotated tools and paginated records. Every result carries a sponsored line by default, the free tier is small, and unclaimed projects vanish after 72 hours.\n\n**Snowflake-managed MCP server.** Tools are governed by Snowflake roles, the SQL tool is read-only by default, and sign-in runs through Snowflake OAuth or a company identity provider. No rate limits or tool-call error codes were found in the reviewed documentation, and a person must create the account, the server object and the OAuth integration before an agent can connect.\n\n## Before you call either\n\n### ReqRes MCP server\n\n1. Add ?sponsor=0 to the server URL to keep ads out of context\n2. Give the user the claim link so the project survives 72 hours\n3. Use the public key in frontend code and keep the manage key server-side\n\n### Snowflake-managed MCP server\n\n1. Send `Accept: application/json, text/event-stream` and read `tools/call` results as an SSE stream that ends with `data: [DONE]`\n2. Write the account hostname with hyphens, not underscores, or some clients fail to connect\n3. Check the user's `DEFAULT_ROLE` and `DEFAULT_WAREHOUSE` first. Clients that request `session:role:all` get the default role, and a missing warehouse stops the session starting\n4. Keep SQL results narrow. Responses over 250 KB are truncated with no paging, and agent tool responses can pass 200 KB\n5. Treat `invalid_client` from `/oauth/token-request` as a possible network policy block as well as a wrong credential\n\n## Questions\n\n### Which is better for AI agents, ReqRes MCP server or Snowflake-managed MCP server?\n\nSnowflake-managed MCP server scores 52.7 (D) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 3 of 7 scored categories. ReqRes MCP server leads on agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do ReqRes MCP server and Snowflake-managed MCP server need an API key?\n\nReqRes MCP server needs no key. Snowflake-managed MCP server takes an API key or an OAuth sign-in.\n\n### Can an agent call ReqRes MCP server and Snowflake-managed MCP server without installing anything?\n\nReqRes MCP server has a hosted endpoint at https://reqres.in/mcp. No hosted endpoint is listed for Snowflake-managed MCP server.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed.json, and with the fewest tokens: https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"reqres-mcp\", \"b\": \"snowflake-managed\"}`. From a terminal: `anchor compare reqres-mcp snowflake-managed`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/reqres-mcp.json and https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json\n\n## Other comparisons with ReqRes MCP server or Snowflake-managed MCP server\n\n- [ClickHouse MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.md)\n- [DBHub vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/dbhub-vs-snowflake-managed.md)\n- [MCP Toolbox for Databases vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-snowflake-managed.md)\n- [Neon MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.md)\n- [ObsessionDB vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed.md)\n- [PlanetScale MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed.md)\n- [Postgres MCP Pro vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed.md)\n- [PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.md)\n- [Snowflake-managed MCP server vs Supabase API + MCP](https://www.anchorterminal.com/compare/snowflake-managed-vs-supabase-mcp.md)\n- [ClickHouse MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-reqres-mcp.md)\n- [DBHub vs ReqRes MCP server](https://www.anchorterminal.com/compare/dbhub-vs-reqres-mcp.md)\n- [MongoDB MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-snowflake-managed.md)\n- [Neon MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.md)\n- [ObsessionDB vs ReqRes MCP server](https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp.md)\n- [PlanetScale MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-mcp.md)\n- [Postgres MCP Pro vs ReqRes MCP server](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp.md)\n- [PostgreSQL (archived MCP reference server) vs ReqRes MCP server](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp.md)\n- [Redis MCP vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.md)\n- [ReqRes MCP server vs Supabase API + MCP](https://www.anchorterminal.com/compare/reqres-mcp-vs-supabase-mcp.md)\n- [MCP Toolbox for Databases vs ReqRes MCP server](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-reqres-mcp.md)\n- [MongoDB MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-reqres-mcp.md)\n- [Redis MCP vs ReqRes MCP server](https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "ReqRes MCP server vs Snowflake-managed MCP server", "url": "" } ], "description": "Snowflake-managed scores 52.7 (D) to ReqRes's 48.8 (D) for databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ReqRes MCP server D 48.8", "Snowflake-managed MCP server D 52.7", "scores" ], "h1": "ReqRes MCP server vs Snowflake-managed MCP server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/reqres-mcp-vs-snowflake-managed", "published": "2026-10-01", "section": "tools", "title": "ReqRes vs Snowflake-managed for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed" }, "tokens": { "markdown": 4450, "slim": 2580 }, "version": 1 }