MCP.Market

Render Useful MCP server

by LuSrodri·io.github.LuSrodri/render-useful-mcp·v1.4.0
No reviews yet

MCP server for the Render Public API: all 207 endpoints plus workflow tools.

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

0 stars31 downloads/wk

Reviews

Write one

Nobody has reviewed Render Useful MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Render Useful MCP tools (5, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • render_find_service

    Resolves a service name — including a partial or approximate one — to a single Render service,

  • render_recent_logs

    Fetches recent log lines for a service, resolving the service name and workspace id for you.

  • render_service_status

    One-call triage for a service: its configuration, latest deploys, running instances and most

  • render_toolsets

    Lists every Render toolset with its tool count and whether it is currently enabled.

  • render_wait_for_deploywrite action

    Polls a deploy until it reaches a terminal state (live, build_failed, update_failed, canceled,

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings
  • Code scan46 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Render Useful MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
31
more than 19% of 12,191 servers with a package

What its tools let an agent do: 4 read · 1 change

Install Render Useful MCP in Claude Code, Cursor or VS Code

Runs npx -y render-useful-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add render-useful-mcp -- npx -y render-useful-mcp
Add to Cursor

What the publisher says

From the Render Useful MCP repository's README, as published. We do not edit it. Read it on GitHub

render-useful-mcp

A Model Context Protocol server for Render that exposes every endpoint of the official Render Public API, plus a handful of higher-level tools for the workflows the raw API makes tedious.

Written in TypeScript. Every API tool is generated from Render's own OpenAPI document, so coverage is complete by construction and stays that way.

<!-- generated:tool-counts -->

213 tools: all 208 operations of the Render Public API (spec version 1.0.0), plus 5 workflow tools for the sequences the raw API makes tedious. <!-- /generated:tool-counts -->

📖 Documentation site · tool catalogue · llms.txt

Why this one

Most API wrappers stop at a curated subset of endpoints, which drifts out of date and leaves you stuck the moment you need something the author skipped.

  • Complete, by construction. Every operation in Render's own OpenAPI document becomes a tool. Everything the API allows your key to do is reachable out of the box — no opt-in required.
  • Usable by a model. Names resolve to ids fuzzily, your workspace id is filled in automatically, deploys can be waited on in one call, and failures come back with a hint instead of a bare status code.
  • Narrowable when you want it. Every toolset is on by default; RENDERMCPTOOLSETS and RENDERMCPREAD_ONLY exist to restrict the surface deliberately, not to gate it.
  • Honest about risk. MCP destructive/read-only/idempotent annotations are derived from real HTTP semantics, so clients can make sensible auto-approval decisions — including the PUTs that replace a whole collection, where everything the caller omits is deleted. Secrets are redacted from logs.

Install

Both buttons prefill the config with a placeholder API key — replace it after install.

Claude Code — install it globally, so it is there in every project:

claude mcp add render --scope user -e RENDER_API_KEY=rnd_your_key -- npx -y render-useful-mcp

--scope user is the part that matters. Claude Code defaults to local scope, which registers the server for the current directory only — so it works where you installed it and is missing everywhere else, which is the usual reason a freshly added server seems to disappear. The three scopes are:

Confirm with claude mcp list, and re-run the command with --scope user if render is not listed from an unrelated directory.

Claude Code, as a plugin — this wires up the server and its docs in one step, and plugins are installed globally by nature:

/plugin marketplace add LuSrodri/render-useful-mcp
/plugin install render-useful-mcp@lusrodri-render

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Render Useful MCP: common questions

Is Render Useful MCP server safe?
Mostly: it is graded B (83/100). Read the Render Useful MCP safety report
How do I install Render Useful MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Render Useful MCP need an API key?
Yes. The registry entry asks for RENDER_API_KEY.
Is Render Useful MCP maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v1.4.0.
How does Render Useful MCP compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.