{ "data": { "a": { "slug": "netlify", "name": "Netlify API + MCP", "vendor": "Netlify, Inc.", "vendorUrl": "https://www.netlify.com", "kind": "http-api", "category": "infrastructure", "summary": "Netlify's platform for deploying and running web projects, reached through a REST API with a public OpenAPI spec, the netlify-cli command line tool and an official MCP server, hosted at netlify-mcp.netlify.app or run locally from npm.", "url": "https://www.anchorterminal.com/tools/netlify", "markdownUrl": "https://www.anchorterminal.com/tools/netlify.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/netlify.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/netlify.json", "dns": "netlify.grade.anchorterminal.com", "repo": "https://github.com/netlify/netlify-mcp", "license": "ISC for the MCP server (@netlify/mcp) and MIT for the CLI (netlify-cli). The Netlify platform they act on is a proprietary service under Netlify's terms", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.netlify.com/api/v1", "packages": [ { "registry": "npm", "name": "@netlify/mcp" }, { "registry": "npm", "name": "netlify-cli" } ], "auth": "mixed", "authNotes": "Personal access tokens from Applications \u003e Personal access tokens, named, given an expiry date at creation and sent as `Authorization: Bearer`; no scopes are documented, SAML teams need an opt-in at creation, and a password reset invalidates every token. Public integrations use OAuth2 apps registered at app.netlify.com/applications (the spec declares an implicit flow with no scopes). The CLI stores a token from `netlify login` in config.json or reads `NETLIFY_AUTH_TOKEN`. The hosted MCP server signs in with OAuth 2.1 (PKCE, dynamic client registration) and advertises the scopes offline_access, read, write and claudeai; the local server reads the CLI's token or `NETLIFY_PERSONAL_ACCESS_TOKEN`.", "pricing": "freemium", "pricingNotes": "Free plan at $0 with 300 credits a month, deploys from the API, functions, Blobs, Database and custom domains. Personal $9 a month with 1,000 credits, Pro $20 a month with unlimited members and 3,000 credits, Enterprise custom with a 99.99 per cent SLA. Usage is metered in credits, about $0.00667 each at the Pro pack rate (1,500 for $10; Personal 500 for $5). A production deploy is 15 credits, bandwidth 20 a GB, compute 10 a GB-hour and web requests 2 per 10,000. Whether a card is needed is not stated. `netlify deploy --allow-anonymous` publishes without an account, to be claimed within an hour.", "priceSummary": "$9 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI spec (no 402 response), the API guide, the MCP source or the pricing page (checked 2026-11-03).", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": null, "npmWeekly": 58373, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.netlify.com/api-and-cli-guides/api-guides/get-started-with-api/", "llmsTxt": "https://docs.netlify.com/llms.txt", "openapi": "https://raw.githubusercontent.com/netlify/open-api/master/swagger.yml", "capabilities": [ "infra.cloud", "code.deploy", "observability.logs" ], "tags": [ "hosted", "freemium", "free-tier", "mcp", "remote-mcp", "cli", "oauth", "pat", "llms-txt", "openapi", "status-page", "bug-bounty", "soc2", "iso27001", "sla", "typescript", "go", "agent-skills", "enterprise" ], "lastRelease": "2026-10-26", "graded": true, "anchor": { "graded": true, "score": 69.4, "grade": "B", "agentReady": false, "rank": 226, "ranked": true, "rankOf": 1349, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 87, "payments": 55, "reliability": 67, "schema": 79, "security": 59, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "A public OpenAPI spec with 188 operations, documented rate limits, an anonymous deploy route and an MCP server released weekly through October 2026 with complete tool annotations. Personal access tokens and the OAuth flows carry no scopes, the hosted MCP enforces none on tool calls, and the status feed shows several site-serving incidents in the 90 days to 3 November.", "bestFor": "An agent that builds and deploys web projects, sets environment variables and reads forms or logs on a team's Netlify account, including with no account through anonymous deploys.", "strengths": [ "OpenAPI spec (Swagger 2.0, version 2.63.1) with 188 operations, llms.txt and a Markdown twin of every docs page", "Rate limits published (500 a minute, 3 deploys a minute, 100 a day) with X-RateLimit headers on every response", "`netlify deploy --allow-anonymous` publishes a project without an account, claimable within an hour", "MCP server with OAuth 2.1 and PKCE, every tool hint declared since v1.18.0 (7 October 2026), and six tagged releases between 25 September and 26 October", "Public HackerOne bug bounty, SOC 2 Type II, ISO 27001 and 27018, and a trust centre with a downloadable DPA and subprocessor list" ], "weaknesses": [ "Personal access tokens and OAuth apps have no scopes, so a token reaches every team its owner belongs to", "The hosted MCP server advertises read and write scopes but its source enforces none on tool calls", "No idempotency keys for deploys or site creation, and no documented 429 retry guidance beyond the headers", "19 incidents in the status feed from 18 August to 2 November 2026, including errors reaching hosted sites for about 85 minutes on 21 September", "No entry in the official MCP registry, and the privacy statement contradicts itself on AI training (opt-in in one section, never in another)" ], "agentNotes": [ "Send a `User-Agent` naming your app and `Authorization: Bearer $NETLIFY_AUTH_TOKEN`; watch X-RateLimit-Remaining and stop before 3 deploys a minute or 100 a day", "Deploy with `netlify deploy --allow-anonymous` when the person has no account yet, and tell them to claim the project within an hour", "Poll GET /api/v1/deploys/{deploy_id} until `state` is `ready`; a deploy call that runs over 30 seconds is cut off, so send large deploys with `\"async\": true`", "Page lists with `page` and `per_page` (100 at most) and follow the `Link` header's `rel=\"next\"`", "Expect the hosted MCP's deploy tool to hand back a CLI command for the person to run; the local server deploys from the working directory itself" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.4 } ], "editorialScores": { "ergonomics": 69, "maintenance": 87, "payments": 55, "reliability": 67, "schema": 79, "security": 59, "transparency": 73 }, "provenanceScore": 89, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g netlify-cli", "http": "curl -H \"User-Agent: MyApp (you@example.com)\" -H \"Authorization: Bearer $NETLIFY_AUTH_TOKEN\" https://api.netlify.com/api/v1/sites", "claudeCode": "claude mcp add --transport http netlify https://netlify-mcp.netlify.app/mcp", "config": { "mcpServers": { "netlify": { "url": "https://netlify-mcp.netlify.app/mcp" } } } }, "letme": { "capability": "https://letme.dev/infra.cloud", "tool": "https://letme.dev/netlify" }, "area": "developer", "unitPrices": [ { "item": "Personal", "unit": "month", "usd": 9, "note": "1,000 credits a month" }, { "item": "Pro", "unit": "month", "usd": 20, "note": "Unlimited members, 3,000 credits a month" }, { "item": "Credit (Pro pack)", "unit": "credit", "usd": 0.00667, "note": "1,500 credits for $10. A production deploy is 15 credits, bandwidth 20 a GB, compute 10 a GB-hour" }, { "item": "Bandwidth", "unit": "gb", "usd": 0.13, "note": "20 credits a GB at the Pro pack rate" } ], "provenance": { "legalEntity": "Netlify, Inc.", "domain": "netlify.com", "domainRegistered": "2014-06-09", "endpointOnVendorDomain": true, "terms": "https://www.netlify.com/legal/terms-of-use/", "privacy": "https://www.netlify.com/privacy/", "statusPage": "https://www.netlifystatus.com", "changelog": "https://www.netlify.com/changelog/", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms of use (last updated 14 October 2026) name Netlify, Inc. under California law and contain no clause on automated access or scraping; the services run under separate self-serve and enterprise subscription agreements, the self-serve one served as a PDF our reader could not extract.", "The privacy statement (last updated 10 April 2026) names Netlify, Inc. and affiliates, a DPA for enterprise customers, and says in one place that content is not used to train AI models unless the user opts in and in another that Customer Content is never used for training.", "www.netlify.com and docs.netlify.com robots.txt allow every crawler, name ClaudeBot and Claude-Web among allowed AI crawlers, and set Content-Signal search=yes, ai-input=yes, ai-train=yes. www.netlifystatus.com disallows /api/ and /embed/, so the status history was read from /history.atom.", "RDAP gives netlify.com a registration date of 9 June 2014.", "www.netlify.com/.well-known/security.txt returns 404. Vulnerability reports go to the public HackerOne programme per the security transparency post.", "The trust centre at netlify.com/trust-center lists subprocessors (all US) with CSV and PDF downloads and an RSS feed, and the DPA as a direct download." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/netlify.json", "live": { "slug": "netlify", "probe": { "target": "https://api.netlify.com/api/v1", "method": "get", "lastAt": "2026-11-04T20:47:02.5486596Z", "lastOk": true, "lastStatus": 401, "lastMs": 511, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 457, "p95ms24h": 548, "samples24h": 55, "samples30d": 55, "days": [ { "date": "2026-11-04", "probes": 55, "ok": 55 } ] }, "vendorStatus": { "page": "https://www.netlifystatus.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T20:39:30.739538782Z" }, "versions": [ { "registry": "github", "name": "netlify/netlify-mcp", "version": "mcp-v1.21.0", "released": "2026-10-26", "seenAt": "2026-11-04T20:39:31.488292719Z" }, { "registry": "npm", "name": "@netlify/mcp", "version": "1.21.0", "seenAt": "2026-11-04T20:39:29.42118318Z" }, { "registry": "npm", "name": "netlify-cli", "version": "27.16.2", "seenAt": "2026-11-04T20:39:30.256102488Z" } ], "githubStars": 69, "npmWeekly": 54818, "securityTxt": { "url": "https://netlify.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:05.436387975Z" }, "updatedAt": "2026-11-04T20:47:02.5486596Z" } }, "answer": "Netlify API + MCP scores 69.4 (B) on agent readiness against Render MCP Server's 66.9 (B), and leads in 4 of 7 scored categories. Render MCP Server leads on reliability.", "b": { "slug": "render-mcp-server", "name": "Render MCP Server", "vendor": "Render Services, Inc.", "vendorUrl": "https://render.com", "kind": "mcp", "category": "infrastructure", "summary": "Render's official MCP server lets an agent create services and data stores on the Render cloud platform, trigger deploys, read logs and metrics, and run read-only SQL on Render Postgres. It is hosted at mcp.render.com.", "url": "https://www.anchorterminal.com/tools/render-mcp-server", "markdownUrl": "https://www.anchorterminal.com/tools/render-mcp-server.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/render-mcp-server.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/render-mcp-server.json", "dns": "render-mcp-server.grade.anchorterminal.com", "repo": "https://github.com/render-oss/render-mcp-server", "license": "Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://mcp.render.com/mcp", "packages": [ { "registry": "oci", "name": "ghcr.io/render-oss/render-mcp-server" } ], "auth": "mixed", "authNotes": "OAuth or a Render API key. The hosted server answers 401 with a pointer to its protected-resource metadata, which names the authorisation server at api.render.com and no scopes, and the server rejects revoked tokens through introspection. Render documents OAuth for Claude Code, Claude Desktop, Codex and Cursor. Other clients send an API key as `Authorization: Bearer`. A person creates the key in the dashboard, it does not expire, it can be revoked, and it reaches every workspace its owner belongs to.", "pricing": "byo-plan", "pricingNotes": "The server itself is free. Tools act on a Render workspace and bill under its plan. Hobby is $0 a month plus compute, Pro $25 and Scale $499, with Enterprise priced by sales. Compute runs from a free 512 MB instance to $7 a month and up, prorated to the second. The free-tier docs describe workspaces with no payment method, whose free services are suspended when the 750 monthly free instance hours run out. Free Postgres databases expire 30 days after creation (checked 2026-10-08).", "priceSummary": "Your plan", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP server docs, the repository README, llms.txt or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 26, "popularity": { "githubStars": 176, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://render.com/docs/mcp-server", "llmsTxt": "https://render.com/llms.txt", "openapi": "https://api-docs.render.com/openapi/render-public-api-1.json", "capabilities": [ "infra.cloud", "code.deploy", "observability.logs", "observability.metrics", "db.sql" ], "tags": [ "official", "hosted", "open-source", "mcp", "oauth", "api-key", "llms-txt", "openapi", "status-page", "soc2", "free-tier" ], "lastRelease": "2026-01-14", "graded": true, "anchor": { "graded": true, "score": 66.9, "grade": "B", "agentReady": false, "rank": 314, "ranked": true, "rankOf": 1349, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 56, "payments": 40, "reliability": 78, "schema": 78, "security": 58, "transparency": 84 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "A hosted server with 26 typed and annotated tools, OAuth or API key access and Apache-2.0 source. It cannot delete resources and wraps SQL in a read-only transaction. There are no scopes and no read-only mode, a key reaches every workspace its owner belongs to, and the last tagged release is from January 2026.", "bestFor": "Agents that deploy and debug applications on Render, reading logs and metrics and querying Postgres.", "strengths": [ "All 26 tools declare typed inputs and carry read-only, destructive and open-world annotations in the Apache-2.0 source.", "The server has no delete tools, and `query_render_postgres` runs each query inside a read-only transaction.", "OAuth sign-in since 22 July 2026 for Claude Code, Codex and Cursor, with revoked tokens rejected through introspection, and API keys kept for CI and other non-interactive use.", "The Hobby workspace costs $0 a month with free instances, and the free-tier docs describe use without a payment method.", "Render holds SOC 2 Type 2 and ISO 27001, publishes a valid security.txt and takes reports through HackerOne." ], "weaknesses": [ "No scopes and no read-only mode. An API key reaches every workspace its owner belongs to, and a read-only toolset request has been open since 8 October 2025.", "Render's status page has no MCP component. Eight build and deploy incidents from 20 August to 21 October 2026 affected what the deploy tools start.", "Logs and database rows reach the model with no prompt-injection guidance found, and the docs say secrets may be exposed.", "The last tagged release is v0.3.0 of 14 January 2026. The hosted server carries no version number.", "No entry for the server was found in the official MCP registry on 2 November, and six of 14 open issues had no reply on 8 October." ], "agentNotes": [ "Pass `workspaceId` on every resource tool call. Session-based workspace selection through `select_workspace` is deprecated and scheduled for removal.", "Do not call `trigger_deploy` after pushing to a service with autoDeploy on. The push already starts a deploy.", "Use an API key in the `Authorization` header for CI. OAuth grants expire and need a person to approve the browser flow again.", "`update_environment_variables` merges by default. Set `replace` to true only to overwrite the whole set.", "Expect 429 from the Render API at 20 service creations an hour and 10 deploys a minute per service. Back off with jitter." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 66.9 } ], "editorialScores": { "ergonomics": 69, "maintenance": 56, "payments": 40, "reliability": 78, "schema": 78, "security": 58, "transparency": 71 }, "provenanceScore": 97, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http render https://mcp.render.com/mcp --header \"Authorization: Bearer \u003cYOUR_API_KEY\u003e\"", "config": { "mcpServers": { "render": { "headers": { "Authorization": "Bearer \u003cYOUR_API_KEY\u003e" }, "url": "https://mcp.render.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/infra.cloud", "tool": "https://letme.dev/render-mcp-server" }, "area": "developer", "unitPrices": [ { "item": "Hobby workspace", "unit": "month", "usd": 0, "note": "plus compute" }, { "item": "Pro workspace", "unit": "month", "usd": 25, "note": "plus compute" }, { "item": "Scale workspace", "unit": "month", "usd": 499, "note": "plus compute" }, { "item": "Web service, 0.5 CPU and 512 MB", "unit": "month", "usd": 7, "note": "prorated to the second" }, { "item": "Web service, 1 CPU and 2 GB", "unit": "month", "usd": 25, "note": "prorated to the second" }, { "item": "Postgres, 0.1 CPU and 256 MB", "unit": "month", "usd": 6 }, { "item": "Key Value, 256 MB", "unit": "month", "usd": 10 } ], "provenance": { "legalEntity": "Render Services, Inc.", "domain": "render.com", "domainRegistered": "1998-10-01", "endpointOnVendorDomain": true, "terms": "https://render.com/terms", "privacy": "https://render.com/privacy", "statusPage": "https://status.render.com", "changelog": "https://render.com/changelog", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The Terms of Service (last modified 10 July 2026) name Render Services, Inc., 525 Brannan Street Ste 300, San Francisco, CA 94107, and cover the platform and its APIs, incorporating the Acceptable Use Policy, the Data Processing Addendum and the Privacy Policy.", "The Privacy Policy is also dated 10 July 2026. Customer personal data processed on the platform is governed by the DPA at render.com/dpa.", "The MCP server answers at mcp.render.com and its OAuth server at api.render.com, both render.com subdomains.", "render.com/.well-known/security.txt names security@render.com and the HackerOne programme and expires on 3 October 2027.", "RDAP for render.com gives a registration date of 1998-10-01.", "The Markdown twins of the terms and privacy pages hold only a title, so both documents were read from the HTML pages." ], "score": 97 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/render-mcp-server.json", "live": { "slug": "render-mcp-server", "probe": { "target": "https://mcp.render.com/mcp", "method": "mcp-initialize", "lastAt": "2026-11-04T20:47:10.849496144Z", "lastOk": true, "lastStatus": 401, "lastMs": 261, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 206, "p95ms24h": 429, "samples24h": 246, "samples30d": 6644, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 214, "ok": 214 } ] }, "vendorStatus": { "page": "https://status.render.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T20:39:54.399429341Z" }, "versions": [ { "registry": "github", "name": "render-oss/render-mcp-server", "version": "v0.3.0", "released": "2026-01-14", "seenAt": "2026-11-03T20:53:42.381099028Z" } ], "githubStars": 184, "securityTxt": { "url": "https://render.com/.well-known/security.txt", "state": "valid", "expires": "2027-10-03T00:00:00.000Z", "checkedAt": "2026-11-04T15:54:45.930691251Z" }, "llmsTxt": { "url": "https://render.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:24:02.14002526Z" }, "domain": { "domain": "render.com", "registered": "1998-10-01", "source": "https://rdap.verisign.com/com/v1/domain/render.com", "checkedAt": "2026-11-01T14:10:40.705598315Z" }, "pages": [ { "url": "https://render.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-04T08:31:21.679359042Z", "changedAt": "2026-11-03T07:57:21.182116926Z", "fingerprint": "84eb72e3a64a" }, { "url": "https://render.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:31:24.484283318Z", "changedAt": "2026-11-03T07:57:23.537267414Z", "fingerprint": "9605e4f2908d" }, { "url": "https://render.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:31:26.386316181Z", "changedAt": "2026-11-03T07:57:25.470770966Z", "fingerprint": "9057d3bdd1c9" } ], "mcpTools": { "url": "https://mcp.render.com/mcp", "checkedAt": "2026-11-04T01:23:01.85681248Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:54.635433453Z" }, "github": { "repo": "render-oss/render-mcp-server", "checkedAt": "2026-11-02T09:21:06.313496753Z", "stars": 184, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-01T00:37:23Z", "openIssues": 13, "openPRs": 0, "issuesOpened90d": 6, "issuesClosed90d": 2, "prsMerged90d": 0, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-11-01T00:39:10Z" }, "replies": { "sampled": 19, "unanswered": 13, "medianDays": 20.4 } }, "updatedAt": "2026-11-04T20:47:10.849496144Z" } }, "edges": [ { "by": 31, "category": "maintenance", "leads": "netlify", "name": "Maintenance \u0026 community", "reasons": { "a": "@netlify/mcp 1.21.0 tagged on 26 October 2026 (changelog 23 October), a commit on 28 October, the spec at 2.63.1 and changelog entries to 26 October (30). Six MCP tags between 25 September and 26 October 2026 (20). Issue and pull request responsiveness could not be read (github.com refuses our reader and the API answered empty), while the changelog, the answers.netlify.com forum, Discord and a support hub exist and the MCP changelog cites numbered pull requests (12 of 25). Current official SDKs, a Go client, a JS client and netlify-cli 27.16.2, though the server card names com.netlify/mcp and no such entry is in the official MCP registry (15). CI runs typecheck, build and 31 tests on pinned actions, releases through release-please with npm provenance, and the server runs on @modelcontextprotocol/server 2.2.0 (10). 30 + 20 + 12 + 15 + 10 = 87.", "b": "The main branch had commits changing tools on 12 and 22 October 2026 (input validation, a 5 MB cap on `query_render_postgres` results, UTC timestamps in `list_events`) and dependency commits to 1 November, and Render says the hosted server updates as tools are added. The last tag is still v0.3.0 of 14 January 2026, so 25 of 30. No tagged release in 90 days, and Render's two MCP changelog entries (17 and 22 July 2026) are now outside the window, while the source added Dockerfile-based creation and `list_events` in September and the October changes above (15 of 20). Five Blueprint tools were added to the source from 26 to 30 October, and a test keeps them unregistered. 14 open issues, six with no reply, per the 8 October check, not re-read on 2 November (8 of 25). No entry in the official MCP registry in three searches on 2 November (0). Go 1.27.3, mcp-go 1.4.0, pinned dependencies with Renovate and a test workflow. The workflow's result was not seen (8 of 10). 25 + 15 + 8 + 0 + 8 = 56." }, "scores": { "a": 87, "b": 56 } }, { "by": 15, "category": "payments", "leads": "netlify", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Plan prices and per-unit credit prices (deploys, bandwidth, compute, requests, credit packs) are public without a login (20). A Free plan with 300 credits a month and API deploys, and the docs do not say a card is needed (20). `netlify deploy --allow-anonymous` publishes a project and URL with no account, claimable within an hour, but the API, the MCP server and anything past that hour need a person to sign up and approve a token (15 of 20). 0 + 20 + 20 + 15 = 55.", "b": "No x402 or other machine payment (0). The server is free and plan and instance prices are public, by the month and prorated to the second (20). The Hobby workspace is $0 with free instances, and the docs describe workspaces with no payment method (20). A person has to sign up, then approve OAuth or create a key in the dashboard (0)." }, "scores": { "a": 55, "b": 40 } }, { "by": 11, "category": "reliability", "leads": "render-mcp-server", "name": "Reliability", "reasons": { "a": "Read with the hosted lines. Statuspage at netlifystatus.com with component history and an Atom feed (20). From 5 August to 3 November 2026 the feed lists 19 incidents and no maintenance. None names the API or the MCP server. Errors reaching hosted sites and the Netlify application for about 85 minutes on 21 September read as one major outage; errors on the edge network for 55 minutes on 5 October, CDN DNS errors for 34 minutes on 24 September, 6 minutes of 500s on 18 August, and build, Agent Runner, AI Gateway and log-delay incidents read as minor (10 of 30). Limits are published with numbers, about 500 requests a minute, 3 deploys a minute and 100 a day, with X-RateLimit headers (15). The docs say retrying a timed-out upload is safe and give the reset header, but no backoff guidance, no idempotency key for deploys or site creation, and 429 appears in the spec only on agent runner endpoints (7 of 15). A 99.99 per cent SLA is named for Enterprise on the pricing page, with its terms in order forms (5 of 10). The API is generally available (10). 20 + 10 + 15 + 7 + 5 + 10 = 67.", "b": "Scored as a hosted server. status.render.com is a Statuspage with component history, though the MCP server has no component of its own (20). From 4 August to 2 November 2026 its history feed lists 14 incidents and three maintenance notices. None names the MCP server or the REST API it calls. Eight touch builds and deploys, which the server's create and deploy tools start, among them deploys in every region on 20 August (an upstream Google Cloud issue, about four hours), Singapore on 31 August and builds not starting in any region for nearly three hours on 14 October. Each hit one function or one region, so all read as minor. The dashboard, email, network and Key Value incidents don't touch the server, and the REST API's two maintenance windows were announced ahead (20 of 30). The 8 October count came from a status data path robots.txt disallows and is struck. The REST API's limits are published with numbers, such as 400 GET a minute and 10 deploys a minute per service (15). The docs give rate-limit headers and advise backoff with jitter on 429, but there is no idempotency key for deploys or service creation (10 of 15). The pricing page lists contractual uptime SLAs for Enterprise without publishing the terms (5 of 10). The server has been generally available since 21 August 2025 per Render's changelog, though the source is versioned 0.x (8 of 10). 20 + 20 + 15 + 10 + 5 + 8 = 78." }, "scores": { "a": 67, "b": 78 } } ], "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "Netlify, Inc.", "b": "Render Services, Inc.", "name": "Vendor" }, { "a": "https://api.netlify.com/api/v1", "b": "https://mcp.render.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, stdio", "b": "Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Your plan", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "ISC for the MCP server (@netlify/mcp) and MIT for the CLI (netlify-cli). The Netlify platform they act on is a proprietary service under Netlify's terms", "b": "Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service", "name": "Licence" }, { "a": "11", "b": "26", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-26", "b": "2026-01-14", "name": "Last release" }, { "a": "2026-10-14", "b": "2026-07-10", "name": "Terms last updated" }, { "a": "2026-04-10", "b": "2026-07-10", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "58k npm/wk", "b": "176 stars", "name": "Popularity" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Netlify API + MCP scores 69.4 (B) on agent readiness against Render MCP Server's 66.9 (B), and leads in 4 of 7 scored categories. Render MCP Server leads on reliability.", "question": "Which is better for AI agents, Netlify API + MCP or Render MCP Server?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Netlify API + MCP and Render MCP Server need an API key?" }, { "answer": "Yes. Netlify API + MCP has a hosted endpoint at https://api.netlify.com/api/v1 and Render MCP Server at https://mcp.render.com/mcp.", "question": "Can an agent call Netlify API + MCP and Render MCP Server without installing anything?" }, { "answer": "No open-source release is listed for Netlify API + MCP. Render MCP Server is open source (Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service).", "question": "Are Netlify API + MCP and Render MCP Server open source?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 55 against 40", "Maintenance \u0026 community, 87 against 56" ], "also": null, "goodFor": "An agent that builds and deploys web projects, sets environment variables and reads forms or logs on a team's Netlify account, including with no account through anonymous deploys.", "slug": "netlify", "watchFor": "Personal access tokens and OAuth apps have no scopes, so a token reaches every team its owner belongs to" }, { "aheadOn": [ "Reliability, 78 against 67" ], "also": [ "Open source" ], "goodFor": "Agents that deploy and debug applications on Render, reading logs and metrics and querying Postgres.", "slug": "render-mcp-server", "watchFor": "No scopes and no read-only mode. An API key reaches every workspace its owner belongs to, and a read-only toolset request has been open since 8 October 2025." } ], "history": { "netlify": null, "render-mcp-server": [ { "causes": [ "product", "correction" ], "date": "2026-11-02", "delta": 3.3, "from": 63.6, "fromGrade": "B", "to": 66.9, "toGrade": "B" } ] }, "job": { "capability": "infra.cloud", "name": "Cloud hosting" }, "others": [ { "json": "https://www.anchorterminal.com/compare/azure-mcp-vs-netlify.json", "title": "Azure MCP Server vs Netlify API + MCP", "url": "https://www.anchorterminal.com/compare/azure-mcp-vs-netlify" }, { "json": "https://www.anchorterminal.com/compare/azure-mcp-vs-render-mcp-server.json", "title": "Azure MCP Server vs Render MCP Server", "url": "https://www.anchorterminal.com/compare/azure-mcp-vs-render-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/digitalocean-mcp-vs-netlify.json", "title": "DigitalOcean MCP Server vs Netlify API + MCP", "url": "https://www.anchorterminal.com/compare/digitalocean-mcp-vs-netlify" }, { "json": "https://www.anchorterminal.com/compare/digitalocean-mcp-vs-render-mcp-server.json", "title": "DigitalOcean MCP Server vs Render MCP Server", "url": "https://www.anchorterminal.com/compare/digitalocean-mcp-vs-render-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/neckbeard-vs-netlify.json", "title": "neckbeard vs Netlify API + MCP", "url": "https://www.anchorterminal.com/compare/neckbeard-vs-netlify" }, { "json": "https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server.json", "title": "neckbeard vs Render MCP Server", "url": "https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/netlify-vs-railway-mcp-server.json", "title": "Netlify API + MCP vs Railway MCP Server", "url": "https://www.anchorterminal.com/compare/netlify-vs-railway-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/netlify-vs-terraform-mcp.json", "title": "Netlify API + MCP vs Terraform MCP Server", "url": "https://www.anchorterminal.com/compare/netlify-vs-terraform-mcp" }, { "json": "https://www.anchorterminal.com/compare/railway-mcp-server-vs-render-mcp-server.json", "title": "Railway MCP Server vs Render MCP Server", "url": "https://www.anchorterminal.com/compare/railway-mcp-server-vs-render-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/render-mcp-server-vs-terraform-mcp.json", "title": "Render MCP Server vs Terraform MCP Server", "url": "https://www.anchorterminal.com/compare/render-mcp-server-vs-terraform-mcp" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-cli-vs-netlify.json", "title": "Cloudflare CLI (cf) vs Netlify API + MCP", "url": "https://www.anchorterminal.com/compare/cloudflare-cli-vs-netlify" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-cli-vs-render-mcp-server.json", "title": "Cloudflare CLI (cf) vs Render MCP Server", "url": "https://www.anchorterminal.com/compare/cloudflare-cli-vs-render-mcp-server" } ], "panel": null, "scores": [ { "by": 11, "edge": "render-mcp-server", "key": "reliability", "name": "Reliability", "netlify": 67, "render-mcp-server": 78, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "edge": "netlify", "key": "schema", "name": "Schema \u0026 documentation", "netlify": 79, "render-mcp-server": 78, "weight": 13 }, { "by": 0, "edge": "", "key": "ergonomics", "name": "Agent ergonomics", "netlify": 69, "render-mcp-server": 69, "weight": 13 }, { "by": 1, "edge": "netlify", "key": "security", "name": "Security \u0026 auth", "netlify": 59, "render-mcp-server": 58, "weight": 14 }, { "by": 15, "edge": "netlify", "key": "payments", "name": "Payments \u0026 pricing", "netlify": 55, "render-mcp-server": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 31, "edge": "netlify", "key": "maintenance", "name": "Maintenance \u0026 community", "netlify": 87, "render-mcp-server": 56, "weight": 7 }, { "by": 3, "edge": "render-mcp-server", "key": "transparency", "name": "Transparency \u0026 trust", "netlify": 81, "render-mcp-server": 84, "weight": 7 } ], "summary": "Netlify API + MCP scores 69.4 (B) on agent readiness against Render MCP Server's 66.9 (B), and leads in 4 of 7 scored categories. Render MCP Server leads on reliability. Both do cloud hosting.", "tasks": null, "tutorials": [], "verdicts": { "netlify": "A public OpenAPI spec with 188 operations, documented rate limits, an anonymous deploy route and an MCP server released weekly through October 2026 with complete tool annotations. Personal access tokens and the OAuth flows carry no scopes, the hosted MCP enforces none on tool calls, and the status feed shows several site-serving incidents in the 90 days to 3 November.", "render-mcp-server": "A hosted server with 26 typed and annotated tools, OAuth or API key access and Apache-2.0 source. It cannot delete resources and wraps SQL in a read-only transaction. There are no scopes and no read-only mode, a key reaches every workspace its owner belongs to, and the last tagged release is from January 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server", "json": "https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server.min.md" }, "markdown": "Netlify API + MCP scores 69.4 (B) on agent readiness against Render MCP Server's 66.9 (B), and leads in 4 of 7 scored categories. Render MCP Server leads on reliability. Both do cloud hosting.\n\n- Netlify API + MCP: grade B, 69.4/100, rank #226 of 1349. Markdown https://www.anchorterminal.com/tools/netlify.md · JSON https://www.anchorterminal.com/api/v1/tools/netlify.json\n- Render MCP Server: grade B, 66.9/100, rank #314 of 1349. Markdown https://www.anchorterminal.com/tools/render-mcp-server.md · JSON https://www.anchorterminal.com/api/v1/tools/render-mcp-server.json\n- Best cloud infrastructure tools for AI agents: https://www.anchorterminal.com/best/infrastructure/index.md\n- All 31 infra comparisons: https://www.anchorterminal.com/compare/infrastructure/index.md\n\n## Which one, for what\n\n### Netlify API + MCP (B)\n\nGood for: An agent that builds and deploys web projects, sets environment variables and reads forms or logs on a team's Netlify account, including with no account through anonymous deploys.\n\nAhead on:\n- Payments \u0026 pricing, 55 against 40\n- Maintenance \u0026 community, 87 against 56\n\nWatch for: Personal access tokens and OAuth apps have no scopes, so a token reaches every team its owner belongs to\n\n### Render MCP Server (B)\n\nGood for: Agents that deploy and debug applications on Render, reading logs and metrics and querying Postgres.\n\nAhead on:\n- Reliability, 78 against 67\n\nAlso in its favour:\n- Open source\n\nWatch for: No scopes and no read-only mode. An API key reaches every workspace its owner belongs to, and a read-only toolset request has been open since 8 October 2025.\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Netlify API + MCP +31\n\n- Netlify API + MCP (87): @netlify/mcp 1.21.0 tagged on 26 October 2026 (changelog 23 October), a commit on 28 October, the spec at 2.63.1 and changelog entries to 26 October (30). Six MCP tags between 25 September and 26 October 2026 (20). Issue and pull request responsiveness could not be read (github.com refuses our reader and the API answered empty), while the changelog, the answers.netlify.com forum, Discord and a support hub exist and the MCP changelog cites numbered pull requests (12 of 25). Current official SDKs, a Go client, a JS client and netlify-cli 27.16.2, though the server card names com.netlify/mcp and no such entry is in the official MCP registry (15). CI runs typecheck, build and 31 tests on pinned actions, releases through release-please with npm provenance, and the server runs on @modelcontextprotocol/server 2.2.0 (10). 30 + 20 + 12 + 15 + 10 = 87.\n- Render MCP Server (56): The main branch had commits changing tools on 12 and 22 October 2026 (input validation, a 5 MB cap on `query_render_postgres` results, UTC timestamps in `list_events`) and dependency commits to 1 November, and Render says the hosted server updates as tools are added. The last tag is still v0.3.0 of 14 January 2026, so 25 of 30. No tagged release in 90 days, and Render's two MCP changelog entries (17 and 22 July 2026) are now outside the window, while the source added Dockerfile-based creation and `list_events` in September and the October changes above (15 of 20). Five Blueprint tools were added to the source from 26 to 30 October, and a test keeps them unregistered. 14 open issues, six with no reply, per the 8 October check, not re-read on 2 November (8 of 25). No entry in the official MCP registry in three searches on 2 November (0). Go 1.27.3, mcp-go 1.4.0, pinned dependencies with Renovate and a test workflow. The workflow's result was not seen (8 of 10). 25 + 15 + 8 + 0 + 8 = 56.\n\n### Payments \u0026 pricing: Netlify API + MCP +15\n\n- Netlify API + MCP (55): No x402, MPP or L402 (0). Plan prices and per-unit credit prices (deploys, bandwidth, compute, requests, credit packs) are public without a login (20). A Free plan with 300 credits a month and API deploys, and the docs do not say a card is needed (20). `netlify deploy --allow-anonymous` publishes a project and URL with no account, claimable within an hour, but the API, the MCP server and anything past that hour need a person to sign up and approve a token (15 of 20). 0 + 20 + 20 + 15 = 55.\n- Render MCP Server (40): No x402 or other machine payment (0). The server is free and plan and instance prices are public, by the month and prorated to the second (20). The Hobby workspace is $0 with free instances, and the docs describe workspaces with no payment method (20). A person has to sign up, then approve OAuth or create a key in the dashboard (0).\n\n### Reliability: Render MCP Server +11\n\n- Netlify API + MCP (67): Read with the hosted lines. Statuspage at netlifystatus.com with component history and an Atom feed (20). From 5 August to 3 November 2026 the feed lists 19 incidents and no maintenance. None names the API or the MCP server. Errors reaching hosted sites and the Netlify application for about 85 minutes on 21 September read as one major outage; errors on the edge network for 55 minutes on 5 October, CDN DNS errors for 34 minutes on 24 September, 6 minutes of 500s on 18 August, and build, Agent Runner, AI Gateway and log-delay incidents read as minor (10 of 30). Limits are published with numbers, about 500 requests a minute, 3 deploys a minute and 100 a day, with X-RateLimit headers (15). The docs say retrying a timed-out upload is safe and give the reset header, but no backoff guidance, no idempotency key for deploys or site creation, and 429 appears in the spec only on agent runner endpoints (7 of 15). A 99.99 per cent SLA is named for Enterprise on the pricing page, with its terms in order forms (5 of 10). The API is generally available (10). 20 + 10 + 15 + 7 + 5 + 10 = 67.\n- Render MCP Server (78): Scored as a hosted server. status.render.com is a Statuspage with component history, though the MCP server has no component of its own (20). From 4 August to 2 November 2026 its history feed lists 14 incidents and three maintenance notices. None names the MCP server or the REST API it calls. Eight touch builds and deploys, which the server's create and deploy tools start, among them deploys in every region on 20 August (an upstream Google Cloud issue, about four hours), Singapore on 31 August and builds not starting in any region for nearly three hours on 14 October. Each hit one function or one region, so all read as minor. The dashboard, email, network and Key Value incidents don't touch the server, and the REST API's two maintenance windows were announced ahead (20 of 30). The 8 October count came from a status data path robots.txt disallows and is struck. The REST API's limits are published with numbers, such as 400 GET a minute and 10 deploys a minute per service (15). The docs give rate-limit headers and advise backoff with jitter on 429, but there is no idempotency key for deploys or service creation (10 of 15). The pricing page lists contractual uptime SLAs for Enterprise without publishing the terms (5 of 10). The server has been generally available since 21 August 2025 per Render's changelog, though the source is versioned 0.x (8 of 10). 20 + 20 + 15 + 10 + 5 + 8 = 78.\n\n## Score by category\n\n| Category | Weight | Netlify API + MCP | Render MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 67 | 78 | Render MCP Server +11 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 78 | Netlify API + MCP +1 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 69 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 59 | 58 | Netlify API + MCP +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 55 | 40 | Netlify API + MCP +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 87 | 56 | Netlify API + MCP +31 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 81 | 84 | Render MCP Server +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **69.4 · B** | **66.9 · B** | |\n\n## Facts side by side\n\n| Fact | Netlify API + MCP | Render MCP Server |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | Netlify, Inc. | Render Services, Inc. |\n| Hosted endpoint | `https://api.netlify.com/api/v1` | `https://mcp.render.com/mcp` |\n| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP, stdio |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Your plan |\n| x402 | no | no |\n| Licence | ISC for the MCP server (@netlify/mcp) and MIT for the CLI (netlify-cli). The Netlify platform they act on is a proprietary service under Netlify's terms | Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service |\n| Tools exposed | 11 | 26 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-26 | 2026-01-14 |\n| Terms last updated | 2026-10-14 | 2026-07-10 |\n| Privacy policy last updated | 2026-04-10 | 2026-07-10 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 58k npm/wk | 176 stars |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### Netlify API + MCP\n\nNo score change since it was listed.\n\n### Render MCP Server\n\n- +3.3 on 2 November 2026: product, correction\n\n## Verdicts\n\n**Netlify API + MCP.** A public OpenAPI spec with 188 operations, documented rate limits, an anonymous deploy route and an MCP server released weekly through October 2026 with complete tool annotations. Personal access tokens and the OAuth flows carry no scopes, the hosted MCP enforces none on tool calls, and the status feed shows several site-serving incidents in the 90 days to 3 November.\n\n**Render MCP Server.** A hosted server with 26 typed and annotated tools, OAuth or API key access and Apache-2.0 source. It cannot delete resources and wraps SQL in a read-only transaction. There are no scopes and no read-only mode, a key reaches every workspace its owner belongs to, and the last tagged release is from January 2026.\n\n## Before you call either\n\n### Netlify API + MCP\n\n1. Send a `User-Agent` naming your app and `Authorization: Bearer $NETLIFY_AUTH_TOKEN`; watch X-RateLimit-Remaining and stop before 3 deploys a minute or 100 a day\n2. Deploy with `netlify deploy --allow-anonymous` when the person has no account yet, and tell them to claim the project within an hour\n3. Poll GET /api/v1/deploys/{deploy_id} until `state` is `ready`; a deploy call that runs over 30 seconds is cut off, so send large deploys with `\"async\": true`\n4. Page lists with `page` and `per_page` (100 at most) and follow the `Link` header's `rel=\"next\"`\n5. Expect the hosted MCP's deploy tool to hand back a CLI command for the person to run; the local server deploys from the working directory itself\n\n### Render MCP Server\n\n1. Pass `workspaceId` on every resource tool call. Session-based workspace selection through `select_workspace` is deprecated and scheduled for removal.\n2. Do not call `trigger_deploy` after pushing to a service with autoDeploy on. The push already starts a deploy.\n3. Use an API key in the `Authorization` header for CI. OAuth grants expire and need a person to approve the browser flow again.\n4. `update_environment_variables` merges by default. Set `replace` to true only to overwrite the whole set.\n5. Expect 429 from the Render API at 20 service creations an hour and 10 deploys a minute per service. Back off with jitter.\n\n## Questions\n\n### Which is better for AI agents, Netlify API + MCP or Render MCP Server?\n\nNetlify API + MCP scores 69.4 (B) on agent readiness against Render MCP Server's 66.9 (B), and leads in 4 of 7 scored categories. Render MCP Server leads on reliability.\n\n### Do Netlify API + MCP and Render MCP Server need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Netlify API + MCP and Render MCP Server without installing anything?\n\nYes. Netlify API + MCP has a hosted endpoint at https://api.netlify.com/api/v1 and Render MCP Server at https://mcp.render.com/mcp.\n\n### Are Netlify API + MCP and Render MCP Server open source?\n\nNo open-source release is listed for Netlify API + MCP. Render MCP Server is open source (Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server.json, and with the fewest tokens: https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"netlify\", \"b\": \"render-mcp-server\"}`. From a terminal: `anchor compare netlify render-mcp-server`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/netlify.json and https://www.anchorterminal.com/api/v1/tools/render-mcp-server.json\n\n## Other comparisons with Netlify API + MCP or Render MCP Server\n\n- [Azure MCP Server vs Netlify API + MCP](https://www.anchorterminal.com/compare/azure-mcp-vs-netlify.md)\n- [Azure MCP Server vs Render MCP Server](https://www.anchorterminal.com/compare/azure-mcp-vs-render-mcp-server.md)\n- [DigitalOcean MCP Server vs Netlify API + MCP](https://www.anchorterminal.com/compare/digitalocean-mcp-vs-netlify.md)\n- [DigitalOcean MCP Server vs Render MCP Server](https://www.anchorterminal.com/compare/digitalocean-mcp-vs-render-mcp-server.md)\n- [neckbeard vs Netlify API + MCP](https://www.anchorterminal.com/compare/neckbeard-vs-netlify.md)\n- [neckbeard vs Render MCP Server](https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server.md)\n- [Netlify API + MCP vs Railway MCP Server](https://www.anchorterminal.com/compare/netlify-vs-railway-mcp-server.md)\n- [Netlify API + MCP vs Terraform MCP Server](https://www.anchorterminal.com/compare/netlify-vs-terraform-mcp.md)\n- [Railway MCP Server vs Render MCP Server](https://www.anchorterminal.com/compare/railway-mcp-server-vs-render-mcp-server.md)\n- [Render MCP Server vs Terraform MCP Server](https://www.anchorterminal.com/compare/render-mcp-server-vs-terraform-mcp.md)\n- [Cloudflare CLI (cf) vs Netlify API + MCP](https://www.anchorterminal.com/compare/cloudflare-cli-vs-netlify.md)\n- [Cloudflare CLI (cf) vs Render MCP Server](https://www.anchorterminal.com/compare/cloudflare-cli-vs-render-mcp-server.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-04", "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": "Netlify API + MCP vs Render MCP Server", "url": "" } ], "description": "Netlify scores 69.4 (B) to Render's 66.9 (B) for cloud hosting. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Netlify API + MCP B 69.4", "Render MCP Server B 66.9", "scores" ], "h1": "Netlify API + MCP vs Render MCP Server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/netlify-vs-render-mcp-server", "published": "2026-10-01", "section": "tools", "title": "Netlify vs Render for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server" }, "tokens": { "markdown": 3850, "slim": 2080 }, "version": 1 }