{
  "data": {
    "a": {
      "slug": "infros-mcp",
      "name": "InfrOS MCP Server",
      "vendor": "InfrOS",
      "vendorUrl": "https://infros.io",
      "company": "infros.io",
      "kind": "mcp",
      "category": "infrastructure",
      "summary": "The InfrOS MCP server connects AI assistants to InfrOS, a hosted service that designs cloud architectures across AWS, Google Cloud, Azure and Oracle Cloud, validates them by emulation and exports Terraform. It is a remote server behind OAuth.",
      "url": "https://www.anchorterminal.com/tools/infros-mcp",
      "markdownUrl": "https://www.anchorterminal.com/tools/infros-mcp.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/infros-mcp.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/infros-mcp.json",
      "dns": "infros-mcp.grade.anchorterminal.com",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://api.app.infros.io/assistant/mcp",
      "packages": [],
      "auth": "oauth",
      "authNotes": "OAuth through login.app.infros.io, started from the MCP client. The protected-resource metadata lists four scopes, `infros:read`, `infros:write`, `infros:spend` and `infros:admin`, with bearer tokens in the header only. Spend and admin can be granted only by organisation admins, and the assistant acts within the user's InfrOS role. Connections are revoked in Profile \u003e Connected assistants.",
      "pricing": "usage",
      "pricingNotes": "Credit-based. A free trial gives 700 credits with no card. An architecture design costs 200 to 1,200 credits (400 for a nominal one), an IaC export 100 to 400 and fixes 50 to 400. Credits last 12 months and packs can be bought at any time, but no price per credit or pack is published. Enterprise is priced on request.",
      "priceSummary": "Pay per use",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on infros.io or in the MCP setup post, read on 2026-11-18. The MCP endpoint answers an unauthenticated request with 401 and an OAuth `WWW-Authenticate` header, not a payment request.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://infros.io/blog-posts/mcp-setup-instructions",
      "llmsTxt": "https://infros.io/llms.txt",
      "capabilities": [
        "infra.terraform",
        "infra.cloud",
        "infra.aws",
        "infra.azure"
      ],
      "tags": [
        "hosted",
        "remote-mcp",
        "oauth",
        "credits",
        "free-trial",
        "no-card",
        "terraform",
        "multi-cloud",
        "israel"
      ],
      "lastRelease": "2026-11-05",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 26.8,
        "grade": "F",
        "agentReady": false,
        "rank": 1478,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 11,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 21,
          "maintenance": 35,
          "payments": 40,
          "reliability": 10,
          "schema": 15,
          "security": 49,
          "transparency": 26
        },
        "assessment": {
          "confidence": "low",
          "date": "2026-11-18"
        },
        "negative": 0,
        "warnings": [
          {
            "kind": "operator-unidentified",
            "name": "Operator not identified",
            "text": "InfrOS's terms name Cloudculate Ltd. under Israeli law and its footer says Infros, Inc., with no place of registration, registration number or address on its pages. OpenCorporates refused our reader (403) and the Israeli Corporations Authority register wasn't reachable, so no register entry was found.",
            "deduct": 0,
            "capGrade": "B",
            "since": "2026-11-18",
            "sources": [
              "https://infros.io/terms",
              "https://infros.io/privacy-policy"
            ]
          }
        ],
        "verdict": "Agents reach InfrOS through a remote MCP server with OAuth scopes that separate reading, writing, spending credits and administration, and a free trial of 700 credits needs no card. The tool list, rate limits, status, changelog and product terms aren't public, and the money price of a credit isn't published.",
        "bestFor": "Cloud architects who want an assistant to draft and compare multi-cloud designs and Terraform.",
        "strengths": [
          "OAuth with four scopes (read, write, spend, admin), header-only bearer tokens, and revocation from the InfrOS profile",
          "Spending credits and admin actions need an organisation admin's grant, and the assistant states the credit price before it spends",
          "A free trial of 700 credits with no card, and published credit costs per action",
          "Documented setup for five assistants, including Claude Code and Codex commands"
        ],
        "weaknesses": [
          "No public tool list, schemas or changelog. The endpoint requires OAuth before `initialize`",
          "No status page, rate limits, SLA, security.txt or disclosure policy found",
          "No price per credit published, so the money cost of a design run is unknown before buying",
          "The published terms and privacy policy cover only the website, and the product terms are separate and not public",
          "A person must sign up in a browser and approve OAuth before an agent can call anything"
        ],
        "agentNotes": [
          "Ask for the `infros:read` and `infros:write` scopes only, unless the person wants design runs started. `infros:spend` uses the organisation's credits",
          "Tell the person the credit price and wait for a yes before a design run or a Terraform export",
          "If the endpoint returns 401, run the client's MCP sign-in again. For Codex, run `codex mcp login infros`",
          "Show the person generated Terraform before anyone applies it to a live cloud account"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "low",
            "grade": "F",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 26.8
          }
        ],
        "editorialScores": {
          "ergonomics": 21,
          "maintenance": 35,
          "payments": 40,
          "reliability": 10,
          "schema": 15,
          "security": 49,
          "transparency": 10
        },
        "provenanceScore": 41,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "lastMoved": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "claudeCode": "claude mcp add --transport http infros https://api.app.infros.io/assistant/mcp",
        "config": {
          "mcpServers": {
            "infros": {
              "url": "https://api.app.infros.io/assistant/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/infra.terraform",
        "tool": "https://letme.dev/infros-mcp"
      },
      "area": "developer",
      "provenance": {
        "legalEntity": "Cloudculate Ltd.",
        "domain": "infros.io",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "",
        "privacy": "",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The website terms and privacy policy (both last updated 5 November 2025) name Cloudculate Ltd. and Israeli law. The site footer reads Infros, Inc. No registration number or address was found on the pages read.",
          "The website terms forbid using the site through bots, crawlers or software that imitates a user (section 4.1.1). A handful of pages were read at a person's pace under the founder's rule of 9 October 2026.",
          "infros.io/robots.txt allows ClaudeBot. api.app.infros.io answers robots.txt with 404, so it publishes no rules. infros.io/llms.txt is crawler guidance, not documentation.",
          "/.well-known/security.txt on infros.io answers 404. No status page or changelog was found."
        ],
        "score": 41
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/infros-mcp.json",
      "live": {
        "slug": "infros-mcp",
        "probe": {
          "target": "https://api.app.infros.io/assistant/mcp",
          "method": "mcp-initialize",
          "lastAt": "2026-11-18T23:01:35.740519681Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 328,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 375,
          "p95ms24h": 731,
          "samples24h": 14,
          "samples30d": 14,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 14,
              "ok": 14
            }
          ],
          "since": "2026-11-18T21:38:05.929270084Z"
        },
        "updatedAt": "2026-11-18T23:01:35.740519681Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "answer": "Render MCP Server scores 69.4 (B) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category.",
    "b": {
      "slug": "render-mcp-server",
      "name": "Render MCP Server",
      "vendor": "Render Services, Inc.",
      "vendorUrl": "https://render.com",
      "company": "render.com",
      "kind": "mcp",
      "category": "infrastructure",
      "summary": "Render's official MCP server lets an agent create services and data stores on the Render cloud platform, trigger deploys, read logs and metrics, and run read-only SQL on Render Postgres. It is hosted at mcp.render.com.",
      "url": "https://www.anchorterminal.com/tools/render-mcp-server",
      "markdownUrl": "https://www.anchorterminal.com/tools/render-mcp-server.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/render-mcp-server.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/render-mcp-server.json",
      "dns": "render-mcp-server.grade.anchorterminal.com",
      "repo": "https://github.com/render-oss/render-mcp-server",
      "license": "Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service",
      "transports": [
        "streamable-http",
        "stdio"
      ],
      "remoteUrl": "https://mcp.render.com/mcp",
      "packages": [
        {
          "registry": "oci",
          "name": "ghcr.io/render-oss/render-mcp-server"
        }
      ],
      "auth": "mixed",
      "authNotes": "OAuth or a Render API key. The hosted server answers 401 with a pointer to its protected-resource metadata, which names the authorisation server at api.render.com and no scopes, and the server rejects revoked tokens through introspection. Render documents OAuth for Claude Code, Claude Desktop, Codex and Cursor. Other clients send an API key as `Authorization: Bearer`. A person creates the key in the dashboard, it does not expire, it can be revoked, and it reaches every workspace its owner belongs to.",
      "pricing": "byo-plan",
      "pricingNotes": "The server itself is free. Tools act on a Render workspace and bill under its plan. Hobby is $0 a month plus compute, Pro $25 and Scale $499, with Enterprise priced by sales. Compute runs from a free 512 MB instance to $7 a month and up, prorated to the second. The free-tier docs describe workspaces with no payment method, whose free services are suspended when the 750 monthly free instance hours run out. Free Postgres databases expire 30 days after creation (checked 2026-10-08).",
      "priceSummary": "Your plan",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the MCP server docs, the repository README, llms.txt or the pricing page (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": 26,
      "popularity": {
        "githubStars": 176,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://render.com/docs/mcp-server",
      "llmsTxt": "https://render.com/llms.txt",
      "openapi": "https://api-docs.render.com/openapi/render-public-api-1.json",
      "capabilities": [
        "infra.cloud",
        "code.deploy",
        "observability.logs",
        "observability.metrics",
        "db.sql"
      ],
      "tags": [
        "official",
        "hosted",
        "open-source",
        "mcp",
        "oauth",
        "api-key",
        "llms-txt",
        "openapi",
        "status-page",
        "soc2",
        "free-tier"
      ],
      "lastRelease": "2026-01-14",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 69.4,
        "grade": "B",
        "agentReady": false,
        "rank": 339,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 5,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 69,
          "maintenance": 56,
          "payments": 60,
          "reliability": 78,
          "schema": 78,
          "security": 58,
          "transparency": 84
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-02"
        },
        "negative": 0,
        "verdict": "A hosted server with 26 typed and annotated tools, OAuth or API key access and Apache-2.0 source. It cannot delete resources and wraps SQL in a read-only transaction. There are no scopes and no read-only mode, a key reaches every workspace its owner belongs to, and the last tagged release is from January 2026.",
        "bestFor": "Agents that deploy and debug applications on Render, reading logs and metrics and querying Postgres.",
        "strengths": [
          "All 26 tools declare typed inputs and carry read-only, destructive and open-world annotations in the Apache-2.0 source.",
          "The server has no delete tools, and `query_render_postgres` runs each query inside a read-only transaction.",
          "OAuth sign-in since 22 July 2026 for Claude Code, Codex and Cursor, with revoked tokens rejected through introspection, and API keys kept for CI and other non-interactive use.",
          "The Hobby workspace costs $0 a month with free instances, and the free-tier docs describe use without a payment method.",
          "Render holds SOC 2 Type 2 and ISO 27001, publishes a valid security.txt and takes reports through HackerOne."
        ],
        "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.",
          "Render's status page has no MCP component. Eight build and deploy incidents from 20 August to 21 October 2026 affected what the deploy tools start.",
          "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 on 2 November, and six of 14 open issues had no reply on 8 October."
        ],
        "agentNotes": [
          "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."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 3,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 69.4
          }
        ],
        "editorialScores": {
          "ergonomics": 69,
          "maintenance": 56,
          "payments": 60,
          "reliability": 78,
          "schema": 78,
          "security": 58,
          "transparency": 71
        },
        "provenanceScore": 97,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-02",
            "maintenance": "2026-11-02",
            "payments": "2026-11-02",
            "reliability": "2026-11-02",
            "schema": "2026-11-02",
            "security": "2026-11-02",
            "transparency": "2026-11-02"
          },
          "last": "2026-11-02",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-02",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "claudeCode": "claude mcp add --transport http render https://mcp.render.com/mcp --header \"Authorization: Bearer \u003cYOUR_API_KEY\u003e\"",
        "config": {
          "mcpServers": {
            "render": {
              "headers": {
                "Authorization": "Bearer \u003cYOUR_API_KEY\u003e"
              },
              "url": "https://mcp.render.com/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/infra.cloud",
        "tool": "https://letme.dev/render-mcp-server"
      },
      "sameCompany": [
        "render-sandboxes"
      ],
      "area": "developer",
      "unitPrices": [
        {
          "item": "Hobby workspace",
          "unit": "month",
          "usd": 0,
          "note": "plus compute"
        },
        {
          "item": "Pro workspace",
          "unit": "month",
          "usd": 25,
          "note": "plus compute"
        },
        {
          "item": "Scale workspace",
          "unit": "month",
          "usd": 499,
          "note": "plus compute"
        },
        {
          "item": "Web service, 0.5 CPU and 512 MB",
          "unit": "month",
          "usd": 7,
          "note": "prorated to the second"
        },
        {
          "item": "Web service, 1 CPU and 2 GB",
          "unit": "month",
          "usd": 25,
          "note": "prorated to the second"
        },
        {
          "item": "Postgres, 0.1 CPU and 256 MB",
          "unit": "month",
          "usd": 6
        },
        {
          "item": "Key Value, 256 MB",
          "unit": "month",
          "usd": 10
        }
      ],
      "provenance": {
        "legalEntity": "Render Services, Inc.",
        "domain": "render.com",
        "domainRegistered": "1998-10-01",
        "endpointOnVendorDomain": true,
        "terms": "https://render.com/terms",
        "privacy": "https://render.com/privacy",
        "statusPage": "https://status.render.com",
        "changelog": "https://render.com/changelog",
        "securityTxt": "valid",
        "checked": "2026-10-08",
        "notes": [
          "The Terms of Service (last modified 10 July 2026) name Render Services, Inc., 525 Brannan Street Ste 300, San Francisco, CA 94107, and cover the platform and its APIs, incorporating the Acceptable Use Policy, the Data Processing Addendum and the Privacy Policy.",
          "The Privacy Policy is also dated 10 July 2026. Customer personal data processed on the platform is governed by the DPA at render.com/dpa.",
          "The MCP server answers at mcp.render.com and its OAuth server at api.render.com, both render.com subdomains.",
          "render.com/.well-known/security.txt names security@render.com and the HackerOne programme and expires on 3 October 2027.",
          "RDAP for render.com gives a registration date of 1998-10-01.",
          "The Markdown twins of the terms and privacy pages hold only a title, so both documents were read from the HTML pages."
        ],
        "score": 97
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/render-mcp-server.json",
      "live": {
        "slug": "render-mcp-server",
        "probe": {
          "target": "https://mcp.render.com/mcp",
          "method": "mcp-initialize",
          "lastAt": "2026-11-18T23:01:50.807132932Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 174,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 99.99,
          "p50ms24h": 197,
          "p95ms24h": 420,
          "samples24h": 241,
          "samples30d": 7840,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-29",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 244
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 231,
              "ok": 231
            }
          ],
          "since": "2026-10-09T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.render.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T23:01:15.588041294Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "render-oss/render-mcp-server",
            "version": "v0.3.0",
            "released": "2026-01-14",
            "seenAt": "2026-11-18T18:23:42.255148016Z"
          }
        ],
        "githubStars": 203,
        "securityTxt": {
          "url": "https://render.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-10-03T00:00:00.000Z",
          "checkedAt": "2026-11-18T16:30:28.896502171Z"
        },
        "llmsTxt": {
          "url": "https://render.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:15:53.262722303Z"
        },
        "domain": {
          "domain": "render.com",
          "registered": "1998-10-01",
          "source": "https://rdap.verisign.com/com/v1/domain/render.com",
          "checkedAt": "2026-11-15T15:17:18.779152766Z"
        },
        "pages": [
          {
            "url": "https://render.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-18T21:52:25.744753789Z",
            "changedAt": "2026-11-18T21:52:25.744753789Z",
            "fingerprint": "02f05ea91c53"
          },
          {
            "url": "https://render.com/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:52:28.335328887Z",
            "changedAt": "2026-11-16T20:31:42.858805343Z",
            "fingerprint": "928d9f855e8e"
          },
          {
            "url": "https://render.com/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:52:30.118954902Z",
            "changedAt": "2026-11-16T20:31:46.243256358Z",
            "fingerprint": "304205c74e3f"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.render.com/mcp",
          "checkedAt": "2026-11-18T04:27:41.760554768Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-10-09T21:40:54.635433453Z"
        },
        "github": {
          "repo": "render-oss/render-mcp-server",
          "checkedAt": "2026-11-16T12:53:56.177332321Z",
          "stars": 202,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-13T23:32:49Z",
          "openIssues": 14,
          "openPRs": 0,
          "issuesOpened90d": 6,
          "issuesClosed90d": 2,
          "prsMerged90d": 0,
          "ci": {
            "branch": "main",
            "runs": 50,
            "success": 49,
            "failure": 1,
            "other": 0,
            "latest": "success",
            "latestAt": "2026-11-13T23:34:19Z"
          },
          "replies": {
            "sampled": 19,
            "unanswered": 13,
            "medianDays": 20.4
          }
        },
        "updatedAt": "2026-11-18T23:01:50.807132932Z"
      },
      "streak": {
        "days": 40,
        "from": "2026-10-09",
        "sinceWatching": true,
        "best": 40
      }
    },
    "edges": [
      {
        "by": 68,
        "category": "reliability",
        "leads": "render-mcp-server",
        "name": "Reliability",
        "reasons": {
          "a": "Graded as a hosted MCP server. No status page found (0). No history to read (5). No rate limits published (0). No 429, retry or backoff guidance (0). No SLA, and Enterprise lists dedicated support without a figure (0). InfrOS's own pages don't call the server beta, but the press article on its news page calls it a preview, so half (5). 0 + 5 + 0 + 0 + 0 + 5 = 10.",
          "b": "Scored as a hosted server. status.render.com is a Statuspage with component history, though the MCP server has no component of its own (20). From 4 August to 2 November 2026 its history feed lists 14 incidents and three maintenance notices. None names the MCP server or the REST API it calls. Eight touch builds and deploys, which the server's create and deploy tools start, among them deploys in every region on 20 August (an upstream Google Cloud issue, about four hours), Singapore on 31 August and builds not starting in any region for nearly three hours on 14 October. Each hit one function or one region, so all read as minor. The dashboard, email, network and Key Value incidents don't touch the server, and the REST API's two maintenance windows were announced ahead (20 of 30). The 8 October count came from a status data path robots.txt disallows and is struck. 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 server has been generally available since 21 August 2025 per Render's changelog, though the source is versioned 0.x (8 of 10). 20 + 20 + 15 + 10 + 5 + 8 = 78."
        },
        "scores": {
          "a": 10,
          "b": 78
        }
      },
      {
        "by": 63,
        "category": "schema",
        "leads": "render-mcp-server",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "No tool list or schema is published, and the endpoint needs OAuth before `initialize`. An OAuth protected-resource document states the scopes and bearer method (5 of 25). llms.txt exists but holds crawler rules and brand notes, not docs (2). The setup post describes four permission groups and what each allows, not individual tools (5). Inputs unknown (0). One example prompt and no documented errors (3). No versioning or changelog found (0). 5 + 2 + 5 + 0 + 3 + 0 = 15.",
          "b": "Every tool declares typed inputs through mcp-go, and since 12 October the server rejects an out-of-range `list_logs` limit, an invalid direction and an invalid cron schedule before calling the API, closing the two issues of 22 September 2026 (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). 25 + 10 + 15 + 11 + 8 + 9 = 78."
        },
        "scores": {
          "a": 15,
          "b": 78
        }
      },
      {
        "by": 58,
        "category": "transparency",
        "leads": "render-mcp-server",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed service. The published terms cover only the website, and the product is under separate agreements that aren't public (5). The privacy policy covers website forms only, with no product data, retention or DPA found (5). No deprecation policy (0). No subprocessors or data locations disclosed (0). 5 + 5 + 0 + 0 = 10.",
          "b": "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)."
        },
        "scores": {
          "a": 26,
          "b": 84
        }
      },
      {
        "by": 48,
        "category": "ergonomics",
        "leads": "render-mcp-server",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "Tool count and sizes couldn't be read. Scope-based access may narrow what a session can do, so partial credit (8). No pagination or output controls documented (0). Errors undocumented beyond the 401 with a `WWW-Authenticate` header (2). The setup post says the assistant states the credit price and waits for a yes, but no annotations or idempotency are documented (6). One URL and an OAuth sign-in, with no SDK (5). 8 + 0 + 2 + 6 + 5 = 21.",
          "b": "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)."
        },
        "scores": {
          "a": 21,
          "b": 69
        }
      },
      {
        "by": 21,
        "category": "maintenance",
        "leads": "render-mcp-server",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Read as a closed hosted service. The MCP server was announced on 5 November 2026, 13 days before the check (30). No changelog. The news page lists dated launches on 30 September and 9 November 2026, two in 90 days (0). Support by email and a Slack chat link, with no public changelog (5). Not in the official MCP registry, by a search for infros (0). No SDK (0). 30 + 0 + 5 + 0 + 0 = 35.",
          "b": "The main branch had commits changing tools on 12 and 22 October 2026 (input validation, a 5 MB cap on `query_render_postgres` results, UTC timestamps in `list_events`) and dependency commits to 1 November, and Render says the hosted server updates as tools are added. The last tag is still v0.3.0 of 14 January 2026, so 25 of 30. No tagged release in 90 days, and Render's two MCP changelog entries (17 and 22 July 2026) are now outside the window, while the source added Dockerfile-based creation and `list_events` in September and the October changes above (15 of 20). Five Blueprint tools were added to the source from 26 to 30 October, and a test keeps them unregistered. 14 open issues, six with no reply, per the 8 October check, not re-read on 2 November (8 of 25). No entry in the official MCP registry in three searches on 2 November (0). Go 1.27.3, mcp-go 1.4.0, pinned dependencies with Renovate and a test workflow. The workflow's result was not seen (8 of 10). 25 + 15 + 8 + 0 + 8 = 56."
        },
        "scores": {
          "a": 35,
          "b": 56
        }
      },
      {
        "by": 20,
        "category": "payments",
        "leads": "render-mcp-server",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No payment protocol (0). Credit costs per action are public, but no price per credit or pack is, so the money price is hidden, as for Datadog's plan-only case (10). A free trial of 700 credits with no card (30). A person signs up in a browser and approves OAuth (0). 0 + 10 + 30 + 0 = 40.",
          "b": "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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60."
        },
        "scores": {
          "a": 40,
          "b": 60
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "InfrOS",
        "b": "Render Services, Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://api.app.infros.io/assistant/mcp",
        "b": "https://mcp.render.com/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "Streamable HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "OAuth",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Your plan",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "none",
        "b": "Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "26",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-11-05",
        "b": "2026-01-14",
        "name": "Last release"
      },
      {
        "a": "no document linked",
        "b": "2026-07-10",
        "name": "Terms last updated"
      },
      {
        "a": "no document linked",
        "b": "2026-07-10",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not read yet",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not read yet",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "176 stars",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3/5 (4)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Render MCP Server scores 69.4 (B) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category.",
        "question": "Which is better for AI agents, InfrOS MCP Server or Render MCP Server?"
      },
      {
        "answer": "InfrOS MCP Server uses an OAuth sign-in. Render MCP Server takes an API key or an OAuth sign-in.",
        "question": "Do InfrOS MCP Server and Render MCP Server need an API key?"
      },
      {
        "answer": "Yes. InfrOS MCP Server has a hosted endpoint at https://api.app.infros.io/assistant/mcp and Render MCP Server at https://mcp.render.com/mcp.",
        "question": "Can an agent call InfrOS MCP Server and Render MCP Server without installing anything?"
      },
      {
        "answer": "No open-source release is listed for InfrOS MCP Server. Render MCP Server is open source (Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service).",
        "question": "Are InfrOS MCP Server and Render MCP Server open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": null,
        "also": [
          "Free to start without a card"
        ],
        "goodFor": "Cloud architects who want an assistant to draft and compare multi-cloud designs and Terraform.",
        "slug": "infros-mcp",
        "watchFor": "No public tool list, schemas or changelog. The endpoint requires OAuth before `initialize`"
      },
      {
        "aheadOn": [
          "Reliability, 78 against 10",
          "Schema \u0026 documentation, 78 against 15",
          "Agent ergonomics, 69 against 21",
          "Security \u0026 auth, 58 against 49",
          "Payments \u0026 pricing, 60 against 40",
          "Maintenance \u0026 community, 56 against 35",
          "Transparency \u0026 trust, 84 against 26"
        ],
        "also": [
          "Runs on your own machine",
          "Open source"
        ],
        "goodFor": "Agents that deploy and debug applications on Render, reading logs and metrics and querying Postgres.",
        "slug": "render-mcp-server",
        "watchFor": "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."
      }
    ],
    "history": {
      "infros-mcp": [
        {
          "causes": [
            "correction"
          ],
          "date": "2026-11-18",
          "delta": -0.6,
          "from": 27.4,
          "fromGrade": "F",
          "to": 26.8,
          "toGrade": "F"
        }
      ],
      "render-mcp-server": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 66.9,
          "fromGrade": "B",
          "to": 69.4,
          "toGrade": "B"
        },
        {
          "causes": [
            "product",
            "correction"
          ],
          "date": "2026-11-02",
          "delta": 3.3,
          "from": 63.6,
          "fromGrade": "B",
          "to": 66.9,
          "toGrade": "B"
        }
      ]
    },
    "job": {
      "capability": "infra.cloud",
      "name": "Cloud hosting"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/azure-mcp-vs-render-mcp-server.json",
        "title": "Azure MCP Server vs Render MCP Server",
        "url": "https://www.anchorterminal.com/compare/azure-mcp-vs-render-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-mcp-vs-infros-mcp.json",
        "title": "DigitalOcean MCP Server vs InfrOS MCP Server",
        "url": "https://www.anchorterminal.com/compare/digitalocean-mcp-vs-infros-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-mcp-vs-render-mcp-server.json",
        "title": "DigitalOcean MCP Server vs Render MCP Server",
        "url": "https://www.anchorterminal.com/compare/digitalocean-mcp-vs-render-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/infros-mcp-vs-netlify.json",
        "title": "InfrOS MCP Server vs Netlify API + MCP",
        "url": "https://www.anchorterminal.com/compare/infros-mcp-vs-netlify"
      },
      {
        "json": "https://www.anchorterminal.com/compare/infros-mcp-vs-railway-mcp-server.json",
        "title": "InfrOS MCP Server vs Railway MCP Server",
        "url": "https://www.anchorterminal.com/compare/infros-mcp-vs-railway-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server.json",
        "title": "neckbeard vs Render MCP Server",
        "url": "https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server.json",
        "title": "Netlify API + MCP vs Render MCP Server",
        "url": "https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/railway-mcp-server-vs-render-mcp-server.json",
        "title": "Railway MCP Server vs Render MCP Server",
        "url": "https://www.anchorterminal.com/compare/railway-mcp-server-vs-render-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/render-mcp-server-vs-terraform-mcp.json",
        "title": "Render MCP Server vs Terraform MCP Server",
        "url": "https://www.anchorterminal.com/compare/render-mcp-server-vs-terraform-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-cli-vs-render-mcp-server.json",
        "title": "Cloudflare CLI (cf) vs Render MCP Server",
        "url": "https://www.anchorterminal.com/compare/cloudflare-cli-vs-render-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/infros-mcp-vs-neckbeard.json",
        "title": "InfrOS MCP Server vs neckbeard",
        "url": "https://www.anchorterminal.com/compare/infros-mcp-vs-neckbeard"
      },
      {
        "json": "https://www.anchorterminal.com/compare/infros-mcp-vs-terraform-mcp.json",
        "title": "InfrOS MCP Server vs Terraform MCP Server",
        "url": "https://www.anchorterminal.com/compare/infros-mcp-vs-terraform-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/aws-mcp-servers-vs-infros-mcp.json",
        "title": "AWS MCP Servers vs InfrOS MCP Server",
        "url": "https://www.anchorterminal.com/compare/aws-mcp-servers-vs-infros-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/azure-mcp-vs-infros-mcp.json",
        "title": "Azure MCP Server vs InfrOS MCP Server",
        "url": "https://www.anchorterminal.com/compare/azure-mcp-vs-infros-mcp"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 68,
        "edge": "render-mcp-server",
        "infros-mcp": 10,
        "key": "reliability",
        "name": "Reliability",
        "render-mcp-server": 78,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 63,
        "edge": "render-mcp-server",
        "infros-mcp": 15,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "render-mcp-server": 78,
        "weight": 13
      },
      {
        "by": 48,
        "edge": "render-mcp-server",
        "infros-mcp": 21,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "render-mcp-server": 69,
        "weight": 13
      },
      {
        "by": 9,
        "edge": "render-mcp-server",
        "infros-mcp": 49,
        "key": "security",
        "name": "Security \u0026 auth",
        "render-mcp-server": 58,
        "weight": 14
      },
      {
        "by": 20,
        "edge": "render-mcp-server",
        "infros-mcp": 40,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "render-mcp-server": 60,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 21,
        "edge": "render-mcp-server",
        "infros-mcp": 35,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "render-mcp-server": 56,
        "weight": 7
      },
      {
        "by": 58,
        "edge": "render-mcp-server",
        "infros-mcp": 26,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "render-mcp-server": 84,
        "weight": 7
      }
    ],
    "summary": "Render MCP Server scores 69.4 (B) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category. Both do cloud hosting.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "infros-mcp": "Agents reach InfrOS through a remote MCP server with OAuth scopes that separate reading, writing, spending credits and administration, and a free trial of 700 credits needs no card. The tool list, rate limits, status, changelog and product terms aren't public, and the money price of a credit isn't published.",
      "render-mcp-server": "A hosted server with 26 typed and annotated tools, OAuth or API key access and Apache-2.0 source. It cannot delete resources and wraps SQL in a read-only transaction. There are no scopes and no read-only mode, a key reaches every workspace its owner belongs to, and the last tagged release is from January 2026."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/infros-mcp-vs-render-mcp-server",
    "json": "https://www.anchorterminal.com/compare/infros-mcp-vs-render-mcp-server.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/infros-mcp-vs-render-mcp-server.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/infros-mcp-vs-render-mcp-server.min.md"
  },
  "markdown": "Render MCP Server scores 69.4 (B) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category. Both do cloud hosting.\n\n- InfrOS MCP Server: grade F, 26.8/100, rank #1478 of 1557. Markdown https://www.anchorterminal.com/tools/infros-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/infros-mcp.json\n- Render MCP Server: grade B, 69.4/100, rank #339 of 1557. Markdown https://www.anchorterminal.com/tools/render-mcp-server.md · JSON https://www.anchorterminal.com/api/v1/tools/render-mcp-server.json\n- Best cloud infrastructure tools for AI agents: https://www.anchorterminal.com/best/infrastructure/index.md\n- All 39 infra comparisons: https://www.anchorterminal.com/compare/infrastructure/index.md\n\n## Which one, for what\n\n### InfrOS MCP Server (F)\n\nGood for: Cloud architects who want an assistant to draft and compare multi-cloud designs and Terraform.\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No public tool list, schemas or changelog. The endpoint requires OAuth before `initialize`\n\n### Render MCP Server (B)\n\nGood for: Agents that deploy and debug applications on Render, reading logs and metrics and querying Postgres.\n\nAhead on:\n- Reliability, 78 against 10\n- Schema \u0026 documentation, 78 against 15\n- Agent ergonomics, 69 against 21\n- Security \u0026 auth, 58 against 49\n- Payments \u0026 pricing, 60 against 40\n- Maintenance \u0026 community, 56 against 35\n- Transparency \u0026 trust, 84 against 26\n\nAlso in its favour:\n- Runs on your own machine\n- Open source\n\nWatch for: 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.\n\n\n## Why the edge\n\n### Reliability: Render MCP Server +68\n\n- InfrOS MCP Server (10): Graded as a hosted MCP server. No status page found (0). No history to read (5). No rate limits published (0). No 429, retry or backoff guidance (0). No SLA, and Enterprise lists dedicated support without a figure (0). InfrOS's own pages don't call the server beta, but the press article on its news page calls it a preview, so half (5). 0 + 5 + 0 + 0 + 0 + 5 = 10.\n- Render MCP Server (78): Scored as a hosted server. status.render.com is a Statuspage with component history, though the MCP server has no component of its own (20). From 4 August to 2 November 2026 its history feed lists 14 incidents and three maintenance notices. None names the MCP server or the REST API it calls. Eight touch builds and deploys, which the server's create and deploy tools start, among them deploys in every region on 20 August (an upstream Google Cloud issue, about four hours), Singapore on 31 August and builds not starting in any region for nearly three hours on 14 October. Each hit one function or one region, so all read as minor. The dashboard, email, network and Key Value incidents don't touch the server, and the REST API's two maintenance windows were announced ahead (20 of 30). The 8 October count came from a status data path robots.txt disallows and is struck. 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 server has been generally available since 21 August 2025 per Render's changelog, though the source is versioned 0.x (8 of 10). 20 + 20 + 15 + 10 + 5 + 8 = 78.\n\n### Schema \u0026 documentation: Render MCP Server +63\n\n- InfrOS MCP Server (15): No tool list or schema is published, and the endpoint needs OAuth before `initialize`. An OAuth protected-resource document states the scopes and bearer method (5 of 25). llms.txt exists but holds crawler rules and brand notes, not docs (2). The setup post describes four permission groups and what each allows, not individual tools (5). Inputs unknown (0). One example prompt and no documented errors (3). No versioning or changelog found (0). 5 + 2 + 5 + 0 + 3 + 0 = 15.\n- Render MCP Server (78): Every tool declares typed inputs through mcp-go, and since 12 October the server rejects an out-of-range `list_logs` limit, an invalid direction and an invalid cron schedule before calling the API, closing the two issues of 22 September 2026 (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). 25 + 10 + 15 + 11 + 8 + 9 = 78.\n\n### Transparency \u0026 trust: Render MCP Server +58\n\n- InfrOS MCP Server (26): Closed service. The published terms cover only the website, and the product is under separate agreements that aren't public (5). The privacy policy covers website forms only, with no product data, retention or DPA found (5). No deprecation policy (0). No subprocessors or data locations disclosed (0). 5 + 5 + 0 + 0 = 10.\n- Render MCP Server (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).\n\n### Agent ergonomics: Render MCP Server +48\n\n- InfrOS MCP Server (21): Tool count and sizes couldn't be read. Scope-based access may narrow what a session can do, so partial credit (8). No pagination or output controls documented (0). Errors undocumented beyond the 401 with a `WWW-Authenticate` header (2). The setup post says the assistant states the credit price and waits for a yes, but no annotations or idempotency are documented (6). One URL and an OAuth sign-in, with no SDK (5). 8 + 0 + 2 + 6 + 5 = 21.\n- Render MCP Server (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).\n\n### Maintenance \u0026 community: Render MCP Server +21\n\n- InfrOS MCP Server (35): Read as a closed hosted service. The MCP server was announced on 5 November 2026, 13 days before the check (30). No changelog. The news page lists dated launches on 30 September and 9 November 2026, two in 90 days (0). Support by email and a Slack chat link, with no public changelog (5). Not in the official MCP registry, by a search for infros (0). No SDK (0). 30 + 0 + 5 + 0 + 0 = 35.\n- Render MCP Server (56): The main branch had commits changing tools on 12 and 22 October 2026 (input validation, a 5 MB cap on `query_render_postgres` results, UTC timestamps in `list_events`) and dependency commits to 1 November, and Render says the hosted server updates as tools are added. The last tag is still v0.3.0 of 14 January 2026, so 25 of 30. No tagged release in 90 days, and Render's two MCP changelog entries (17 and 22 July 2026) are now outside the window, while the source added Dockerfile-based creation and `list_events` in September and the October changes above (15 of 20). Five Blueprint tools were added to the source from 26 to 30 October, and a test keeps them unregistered. 14 open issues, six with no reply, per the 8 October check, not re-read on 2 November (8 of 25). No entry in the official MCP registry in three searches on 2 November (0). Go 1.27.3, mcp-go 1.4.0, pinned dependencies with Renovate and a test workflow. The workflow's result was not seen (8 of 10). 25 + 15 + 8 + 0 + 8 = 56.\n\n### Payments \u0026 pricing: Render MCP Server +20\n\n- InfrOS MCP Server (40): No payment protocol (0). Credit costs per action are public, but no price per credit or pack is, so the money price is hidden, as for Datadog's plan-only case (10). A free trial of 700 credits with no card (30). A person signs up in a browser and approves OAuth (0). 0 + 10 + 30 + 0 = 40.\n- Render MCP Server (60): 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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.\n\n## Score by category\n\n| Category | Weight | InfrOS MCP Server | Render MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 10 | 78 | Render MCP Server +68 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 15 | 78 | Render MCP Server +63 |\n| Agent ergonomics | 13% | 21 | 69 | Render MCP Server +48 |\n| Security \u0026 auth | 14% | 49 | 58 | Render MCP Server +9 |\n| Payments \u0026 pricing | 10% | 40 | 60 | Render MCP Server +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 35 | 56 | Render MCP Server +21 |\n| Transparency \u0026 trust | 7% | 26 | 84 | Render MCP Server +58 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **26.8 · F** | **69.4 · B** | |\n\n## Facts side by side\n\n| Fact | InfrOS MCP Server | Render MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | InfrOS | Render Services, Inc. |\n| Hosted endpoint | `https://api.app.infros.io/assistant/mcp` | `https://mcp.render.com/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP, stdio |\n| Auth | OAuth | OAuth or key |\n| Pricing | Pay per use | Your plan |\n| x402 | no | no |\n| Licence | none | Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service |\n| Tools exposed | none | 26 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-11-05 | 2026-01-14 |\n| Terms last updated | no document linked | 2026-07-10 |\n| Privacy policy last updated | no document linked | 2026-07-10 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | yes |\n| Arbitration or class-action waiver | not read yet | yes |\n| Popularity | none | 176 stars |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### InfrOS MCP Server\n\n- -0.6 on 18 November 2026: correction\n\n### Render MCP Server\n\n- +2.5 on 13 November 2026: checklist\n- +3.3 on 2 November 2026: product, correction\n\n## Verdicts\n\n**InfrOS MCP Server.** Agents reach InfrOS through a remote MCP server with OAuth scopes that separate reading, writing, spending credits and administration, and a free trial of 700 credits needs no card. The tool list, rate limits, status, changelog and product terms aren't public, and the money price of a credit isn't published.\n\n**Render MCP Server.** A hosted server with 26 typed and annotated tools, OAuth or API key access and Apache-2.0 source. It cannot delete resources and wraps SQL in a read-only transaction. There are no scopes and no read-only mode, a key reaches every workspace its owner belongs to, and the last tagged release is from January 2026.\n\n## Before you call either\n\n### InfrOS MCP Server\n\n1. Ask for the `infros:read` and `infros:write` scopes only, unless the person wants design runs started. `infros:spend` uses the organisation's credits\n2. Tell the person the credit price and wait for a yes before a design run or a Terraform export\n3. If the endpoint returns 401, run the client's MCP sign-in again. For Codex, run `codex mcp login infros`\n4. Show the person generated Terraform before anyone applies it to a live cloud account\n\n### Render MCP Server\n\n1. Pass `workspaceId` on every resource tool call. Session-based workspace selection through `select_workspace` is deprecated and scheduled for removal.\n2. Do not call `trigger_deploy` after pushing to a service with autoDeploy on. The push already starts a deploy.\n3. Use an API key in the `Authorization` header for CI. OAuth grants expire and need a person to approve the browser flow again.\n4. `update_environment_variables` merges by default. Set `replace` to true only to overwrite the whole set.\n5. Expect 429 from the Render API at 20 service creations an hour and 10 deploys a minute per service. Back off with jitter.\n\n## Questions\n\n### Which is better for AI agents, InfrOS MCP Server or Render MCP Server?\n\nRender MCP Server scores 69.4 (B) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category.\n\n### Do InfrOS MCP Server and Render MCP Server need an API key?\n\nInfrOS MCP Server uses an OAuth sign-in. Render MCP Server takes an API key or an OAuth sign-in.\n\n### Can an agent call InfrOS MCP Server and Render MCP Server without installing anything?\n\nYes. InfrOS MCP Server has a hosted endpoint at https://api.app.infros.io/assistant/mcp and Render MCP Server at https://mcp.render.com/mcp.\n\n### Are InfrOS MCP Server and Render MCP Server open source?\n\nNo open-source release is listed for InfrOS MCP Server. Render MCP Server is open source (Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/infros-mcp-vs-render-mcp-server.json, and with the fewest tokens: https://www.anchorterminal.com/compare/infros-mcp-vs-render-mcp-server.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"infros-mcp\", \"b\": \"render-mcp-server\"}`. From a terminal: `anchor compare infros-mcp render-mcp-server`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/infros-mcp.json and https://www.anchorterminal.com/api/v1/tools/render-mcp-server.json\n\n## Other comparisons with InfrOS MCP Server or Render MCP Server\n\n- [Azure MCP Server vs Render MCP Server](https://www.anchorterminal.com/compare/azure-mcp-vs-render-mcp-server.md)\n- [DigitalOcean MCP Server vs InfrOS MCP Server](https://www.anchorterminal.com/compare/digitalocean-mcp-vs-infros-mcp.md)\n- [DigitalOcean MCP Server vs Render MCP Server](https://www.anchorterminal.com/compare/digitalocean-mcp-vs-render-mcp-server.md)\n- [InfrOS MCP Server vs Netlify API + MCP](https://www.anchorterminal.com/compare/infros-mcp-vs-netlify.md)\n- [InfrOS MCP Server vs Railway MCP Server](https://www.anchorterminal.com/compare/infros-mcp-vs-railway-mcp-server.md)\n- [neckbeard vs Render MCP Server](https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server.md)\n- [Netlify API + MCP vs Render MCP Server](https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server.md)\n- [Railway MCP Server vs Render MCP Server](https://www.anchorterminal.com/compare/railway-mcp-server-vs-render-mcp-server.md)\n- [Render MCP Server vs Terraform MCP Server](https://www.anchorterminal.com/compare/render-mcp-server-vs-terraform-mcp.md)\n- [Cloudflare CLI (cf) vs Render MCP Server](https://www.anchorterminal.com/compare/cloudflare-cli-vs-render-mcp-server.md)\n- [InfrOS MCP Server vs neckbeard](https://www.anchorterminal.com/compare/infros-mcp-vs-neckbeard.md)\n- [InfrOS MCP Server vs Terraform MCP Server](https://www.anchorterminal.com/compare/infros-mcp-vs-terraform-mcp.md)\n- [AWS MCP Servers vs InfrOS MCP Server](https://www.anchorterminal.com/compare/aws-mcp-servers-vs-infros-mcp.md)\n- [Azure MCP Server vs InfrOS MCP Server](https://www.anchorterminal.com/compare/azure-mcp-vs-infros-mcp.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "InfrOS MCP Server vs Render MCP Server",
        "url": ""
      }
    ],
    "description": "Render scores 69.4 (B) to InfrOS's 26.8 (F) for cloud hosting. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "InfrOS MCP Server F 26.8",
      "Render MCP Server B 69.4",
      "scores"
    ],
    "h1": "InfrOS MCP Server vs Render MCP Server",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/infros-mcp-vs-render-mcp-server",
    "published": "2026-10-01",
    "section": "tools",
    "title": "InfrOS vs Render for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/infros-mcp-vs-render-mcp-server"
  },
  "tokens": {
    "markdown": 4400,
    "slim": 1080
  },
  "version": 1
}
