---
title: "Render: the 360 agent-readiness check | Agent MCP Directory"
description: "Render on Ora's agent-readiness scan, read 2026-11-09: 84 of 100, grade B, with the MCP, API and OAuth surfaces an agent can call."
canonical: https://agentmcpdirectory.com/blog/render-agent-readiness
site: "Agent MCP Directory"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# Render: the 360 agent-readiness check | Agent MCP Directory

> Render on Ora's agent-readiness scan, read 2026-11-09: 84 of 100, grade B, with the MCP, API and OAuth surfaces an agent can call.

Source: https://agentmcpdirectory.com/blog/render-agent-readiness
Site: Agent MCP Directory
Last reviewed: 2026-11-09

# Render: the 360 agent-readiness check

Render scores 84 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 3: an OpenAPI specification, a public API, OAuth. Twenty-two skills, a WebMCP tool and a specification, under a name search cannot place.

On 9 November 2026 the public site at render.com scored 84 of 100 on [Ora's](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a B, in Ora's Infrastructure category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: Render offers strong API access and a published SDK, but lacks scoped OAuth permissions, leaving agents with all-or-nothing access.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Usability | Can agents use it | 73 of 86 | 85% |
| Access | Can agents read it | 59 of 64 | 92% |
| Discovery | Can agents find and recommend it | 10 of 14 | 71% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 84 of 100 | 84% |

## What an agent can do

The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first.

In the directory, Render sign-in required, tools not seen, not counted; the connector run of 4 November 2026 is on [the entry page](https://agentmcpdirectory.com/directory/render-com/). Ora's MCP server check for the same domain reads partial; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| MCP server / manifest mcp-server | Partial | 5 of 6 | MCP server detected at https://mcp.render.com/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery mcp-well-known-discovery | Pass | 2 of 2 | MCP server discoverable via server-card.json at /.well-known/mcp/ |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | Documented REST API detected; endpoints require authentication (API key / OAuth), which is expected for agent access. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://render.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /docs |
| OpenAPI spec published openapi-spec | Pass | 7 of 7 | OpenAPI spec found at https://api-docs.render.com/openapi/render-public-api-1.json (version: 3.0.2) |
| API catalog (RFC 9727) api-catalog-rfc9727 | Partial | 1 of 2 | api-catalog linkset[0] has no 'item' entries |
| A2A / agent-card a2a-agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file agent-discovery-file | Pass | 2 of 2 | Agent Skills index (agentskills.io) found at /.well-known/agent-skills/index.json with 22 skill(s) |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OAuth authorization server metadata at https://api.render.com |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Pass | 2 of 2 | no detail published |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Pass | 5 of 5 | Imperative WebMCP API detected (navigator.modelContext.registerTool in inline script). Note: the entry point moved to document.modelContext - Chrome 150+ deprecates the navigator.modelContext alias. |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Partial | 2 of 3 | CLI tool mentioned in llms.txt |
| Multi-language SDK packages rest-sdk-packages | Partial | 2 of 3 | SDK packages found in npm, pypi |
| Rate limit response headers rate-limit-headers | Partial | 1 of 2 | REST rate-limit headers documented in OpenAPI spec, but not observed on a live response (API requires authentication). (GraphQL signal: fail 0). |
| Idempotency-Key support idempotency-key-support | Fail | 0 of 3 | No REST Idempotency-Key support detected (GraphQL signal: fail 0). |
| JSON error responses json-error-responses | Pass | 4 of 4 | no detail published |

## At the door

What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection bot-detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability agent-crawler-reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| robots.txt AI crawler policy robots-ai-policy-quality | Pass | 2 of 2 | AI search crawlers: allowed in 15 of 15 checks (3 crawlers on 5 pages). AI training crawlers: allowed in 10 of 10 checks (2 crawlers on 5 pages), not scored. |
| robots.txt agent-user policy robots-agent-user-policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://render.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (4 with substantive content) |
| Homepage not hidden from search noindex-directives | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
| Redirect hygiene redirect-hygiene | Pass | 1 of 1 | no detail published |
| Web Bot Auth directory web-bot-auth-directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |

## What an agent can read

Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript content-no-js | Partial | 2 of 3 | Homepage: 6049 chars with H1, but 1.7% content ratio is below the 5% target. 4 of 4 sampled inner pages have text without JavaScript (1 skipped). |
| Page token budget page-token-budget | Pass | 1 of 1 | All 7 measured pages fit an agent context budget (largest ~3K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://render.com/sitemap-index.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Pass | 1 of 1 | no detail published |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://render.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt at https://render.com/llms.txt is well-formatted with markdown links, but at 52,594 characters it exceeds the 30,000-character recommendation for a navigation index. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Pass | 1 of 1 | Path-suffix markdown docs served with text/markdown content-type: /agents.md, /index.md |
| Markdown URL fallback markdown-url-fallback | Partial | 1 of 2 | Partial markdown fallback support. Homepage (https://render.com/index.md) returns markdown, but 1 of 3 sampled content pages do not: https://render.com/about.md. To earn full credit, serve a .md twin for each content page (e.g. |
| Bot-UA markdown serving agent-ua-markdown | Fail | 0 of 1 | No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. |
| Agent mode view agent-mode-view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| JSON-LD structured data json-ld | Pass | 4 of 4 | Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (3 block(s)) |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: contactPoint, address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Pass | 2 of 2 | no detail published |
| Schema type breadth schema-type-breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness metadata-completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Pass | 3 of 3 | no detail published |

## Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability brand-search-accuracy | Partial | 1 of 3 | render.com ranks #8 for "Render" (searched your brand name alone: no main product term from your homepage qualified) |
| Wikipedia / Wikidata entity presence wikipedia-presence | Fail | 0 of 4 | No Wikipedia article or Wikidata entity found for "render" - creating a Wikipedia page and a Wikidata item with P856 = render.com is the highest-impact step for AI search citation coverage |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Fail | 0 of 1 | No verified entry in the official MCP Registry or on Smithery, and no npm or PyPI package of yours that runs as an MCP server. To pass, |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Pass | 2 of 2 | no detail published |
| Registry branding registry-branding | Fail | 0 of 2 | No registry branding (name, icon, description) found |
| Listed on skills.sh skills-sh-listed | Fail | 0 of 1 | No official skills self-published on skills.sh (100 community skills with potential relation to this domain found, but only self-published official skills count) |
| ARD discovery ard-catalog | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |

## Payments

The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies. None of the 6 payment checks applied to render.com.

## The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Render, with what Ora observed. The wording of each fix is Ora's; [the 28 checks it runs on an MCP server](https://agentmcpdirectory.com/mcp-checks/) are listed with their layer and tier.

-   Brand name discoverability: partial, 1 of 3, about 3.2 points to gain. Ora saw: render.com ranks #8 for "Render" (searched your brand name alone: no main product term from your homepage qualified)
-   ARD discovery: fail, 0 of 1, about 1.6 points to gain. Ora saw: No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json
-   Idempotency-Key support: fail, 0 of 3, about 1.6 points to gain. Ora saw: No REST Idempotency-Key support detected (GraphQL signal: fail 0).
-   Listed in MCP registries: fail, 0 of 1, about 1.6 points to gain. Ora saw: No verified entry in the official MCP Registry or on Smithery, and no npm or PyPI package of yours that runs as an MCP server. To pass,
-   Scoped permissions: partial, 2 of 5, about 1.6 points to gain. Ora saw: OpenAPI declares security schemes but no named OAuth scopes - agents get all-or-nothing access. Declare per-scope grants (e.g. read:\*, write:\*) in the spec.

## Our read

Render's act layer is complete in the way the top of this directory is complete. The MCP server at mcp.render.com/mcp answers and requires authentication, its server card is at /.well-known/mcp/, OAuth authorization server metadata is at api.render.com, an OpenAPI 3.0.2 specification is published at api-docs.render.com, SDKs are in npm and PyPI, an agent skills index lists 22 skills, a WebMCP tool is registered in an inline script, render.com serves an llms.txt and markdown twins at /agents.md and /index.md with the right content type. The points left are the specification's scopes, which are schemes without names, REST without an Idempotency-Key, an ARD catalog and a registry entry that are both absent, and a CLI that is mentioned rather than published. Discovery is the weak layer at 10 of 14, because render.com ranks eighth for a word that means something else and the home page is 1.7 percent text. A B at 84 that is one registry entry and a few headers from an A.

## Test your own surfaces

The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; [the reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/) are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.

```bash
npx ax@0.10 audit https://example.com --min-score 70
```

[All 360 checks](https://agentmcpdirectory.com/blog/), one company a day. Corrections to [the corrections page](https://agentmcpdirectory.com/corrections/).

Edition

4 November 2026

Method

[How rows are verified](https://agentmcpdirectory.com/method/)

Data

[CSV and JSON](https://agentmcpdirectory.com/data/)

Markdown

[This page as markdown](https://agentmcpdirectory.com/blog/render-agent-readiness/index.md)

## Sources

-   [Ora's scan of render.com, GET /api/score (vendor)](https://ora.ai/api/score/render.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 9 November 2026
-   [Ora check catalogue, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 5 November 2026
-   [render.com, the company's site](https://render.com/), read 9 November 2026

Last reviewed 9 November 2026