RRender MCP (official, remote)

Vendor-hosted
What we probed (2026-11-11, no credentials): an MCP initialize POST to https://mcp.render.com/mcp returned HTTP 401 with an OAuth challenge (authorization server https://api.render.com). We did not sign in or use a key, so no tools were listed or called. Render's docs state this endpoint, show setup with a Render API key in an Authorization: Bearer header (OAuth via Render's plugins), and link the source repo render-oss/render-mcp-server (Apache-2.0, 200 GitHub stars when checked). Tools create and manage services, databases and deploys and query Postgres, so they can change your Render account. Core tools not tested.

Transport: Streamable HTTP · not tested

Score 65/100 · Tools 0 · Token cost pending · Compare · Last tested 2026-11-11 · Server version not reported · Remote endpoint https://mcp.render.com/mcp (streamable-http) · Repo render-oss/render-mcp-server

Summary: Render MCP (official, remote) requires credentials or a backing service before it will list tools.

Evidence summary

Handshake

auth-gated

Tools listed

0

Context cost

Pending The token cost figure is pending. ranking

Login

Needs OAuth sign-in

Tested

2026-11-11

Test results

Local-model readiness

What we tested and what we didn't

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

{
  "name": "render-remote",
  "version": null,
  "registry": "remote",
  "status": "auth-gated",
  "tested": "2026-11-11",
  "tools_count": null,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "Endpoint https://mcp.render.com/mcp reachable over streamable-http (HTTP 401) in 0.1s; no install step for remote servers."
    ],
    "handshake": [
      "auth-gated",
      5,
      "Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.render.com/.well-known/oauth-protected-resource/mcp; metadata lists authorization server https://api.render.com). We do not sign in; not counted as working until a credentialed test exists."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 0 days before test; 200 GitHub stars."
    ],
    "docs": [
      "partial",
      5,
      "README over 3,000 chars. Check of the package's own README (vendor repo README (github.com/render-oss/render-mcp-server))."
    ],
    "license": [
      "pass",
      10,
      "Apache-2.0 (OSI-approved)."
    ]
  }
}

Install

https://mcp.render.com/mcpCopy

Tools listed

Not available (handshake did not complete without credentials).

Quick config

{
  "mcpServers": {
    "render-mcp-remote": {
      "type": "http",
      "url": "https://mcp.render.com/mcp"
    }
  }
}

Add to config Opens the config generator with this server selected.

{
  "mcpServers": {
    "render-mcp-remote": {
      "type": "http",
      "url": "https://mcp.render.com/mcp"
    }
  }
}

Related: Troubleshooting: 401 Unauthorized on remote servers · MCP servers that need an OAuth sign-in · How to protect AI API keys

FAQ

Is Render MCP deprecated?

No. render-remote was not deprecated or archived when we last tested it on 2026-11-11.

What replaces Render MCP?

Nothing; Render MCP (official, remote) is not deprecated as of 2026-11-11.

Does Render MCP need an API key?

Not an API key: it needs an OAuth sign-in. Without signing in, the endpoint returned HTTP 401 with an OAuth challenge and did not list tools.

Embed the badge

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Copy HTML

Copy Markdown Claim this listing · Report an issue