Render MCP Server

# Fix list: Render MCP Server

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/render-mcp-server, the October 2026 research run, assessed 8 October 2026. Grade B, 63.6 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Render MCP Server: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Payments & pricing, 40 out of 100, up to 7.5 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 2. Reliability, 63 out of 100, up to 7.4 more on the total

Why it scored 63: Scored as a hosted server. status.render.com is a Statuspage with component history (20). From 15 July to 3 October 2026 it lists 16 incidents, four critical and five major, among them the dashboard unavailable for 32 minutes on 15 July, web services in Oregon disrupted for over two hours on 24 July, deploy failures for nearly four hours on 20 August and instability in Singapore for over two hours on 31 August. Two of the critical ones were GitHub outages. The REST API the server calls was named in one minor incident, and the MCP server is not a component (5 of 30). 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 docs carry no beta label, though the source is versioned 0.x (8 of 10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 3. Security & auth, 58 out of 100, up to 7.4 more on the total

Why it scored 58: OAuth with PKCE, refresh and revocation, or a revocable API key. The OAuth metadata lists no scopes, and a key reaches every workspace its owner belongs to (20 of 30). There is no read-only mode and no confirmation step on the server. The tool set itself is limited, with no deletions, SQL wrapped in a read-only transaction and a workspace check before writes, and Render warns that environment variable updates and deploys can be destructive (9 of 20). Logs and database rows are untrusted content. The docs warn that secrets may reach the model's context, and no prompt-injection guidance was found (3 of 15). Workspace audit logs on Pro and above are kept at least 90 days. Whether they mark MCP calls was not found (9 of 15). Valid security.txt, a HackerOne disclosure programme, SOC 2 Type 2 and ISO 27001. No paid bounty was established (17 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 4. Agent ergonomics, 69 out of 100, up to 5 more on the total

Why it scored 69: 26 tools with no toolsets or read-only subset, which an issue has requested since 8 October 2025 (15 of 25). `list_logs` pages by time window with `hasMore` and takes nine filters and a limit. The other list tools were not read in full (15 of 20). Errors pass through the API's messages, with a written explanation when a Postgres IP allowlist blocks a query. No documented error codes (11 of 20). Every tool carries read-only, destructive and open-world hints and 22 carry an idempotent hint, but a deploy cannot be retried safely with a key (16 of 20). Few required parameters, merge-by-default for environment variables, and Render publishes Python and TypeScript SDKs and a CLI (12 of 15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 5. Schema & documentation, 76 out of 100, up to 3.9 more on the total

Why it scored 76: Every tool declares typed inputs through mcp-go, though two open issues from 22 September 2026 report `list_logs` and `create_cron_job` accepting invalid values (23 of 25). llms.txt and a Markdown twin of every docs page (10). Descriptions say what a tool does, and some say when not to use it, as `trigger_deploy` does for services with autoDeploy on (15 of 20). Enums, defaults and bounds are present, such as `direction` and a `limit` of 1 to 100 on `list_logs` (11 of 15). The README lists each tool with its parameters and the docs give example prompts. No list of error responses was found (8 of 15). Render's changelog dates MCP changes, but the last tag is v0.3.0 of 14 January 2026 and the hosted server has no version (9 of 15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 6. Maintenance & community, 56 out of 100, up to 3.9 more on the total

Why it scored 56: The main branch had feature commits on 24 and 25 September 2026 and dependency commits to 8 October, and Render says the hosted server updates as tools are added. The last tag is v0.3.0 of 14 January 2026, so 25 of 30. No tagged release in 90 days. Render's changelog has two MCP entries, on 17 and 22 July 2026, and the source added `list_events` and Dockerfile-based creation in September (15 of 20). 14 open issues, six with no reply, including an OAuth failure in Claude Code from 3 August 2026 and a TLS error on queries from October 2025 (8 of 25). No entry was found in the official MCP registry in three searches (0). Go 1.27, mcp-go 1.1.1, pinned dependencies and a test workflow with the race detector. The workflow's result was not seen (8 of 10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 7. Transparency & trust, 84 out of 100, up to 1.4 more on the total

Made of editorial 71, provenance 97.

Why it scored 84: The server is Apache-2.0 and the platform is closed with clear terms (28 of 30). A privacy policy and a DPA, both published. Retention is stated in general words, and nothing covers how long the hosted server keeps sessions or OAuth grants (20 of 30). The README says session-based workspace selection is deprecated and scheduled for removal, with no date. The terms let Render change or stop the Service without notice, while the API docs promise backward compatibility (8 of 20). Four sub-processors with countries on render.com/security, Data Privacy Framework certification, and ten days' notice of a new sub-processor under the DPA (15 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Terms of service: read, states 6 of the 7 things a reader expects, and has 1 clause that costs points (7.1 of 10)

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: whether the commits on the main branch are what runs at mcp.render.com. The hosted server shows no version.
- unchecked: the result of the Go test workflow on the default branch. GitHub's API refused us for its rate limit.
- unchecked: security incidents at Render in the last 12 months beyond the status page. No incident page or advisory list was searched, so the deduction is 0 on what was read.
- unchecked: whether workspace audit logs record MCP tool calls and mark their origin, and whether a Viewer role limits an API key.
- unchecked: the terms of the Enterprise uptime SLA, which are not published.
- The official MCP registry returned no Render entry for the searches com.render, render-oss and render-mcp-server. A search for render timed out once and then returned 30 unrelated servers.
- The Acceptable Use Policy forbids automated access to the Service without written consent, while the Terms of Service allow authorised AI tools. This matters before our probes run.
- `lastRelease` is the last tag (14 January 2026). The last feature commit on the main branch was 25 September 2026.

## 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.
- status.render.com lists 16 incidents from 15 July to 3 October 2026, four critical and five major, mostly on builds, deploys and the dashboard.
- 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, and six of 14 open issues have no reply.

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- 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.

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.