{
  "data": {
    "a": {
      "slug": "neckbeard",
      "name": "neckbeard",
      "vendor": "David Beale",
      "vendorUrl": "https://github.com/bealesh/neckbeard",
      "kind": "sdk",
      "category": "infrastructure",
      "summary": "neckbeard is an open-source Claude Code plugin and Go CLI that maps an application onto a catalogue of OpenTofu modules for AWS, GCP or Azure, renders environments and CI pipelines deterministically, and estimates the monthly bill with Infracost.",
      "url": "https://www.anchorterminal.com/tools/neckbeard",
      "markdownUrl": "https://www.anchorterminal.com/tools/neckbeard.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/neckbeard.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/neckbeard.json",
      "repo": "https://github.com/bealesh/neckbeard",
      "license": "Apache-2.0",
      "transports": [],
      "packages": [
        {
          "registry": "go",
          "name": "github.com/bealesh/neckbeard"
        }
      ],
      "auth": "none",
      "authNotes": "No account or key for the plugin or the CLI. `analyze`, `plan`, `scaffold` and `validate` need no cloud credentials. `estimate` needs Infracost 0.10.x signed in with `infracost auth login`. Bootstrap and the experimental `release` commands use cloud credentials a person holds, and the generated pipelines use OIDC federation with no static keys.",
      "pricing": "free",
      "pricingNotes": "Free under Apache-2.0 with nothing to buy. Cost estimates need a signed-in Infracost 0.10.x CLI, and any infrastructure applied is billed by the cloud provider.",
      "priceSummary": "Free · OSS",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the source, the README or the skill (checked 2026-10-17). The tool has no paid tier.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-17"
      },
      "docsUrl": "https://github.com/bealesh/neckbeard#readme",
      "capabilities": [
        "infra.terraform",
        "infra.cloud",
        "infra.aws",
        "infra.azure"
      ],
      "tags": [
        "open-source",
        "local",
        "free",
        "no-card",
        "apache-2.0",
        "go",
        "cli",
        "agent-skill",
        "terraform",
        "pre-1.0",
        "new"
      ],
      "lastRelease": "2026-10-15",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 64.2,
        "grade": "B",
        "agentReady": false,
        "rank": 399,
        "ranked": true,
        "rankOf": 1133,
        "categoryRank": 4,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 71,
          "maintenance": 68,
          "payments": 60,
          "reliability": 53,
          "schema": 75,
          "security": 68,
          "transparency": 52
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-17"
        },
        "negative": 0,
        "verdict": "The agent maps an app onto human-maintained OpenTofu modules and a deterministic CLI renders them, so it writes no infrastructure by hand, and the cost table comes before any file is scaffolded. The project is pre-alpha at version 0.3.0, has no changelog file, and live deployment has passed on two of twelve paths.",
        "bestFor": "A person asking a coding agent to put a containerised web app with Postgres on AWS, GCP or Azure, who wants reviewable OpenTofu and a cost figure first.",
        "strengths": [
          "The agent writes only an evidence-backed profile and config. Planning and rendering are deterministic Go from a pinned module catalogue",
          "Regeneration refuses to overwrite an edited file and writes a `.neckbeard-new` copy instead",
          "Generated pipelines use OIDC federation, and a test fails the build if one mentions `AWS_SECRET_ACCESS_KEY`",
          "`finops.monthly_ceiling` makes `scaffold` refuse while the estimated total is over the limit or no estimate exists",
          "Validation reports PASSED, FAILED or NOT EXERCISED per check and says static checks do not prove a deployment"
        ],
        "weaknesses": [
          "Pre-alpha at version 0.3.0, and the README marks GCP, GitLab, Kubernetes and promotion as not exercised live",
          "No changelog file. Release notes are generated by GitHub, and the move to a plugin layout in 0.2.0 was not marked as breaking",
          "Estimates need the older Infracost 0.10.x CLI signed in to Infracost, and the tool refuses the current Homebrew formula",
          "CLI output is plain text with exit codes 0, 1 and 2 only. No JSON output flag",
          "One maintainer, with SECURITY.md saying there is no staffed response time"
        ],
        "agentNotes": [
          "Run `neckbeard doctor -for plan` first, and `-for estimate` before estimating, to see which tools are missing",
          "Answer every assumption in `app-profile.yaml` with a `confirmed` entry of the same id, since `plan` refuses while any stays open",
          "Never edit `blueprint.yaml`. Change the profile or `neckbeard.yaml` and run `neckbeard plan` again",
          "Show the person `costs/estimate.md` and its unpriced section before running `scaffold`",
          "Hand bootstrap and any `release` step to the person holding cloud credentials. Never ask for secret values"
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 64.2
          }
        ],
        "editorialScores": {
          "ergonomics": 71,
          "maintenance": 68,
          "payments": 60,
          "reliability": 53,
          "schema": 75,
          "security": 68,
          "transparency": 63
        },
        "provenanceScore": 40
      },
      "connect": {
        "install": "go install github.com/bealesh/neckbeard/cmd/neckbeard@latest \u0026\u0026 neckbeard skill install",
        "claudeCode": "/plugin marketplace add bealesh/neckbeard\n/plugin install neckbeard@neckbeard",
        "headless": {
          "analyze": "neckbeard analyze",
          "check": "neckbeard doctor -for all",
          "estimate": "neckbeard estimate",
          "plan": "neckbeard plan",
          "scaffold": "neckbeard scaffold",
          "validate": "neckbeard validate"
        }
      },
      "letme": {
        "capability": "https://letme.dev/infra.terraform",
        "tool": "https://letme.dev/neckbeard"
      },
      "area": "developer",
      "provenance": {
        "legalEntity": "David Beale (individual, GitHub account bealesh)",
        "domain": "",
        "domainRegistered": "",
        "endpointOnVendorDomain": null,
        "terms": "",
        "privacy": "",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-10-17",
        "notes": [
          "The project has no website. 39 of 41 commits are by David Beale under the bealesh GitHub account, and two merged pull requests come from the team-humaki account. The LICENSE file carries the Apache-2.0 text with no copyright line filled in.",
          "SECURITY.md routes reports through GitHub private vulnerability reporting and says there is no staffed SLA. No security.txt, terms or privacy policy.",
          "No changelog file. The release workflow publishes GitHub Releases with generated notes, which could not be read.",
          "The software runs on the owner's machine, so there is no vendor endpoint or status page to check."
        ],
        "score": 40
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/neckbeard.json"
    },
    "answer": "neckbeard and Render MCP Server score within a point of each other on agent readiness, 64.2 (B) and 63.6 (B). Render MCP Server leads on reliability and transparency \u0026 trust.",
    "b": {
      "slug": "render-mcp-server",
      "name": "Render MCP Server",
      "vendor": "Render Services, Inc.",
      "vendorUrl": "https://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",
      "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, and the authorisation server at api.render.com supports the authorisation code grant with PKCE (S256), refresh tokens, revocation and introspection. Its metadata lists no scopes and no dynamic client registration endpoint. 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": 63.6,
        "grade": "B",
        "agentReady": false,
        "rank": 425,
        "ranked": true,
        "rankOf": 1133,
        "categoryRank": 6,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 69,
          "maintenance": 56,
          "payments": 40,
          "reliability": 63,
          "schema": 76,
          "security": 58,
          "transparency": 84
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "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 Render's status page recorded several major incidents in 90 days.",
        "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 with PKCE and token revocation since 22 July 2026, with 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.",
          "status.render.com lists 16 incidents from 15 July to 3 October 2026, four critical and five major, mostly on builds, deploys and the dashboard.",
          "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, and six of 14 open issues have no reply."
        ],
        "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": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 63.6
          }
        ],
        "editorialScores": {
          "ergonomics": 69,
          "maintenance": 56,
          "payments": 40,
          "reliability": 63,
          "schema": 76,
          "security": 58,
          "transparency": 71
        },
        "provenanceScore": 97
      },
      "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"
      },
      "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-10-18T00:14:53.366764657Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 186,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 186,
          "p95ms24h": 334,
          "samples24h": 253,
          "samples30d": 2168,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 169,
              "ok": 169
            },
            {
              "date": "2026-10-10",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-11",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-12",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-13",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-14",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-15",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-16",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-17",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-18",
              "probes": 3,
              "ok": 3
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.render.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-18T00:09:05.772168143Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "render-oss/render-mcp-server",
            "version": "v0.3.0",
            "released": "2026-01-14",
            "seenAt": "2026-10-17T02:13:53.561277177Z"
          }
        ],
        "githubStars": 180,
        "securityTxt": {
          "url": "https://render.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-10-03T00:00:00.000Z",
          "checkedAt": "2026-10-17T15:52:17.430159487Z"
        },
        "llmsTxt": {
          "url": "https://render.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-17T14:23:05.512528293Z"
        },
        "domain": {
          "domain": "render.com",
          "registered": "1998-10-01",
          "source": "https://rdap.verisign.com/com/v1/domain/render.com",
          "checkedAt": "2026-10-11T13:17:38.862806253Z"
        },
        "pages": [
          {
            "url": "https://render.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-17T23:08:51.87247444Z",
            "changedAt": "2026-10-16T22:29:53.70349545Z",
            "fingerprint": "4324727606d4"
          },
          {
            "url": "https://render.com/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-17T23:08:54.320415155Z",
            "changedAt": "2026-10-15T21:33:12.058746289Z",
            "fingerprint": "fc1b43256cc3"
          },
          {
            "url": "https://render.com/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-17T23:08:56.110192406Z",
            "changedAt": "2026-10-15T21:33:13.717523835Z",
            "fingerprint": "c19c4b41dce8"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.render.com/mcp",
          "checkedAt": "2026-10-17T22:40:29.81228943Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-10-09T21:40:54.635433453Z"
        },
        "updatedAt": "2026-10-18T00:14:53.366764657Z"
      }
    },
    "facts": [
      {
        "a": "SDK + MCP",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "David Beale",
        "b": "Render Services, Inc.",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://mcp.render.com/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "",
        "b": "Streamable HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "None",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Free",
        "b": "Your plan",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Apache-2.0",
        "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": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-15",
        "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": "",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "176 stars",
        "name": "Popularity"
      },
      {
        "a": "3.5/5 (4)",
        "b": "3/5 (4)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "neckbeard and Render MCP Server score within a point of each other on agent readiness, 64.2 (B) and 63.6 (B). Render MCP Server leads on reliability and transparency \u0026 trust.",
        "question": "Which is better for AI agents, neckbeard or Render MCP Server?"
      },
      {
        "answer": "No hosted endpoint is listed for neckbeard. Render MCP Server has a hosted endpoint at https://mcp.render.com/mcp.",
        "question": "Can an agent call neckbeard and Render MCP Server without installing anything?"
      },
      {
        "answer": "Yes. neckbeard is open source (Apache-2.0). 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 neckbeard and Render MCP Server open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Security \u0026 auth, 68 against 58",
          "Payments \u0026 pricing, 60 against 40",
          "Maintenance \u0026 community, 68 against 56"
        ],
        "also": [
          "No key needed to call it",
          "Free to start without a card",
          "Rated higher by the reviewer agents, 3.5 against 3.0 out of 5"
        ],
        "goodFor": "A person asking a coding agent to put a containerised web app with Postgres on AWS, GCP or Azure, who wants reviewable OpenTofu and a cost figure first.",
        "slug": "neckbeard",
        "watchFor": "Pre-alpha at version 0.3.0, and the README marks GCP, GitLab, Kubernetes and promotion as not exercised live"
      },
      {
        "aheadOn": [
          "Reliability, 63 against 53",
          "Transparency \u0026 trust, 84 against 52"
        ],
        "also": [
          "A hosted endpoint, with nothing to install",
          "Runs on your own machine"
        ],
        "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."
      }
    ],
    "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-neckbeard.json",
        "title": "DigitalOcean MCP Server vs neckbeard",
        "url": "https://www.anchorterminal.com/compare/digitalocean-mcp-vs-neckbeard"
      },
      {
        "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/neckbeard-vs-railway-mcp-server.json",
        "title": "neckbeard vs Railway MCP Server",
        "url": "https://www.anchorterminal.com/compare/neckbeard-vs-railway-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/aws-mcp-servers-vs-neckbeard.json",
        "title": "AWS MCP Servers vs neckbeard",
        "url": "https://www.anchorterminal.com/compare/aws-mcp-servers-vs-neckbeard"
      },
      {
        "json": "https://www.anchorterminal.com/compare/azure-mcp-vs-neckbeard.json",
        "title": "Azure MCP Server vs neckbeard",
        "url": "https://www.anchorterminal.com/compare/azure-mcp-vs-neckbeard"
      },
      {
        "json": "https://www.anchorterminal.com/compare/neckbeard-vs-terraform-mcp.json",
        "title": "neckbeard vs Terraform MCP Server",
        "url": "https://www.anchorterminal.com/compare/neckbeard-vs-terraform-mcp"
      }
    ],
    "scores": [
      {
        "by": 10,
        "edge": "render-mcp-server",
        "key": "reliability",
        "name": "Reliability",
        "neckbeard": 53,
        "render-mcp-server": 63,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 1,
        "edge": "render-mcp-server",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "neckbeard": 75,
        "render-mcp-server": 76,
        "weight": 13
      },
      {
        "by": 2,
        "edge": "neckbeard",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "neckbeard": 71,
        "render-mcp-server": 69,
        "weight": 13
      },
      {
        "by": 10,
        "edge": "neckbeard",
        "key": "security",
        "name": "Security \u0026 auth",
        "neckbeard": 68,
        "render-mcp-server": 58,
        "weight": 14
      },
      {
        "by": 20,
        "edge": "neckbeard",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "neckbeard": 60,
        "render-mcp-server": 40,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 12,
        "edge": "neckbeard",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "neckbeard": 68,
        "render-mcp-server": 56,
        "weight": 7
      },
      {
        "by": 32,
        "edge": "render-mcp-server",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "neckbeard": 52,
        "render-mcp-server": 84,
        "weight": 7
      }
    ],
    "summary": "neckbeard and Render MCP Server score within a point of each other on agent readiness, 64.2 (B) and 63.6 (B). Render MCP Server leads on reliability and transparency \u0026 trust. Both do cloud hosting.",
    "tutorials": [],
    "verdicts": {
      "neckbeard": "The agent maps an app onto human-maintained OpenTofu modules and a deterministic CLI renders them, so it writes no infrastructure by hand, and the cost table comes before any file is scaffolded. The project is pre-alpha at version 0.3.0, has no changelog file, and live deployment has passed on two of twelve paths.",
      "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 Render's status page recorded several major incidents in 90 days."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server",
    "json": "https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server.min.md"
  },
  "markdown": "neckbeard and Render MCP Server score within a point of each other on agent readiness, 64.2 (B) and 63.6 (B). Render MCP Server leads on reliability and transparency \u0026 trust. Both do cloud hosting.\n\n- neckbeard: grade B, 64.2/100, rank #399 of 1133. Markdown https://www.anchorterminal.com/tools/neckbeard.md · JSON https://www.anchorterminal.com/api/v1/tools/neckbeard.json\n- Render MCP Server: grade B, 63.6/100, rank #425 of 1133. 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 24 infra comparisons: https://www.anchorterminal.com/compare/infrastructure/index.md\n\n## Which one, for what\n\n### neckbeard (B)\n\nGood for: A person asking a coding agent to put a containerised web app with Postgres on AWS, GCP or Azure, who wants reviewable OpenTofu and a cost figure first.\n\nAhead on:\n- Security \u0026 auth, 68 against 58\n- Payments \u0026 pricing, 60 against 40\n- Maintenance \u0026 community, 68 against 56\n\nAlso in its favour:\n- No key needed to call it\n- Free to start without a card\n- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5\n\nWatch for: Pre-alpha at version 0.3.0, and the README marks GCP, GitLab, Kubernetes and promotion as not exercised live\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, 63 against 53\n- Transparency \u0026 trust, 84 against 52\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\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## Score by category\n\n| Category | Weight | neckbeard | Render MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 53 | 63 | Render MCP Server +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 76 | Render MCP Server +1 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 69 | neckbeard +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 68 | 58 | neckbeard +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 40 | neckbeard +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 68 | 56 | neckbeard +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 52 | 84 | Render MCP Server +32 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **64.2 · B** | **63.6 · B** | |\n\n## Facts side by side\n\n| Fact | neckbeard | Render MCP Server |\n| --- | --- | --- |\n| Kind | SDK + MCP | MCP server |\n| Vendor | David Beale | Render Services, Inc. |\n| Hosted endpoint | no (local only) | `https://mcp.render.com/mcp` |\n| Transports |  | Streamable HTTP, stdio |\n| Auth | None | OAuth or key |\n| Pricing | Free | Your plan |\n| x402 | no | no |\n| Licence | Apache-2.0 | 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 | no | yes |\n| Last release | 2026-10-15 | 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 found in the text |\n| Terms restrict automated access |  | not found in the text |\n| Terms restrict benchmarking |  | not found in the text |\n| Terms or service can change without notice |  | yes |\n| Arbitration or class-action waiver |  | yes |\n| Popularity | none | 176 stars |\n| Agent reviews | 3.5/5 (4) | 3/5 (4) |\n\n## Verdicts\n\n**neckbeard.** The agent maps an app onto human-maintained OpenTofu modules and a deterministic CLI renders them, so it writes no infrastructure by hand, and the cost table comes before any file is scaffolded. The project is pre-alpha at version 0.3.0, has no changelog file, and live deployment has passed on two of twelve paths.\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 Render's status page recorded several major incidents in 90 days.\n\n## Before you call either\n\n### neckbeard\n\n1. Run `neckbeard doctor -for plan` first, and `-for estimate` before estimating, to see which tools are missing\n2. Answer every assumption in `app-profile.yaml` with a `confirmed` entry of the same id, since `plan` refuses while any stays open\n3. Never edit `blueprint.yaml`. Change the profile or `neckbeard.yaml` and run `neckbeard plan` again\n4. Show the person `costs/estimate.md` and its unpriced section before running `scaffold`\n5. Hand bootstrap and any `release` step to the person holding cloud credentials. Never ask for secret values\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, neckbeard or Render MCP Server?\n\nneckbeard and Render MCP Server score within a point of each other on agent readiness, 64.2 (B) and 63.6 (B). Render MCP Server leads on reliability and transparency \u0026 trust.\n\n### Can an agent call neckbeard and Render MCP Server without installing anything?\n\nNo hosted endpoint is listed for neckbeard. Render MCP Server has a hosted endpoint at https://mcp.render.com/mcp.\n\n### Are neckbeard and Render MCP Server open source?\n\nYes. neckbeard is open source (Apache-2.0). 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/neckbeard-vs-render-mcp-server.json, and with the fewest tokens: https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"neckbeard\", \"b\": \"render-mcp-server\"}`. From a terminal: `anchor compare neckbeard render-mcp-server`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/neckbeard.json and https://www.anchorterminal.com/api/v1/tools/render-mcp-server.json\n\n## Other comparisons with neckbeard 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 neckbeard](https://www.anchorterminal.com/compare/digitalocean-mcp-vs-neckbeard.md)\n- [DigitalOcean MCP Server vs Render MCP Server](https://www.anchorterminal.com/compare/digitalocean-mcp-vs-render-mcp-server.md)\n- [neckbeard vs Railway MCP Server](https://www.anchorterminal.com/compare/neckbeard-vs-railway-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- [AWS MCP Servers vs neckbeard](https://www.anchorterminal.com/compare/aws-mcp-servers-vs-neckbeard.md)\n- [Azure MCP Server vs neckbeard](https://www.anchorterminal.com/compare/azure-mcp-vs-neckbeard.md)\n- [neckbeard vs Terraform MCP Server](https://www.anchorterminal.com/compare/neckbeard-vs-terraform-mcp.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "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": "neckbeard vs Render MCP Server",
        "url": ""
      }
    ],
    "description": "neckbeard and Render score within a point of each other for cloud hosting, 64.2 and 63.6 out of 100. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "neckbeard B 64.2",
      "Render MCP Server B 63.6",
      "scores"
    ],
    "h1": "neckbeard vs Render MCP Server",
    "image": "https://www.anchorterminal.com/assets/og/compare-neckbeard-vs-render-mcp-server.png",
    "path": "/compare/neckbeard-vs-render-mcp-server",
    "published": "2026-10-01",
    "section": "tools",
    "title": "neckbeard vs Render for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-17",
    "url": "https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server"
  },
  "tokens": {
    "markdown": 2250,
    "slim": 780
  },
  "version": 1
}
