Sites/render.com

Render

Sign in to claim

render.com

Render is a cloud platform that provides intuitive infrastructure for developers to build, deploy, and manage applications and services.

infrastructureplatform-as-a-servicecloud-hostingserverless-computingcontainerization
85
AI-Readiness / 100
Level 5 · Agent-Native
500/5313
Pages analyzed
8/15
Questions answered
Live
For AI agents
Recrawl· $5Visit site →

Content

AI-judged Q&A · 70% of score

83

8 of 15 buyer questions answered cleanly

Your site doesn't cover:

integrationpricingsecurity
See all 4 gaps →

Protocol

Technical hygiene · 30% of score

91

10 of 11 items installed

Missing:

WebMCP +3
Install with Lattis · +3 pts →

Protocol fix list

1 to ship · 10 passing

Start here

install the WebMCP widget (and host the discovery manifest)

Paste the widget script — that is the W3C WebMCP draft (navigator.modelContext) and the actual integration. Then also host the discovery manifest so crawlers can find your tool surface without rendering JS. Do both; the script is the spec, the manifest is just discoverability.

+3 pts

1. Runtime — paste in <head>

<script async src="https://lattis.dev/widget.js"></script>

Calls navigator.modelContext.provideContext() — the W3C WebMCP draft. Agents on the page see your tools live, scoped to render.com.

2. Discovery — host the manifest

Download webmcp.json

Host at render.com/.well-known/webmcp.json. The WebMCP spec defines no discovery mechanism, so crawlers can't see runtime registrations — this manifest closes that gap.

Already passing

✓ robots.txt✓ sitemap.xml✓ llms.txt✓ Allow major AI crawlers✓ Content-Signal policy✓ Clean crawl rate✓ Markdown content negotiation✓ Server-rendered content✓ MCP server card✓ OpenAPI spec

Content gaps

4 gaps

Also covered by render.com

✓ limits✓ technical✓ technical✓ limits✓ limits✓ operations✓ migration✓ technical✓ pricing✓ pricing✓ technical

MCP Server

AI agents can query this site directly via MCP. Add this endpoint to Claude Code, Cursor, or any MCP client.

Endpoint

https://mcp.lattis.dev/s/render-com/mcp

Claude Code

claude mcp add render --transport http https://mcp.lattis.dev/s/render-com/mcp

Cursor

{
  "mcpServers": {
    "render": {
      "url": "https://mcp.lattis.dev/s/render-com/mcp"
    }
  }
}

WebMCP — runtime + discovery

1. Widget script — drop in <head>. WebMCP-capable browsers (Chrome 146+ Origin Trial) call navigator.modelContext.provideContext() via this script — that's the W3C draft and the actual integration agents care about.

<script async src="https://lattis.dev/widget.js"></script>

Renders a small "AI-indexed by Lattis" badge bottom-right. Hide with [data-lattis] { display: none !important; }.

2. Discovery manifest — host alongside the script. The WebMCP spec defines no discovery mechanism, so crawlers can't see the runtime registration. This static JSON closes the gap.

Download webmcp.json

Host at render.com/.well-known/webmcp.json.