{
  "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": "neckbeard scores 66 (B) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category.",
    "b": {
      "slug": "neckbeard",
      "name": "neckbeard",
      "vendor": "David Beale",
      "vendorUrl": "https://github.com/bealesh/neckbeard",
      "company": "neckbeard.sh",
      "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",
      "dns": "neckbeard.grade.anchorterminal.com",
      "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": 66,
        "grade": "B",
        "agentReady": false,
        "rank": 507,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 7,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 71,
          "maintenance": 68,
          "payments": 90,
          "reliability": 53,
          "schema": 75,
          "security": 68,
          "transparency": 52
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-02"
        },
        "negative": -2,
        "negativeNotes": [
          "2026-11-02. neckbeard.sh, the project site linked from the README and plugin.json, still presents the reference cost table ($77 a month on Cloud Run to about $801 on AKS) as \"live prices\", with no notice, while the README and the postmortem dated 22 October 2026 say those figures are withdrawn as undercounted. A claim the project itself has withdrawn, standing on one page, the minimum for a misleading claim, -2 (https://neckbeard.sh/; https://github.com/bealesh/neckbeard/blob/main/docs/findings/2026-10-22-cost-estimator-postmortem.md)"
        ],
        "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 with no changelog file, and its site still shows reference cost figures the project withdrew in October. Live deployment has passed on two 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, with v0.3.0 the stable release, 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",
          "The project withdrew its reference cost figures as undercounted in late October, yet neckbeard.sh still showed them as live prices on 2 November",
          "Estimates need the older Infracost 0.10.x CLI signed in to Infracost, and the tool refuses the current Homebrew formula",
          "One main 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`, its usage assumptions and its unpriced section before running `scaffold`, and treat the totals as estimates, not bills",
          "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": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 66
          }
        ],
        "editorialScores": {
          "ergonomics": 71,
          "maintenance": 68,
          "payments": 90,
          "reliability": 53,
          "schema": 75,
          "security": 68,
          "transparency": 63
        },
        "provenanceScore": 40,
        "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": {
        "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": "neckbeard.sh",
        "domainRegistered": "",
        "endpointOnVendorDomain": null,
        "terms": "",
        "privacy": "",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-02",
        "notes": [
          "Since 19 October the README and plugin.json link a project site at neckbeard.sh, a single page with a contact address at that domain. Its registration date was not read. 47 of 51 commits are by David Beale under the bealesh GitHub account, three come from the team-humaki account and one from Greg Sadetsky. 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. neckbeard.sh answers 404 for /.well-known/security.txt. No terms or privacy policy.",
          "No changelog file. The release workflow publishes GitHub Releases with generated notes, which could not be read, and pre-release tags are published as GitHub pre-releases. A written note for v0.4.0-beta.1 sits in docs/releases.",
          "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",
      "live": {
        "slug": "neckbeard",
        "versions": [
          {
            "registry": "github",
            "name": "bealesh/neckbeard",
            "version": "v0.4.0-beta.1",
            "released": "2026-10-26",
            "seenAt": "2026-11-18T18:10:56.426019986Z"
          }
        ],
        "githubStars": 281,
        "securityTxt": {
          "url": "https://neckbeard.sh/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:29:54.954820005Z"
        },
        "domain": {
          "domain": "neckbeard.sh",
          "checkedAt": "2026-11-15T15:26:47.934959005Z"
        },
        "github": {
          "repo": "bealesh/neckbeard",
          "checkedAt": "2026-11-16T11:46:48.706161083Z",
          "stars": 281,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-06T04:44:25Z",
          "openIssues": 11,
          "openPRs": 5,
          "issuesOpened90d": 22,
          "issuesClosed90d": 11,
          "prsMerged90d": 39,
          "ci": {
            "branch": "main",
            "runs": 50,
            "success": 41,
            "failure": 9,
            "other": 0,
            "latest": "success",
            "latestAt": "2026-11-02T21:39:35Z"
          },
          "replies": {
            "sampled": 22,
            "unanswered": 11,
            "medianDays": 6.2
          }
        },
        "updatedAt": "2026-11-18T18:10:56.426019986Z"
      }
    },
    "edges": [
      {
        "by": 60,
        "category": "schema",
        "leads": "neckbeard",
        "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": "Graded on the CLI and its skill. JSON Schema 2020-12 files for `neckbeard.yaml`, `app-profile.yaml`, the blueprint and the environment manifest, printed by `neckbeard schema`. Command output is text, with the estimate also written as JSON (18 of 25). The skill, two reference files and five commands are Markdown written for agents (10). The skill's description says when to load it, and SKILL.md says what the agent must not do, such as hand-write HCL, map an unsupported need onto the nearest module or read secret values (17 of 20). The schemas use enums, required fields and `additionalProperties: false`, and `neckbeard presets` prints the allowed tiers (13 of 15). The onboarding reference has a complete config and examples for existing databases and unsupported needs. Errors are plain `error:` lines with no catalogue, though many name the next step (9 of 15). Semantic version tags on the CLI and the catalogue, generated GitHub release notes we couldn't read, and since 26 October a written note for the v0.4.0-beta.1 pre-release in docs/releases, with no changelog file (8 of 15). Total 75."
        },
        "scores": {
          "a": 15,
          "b": 75
        }
      },
      {
        "by": 50,
        "category": "ergonomics",
        "leads": "neckbeard",
        "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": "No tool definitions. INSTALL.md puts the always-on SessionStart context at about 280 tokens, and SKILL.md (about 9 KB) and two references (about 13 KB) load when needed. Results go to files on disk with a short summary on stdout (20 of 25). `doctor -for` narrows checks and `estimate` takes a comparison argument, with nothing to page (10 of 20). Errors name the fix, such as the ceiling error that lists four ways to bring the total down. Exit codes are 0, 1 and 2, with no code per failure class (14 of 20). Same inputs render the same bytes, regeneration refuses to overwrite edited files and writes a `.neckbeard-new` copy, `analyze` won't overwrite a profile without `-force`, and `prepare-database` stores its password first so a retry reuses it (18 of 20). Defaults for every path flag and tier presets. One CLI and no library in a second language (9 of 15). Total 71."
        },
        "scores": {
          "a": 21,
          "b": 71
        }
      },
      {
        "by": 50,
        "category": "payments",
        "leads": "neckbeard",
        "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 payment protocol (0). Read with the self-hosted rule. Free under Apache-2.0 with nothing to buy (20). No card or account for the plugin (20). Installs from the plugin marketplace or `go install` with no signup (20). Estimates need a person to sign in to Infracost, which is outside the product and not deducted. Total 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90."
        },
        "scores": {
          "a": 40,
          "b": 90
        }
      },
      {
        "by": 43,
        "category": "reliability",
        "leads": "neckbeard",
        "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": "Read with the local-software lines, since the owner runs the plugin and the CLI. The project is about six weeks old (first commit 8 September 2026) and was launched on Hacker News on 14 October. The Go module is on pkg.go.dev and the plugin's installer fetches a checksummed release binary for Linux or macOS, falling back to `go install`. The Go version is stated only in go.mod (1.27.1), and the release assets themselves couldn't be seen (17 of 20). A public test workflow runs gofmt, `go vet`, `go test`, the plugin and installer checks and a six-lane plan, scaffold and validate matrix on every pull request and push to main. We couldn't see whether main passes (20 of 25). GitHub's issue pages couldn't be read, so there is no readable record of open bugs. INSTALL.md no longer links issue #27 (it now cites a pairing trial that passed on 21 October), and the beta notes name open issues #28 and #44 (10 of 25). Semantic version tags and a written semver contract for the catalogue, but no changelog file, and the plugin-first change in 0.2.0 was not marked as breaking (6 of 15). The README still calls it pre-alpha. v0.3.0 is the stable release and v0.4.0-beta.1 (26 October 2026) a pre-release (0). Total 53."
        },
        "scores": {
          "a": 10,
          "b": 53
        }
      },
      {
        "by": 33,
        "category": "maintenance",
        "leads": "neckbeard",
        "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": "v0.3.0 on 15 October 2026 is the newest stable release, 18 days old on 2 November, and the pre-release v0.4.0-beta.1 with catalog-v0.4.1 followed on 26 October (30). v0.1.0 (commit of 11 September), v0.2.0 and v0.2.1 (14 October), v0.3.0 (15 October) and v0.4.0-beta.1 (26 October) inside 90 days, plus catalogue tags (20). GitHub's issue and pull request pages couldn't be read. The author answered about 20 comments on the Hacker News thread on 14 and 15 October, and pull requests from two other accounts were merged on 12 September, 15 October, 20 October (the Disco target, the first outside contribution) and 21 October (10 of 25). Not an MCP server and no SDK, and the plugin is in its own marketplace, not an official one (0). Dependabot runs weekly on actions and Go modules, actions are pinned by SHA and CI runs on every push. CI status unread (8 of 10). Total 68."
        },
        "scores": {
          "a": 35,
          "b": 68
        }
      },
      {
        "by": 26,
        "category": "transparency",
        "leads": "neckbeard",
        "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": "Apache-2.0 in LICENSE and plugin.json (30). No privacy statement. The README says secret values never pass through neckbeard, its state or git history, and the source we read has no telemetry. What `estimate` sends to Infracost's pricing service is not described (15 of 30). DESIGN.md section 6.3 commits the catalogue to stable input schemas and resource addresses within a major version, with a migration path for a major, and allows planner default changes before 1.0 with migration notes. No dated deprecation notices (8 of 20). No telemetry found, and the docs don't address it (10 of 20). Total 63."
        },
        "scores": {
          "a": 26,
          "b": 52
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "SDK + MCP",
        "name": "Kind"
      },
      {
        "a": "InfrOS",
        "b": "David Beale",
        "name": "Vendor"
      },
      {
        "a": "https://api.app.infros.io/assistant/mcp",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "",
        "name": "Transports"
      },
      {
        "a": "OAuth",
        "b": "None",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Free",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "none",
        "b": "Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "2026-11-05",
        "b": "2026-10-15",
        "name": "Last release"
      },
      {
        "a": "no document linked",
        "b": "no document linked",
        "name": "Terms last updated"
      },
      {
        "a": "no document linked",
        "b": "no document linked",
        "name": "Privacy policy last updated"
      },
      {
        "a": "none",
        "b": "3.5/5 (4)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "neckbeard scores 66 (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 neckbeard?"
      },
      {
        "answer": "InfrOS MCP Server has a hosted endpoint at https://api.app.infros.io/assistant/mcp. No hosted endpoint is listed for neckbeard.",
        "question": "Can an agent call InfrOS MCP Server and neckbeard without installing anything?"
      },
      {
        "answer": "No open-source release is listed for InfrOS MCP Server. neckbeard is open source (Apache-2.0).",
        "question": "Are InfrOS MCP Server and neckbeard open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": null,
        "also": [
          "A hosted endpoint, with nothing to install"
        ],
        "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, 53 against 10",
          "Schema \u0026 documentation, 75 against 15",
          "Agent ergonomics, 71 against 21",
          "Security \u0026 auth, 68 against 49",
          "Payments \u0026 pricing, 90 against 40",
          "Maintenance \u0026 community, 68 against 35",
          "Transparency \u0026 trust, 52 against 26"
        ],
        "also": [
          "No key needed to call it",
          "Open source"
        ],
        "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, with v0.3.0 the stable release, and the README marks GCP, GitLab, Kubernetes and promotion as not exercised live"
      }
    ],
    "history": {
      "infros-mcp": [
        {
          "causes": [
            "correction"
          ],
          "date": "2026-11-18",
          "delta": -0.6,
          "from": 27.4,
          "fromGrade": "F",
          "to": 26.8,
          "toGrade": "F"
        }
      ],
      "neckbeard": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 3.8,
          "from": 62.2,
          "fromGrade": "B",
          "to": 66,
          "toGrade": "B"
        },
        {
          "causes": [
            "event"
          ],
          "date": "2026-11-02",
          "delta": -2,
          "from": 64.2,
          "fromGrade": "B",
          "to": 62.2,
          "toGrade": "B"
        },
        {
          "causes": [
            "correction"
          ],
          "date": "2026-10-28",
          "delta": -0.3,
          "from": 64.5,
          "fromGrade": "B",
          "to": 64.2,
          "toGrade": "B"
        }
      ]
    },
    "job": {
      "capability": "infra.terraform",
      "name": "Infra terraform"
    },
    "others": [
      {
        "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-neckbeard.json",
        "title": "DigitalOcean MCP Server vs neckbeard",
        "url": "https://www.anchorterminal.com/compare/digitalocean-mcp-vs-neckbeard"
      },
      {
        "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/infros-mcp-vs-render-mcp-server.json",
        "title": "InfrOS MCP Server vs Render MCP Server",
        "url": "https://www.anchorterminal.com/compare/infros-mcp-vs-render-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/neckbeard-vs-netlify.json",
        "title": "neckbeard vs Netlify API + MCP",
        "url": "https://www.anchorterminal.com/compare/neckbeard-vs-netlify"
      },
      {
        "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/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/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/neckbeard-vs-terraform-mcp.json",
        "title": "neckbeard vs Terraform MCP Server",
        "url": "https://www.anchorterminal.com/compare/neckbeard-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/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-infros-mcp.json",
        "title": "Azure MCP Server vs InfrOS MCP Server",
        "url": "https://www.anchorterminal.com/compare/azure-mcp-vs-infros-mcp"
      },
      {
        "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"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 43,
        "edge": "neckbeard",
        "infros-mcp": 10,
        "key": "reliability",
        "name": "Reliability",
        "neckbeard": 53,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 60,
        "edge": "neckbeard",
        "infros-mcp": 15,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "neckbeard": 75,
        "weight": 13
      },
      {
        "by": 50,
        "edge": "neckbeard",
        "infros-mcp": 21,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "neckbeard": 71,
        "weight": 13
      },
      {
        "by": 19,
        "edge": "neckbeard",
        "infros-mcp": 49,
        "key": "security",
        "name": "Security \u0026 auth",
        "neckbeard": 68,
        "weight": 14
      },
      {
        "by": 50,
        "edge": "neckbeard",
        "infros-mcp": 40,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "neckbeard": 90,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 33,
        "edge": "neckbeard",
        "infros-mcp": 35,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "neckbeard": 68,
        "weight": 7
      },
      {
        "by": 26,
        "edge": "neckbeard",
        "infros-mcp": 26,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "neckbeard": 52,
        "weight": 7
      }
    ],
    "summary": "neckbeard scores 66 (B) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category. Both do infra terraform.",
    "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.",
      "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 with no changelog file, and its site still shows reference cost figures the project withdrew in October. Live deployment has passed on two paths."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/infros-mcp-vs-neckbeard",
    "json": "https://www.anchorterminal.com/compare/infros-mcp-vs-neckbeard.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/infros-mcp-vs-neckbeard.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/infros-mcp-vs-neckbeard.min.md"
  },
  "markdown": "neckbeard scores 66 (B) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category. Both do infra terraform.\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- neckbeard: grade B, 66/100, rank #507 of 1557. Markdown https://www.anchorterminal.com/tools/neckbeard.md · JSON https://www.anchorterminal.com/api/v1/tools/neckbeard.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- A hosted endpoint, with nothing to install\n\nWatch for: No public tool list, schemas or changelog. The endpoint requires OAuth before `initialize`\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- Reliability, 53 against 10\n- Schema \u0026 documentation, 75 against 15\n- Agent ergonomics, 71 against 21\n- Security \u0026 auth, 68 against 49\n- Payments \u0026 pricing, 90 against 40\n- Maintenance \u0026 community, 68 against 35\n- Transparency \u0026 trust, 52 against 26\n\nAlso in its favour:\n- No key needed to call it\n- Open source\n\nWatch for: Pre-alpha, with v0.3.0 the stable release, and the README marks GCP, GitLab, Kubernetes and promotion as not exercised live\n\n\n## Why the edge\n\n### Schema \u0026 documentation: neckbeard +60\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- neckbeard (75): Graded on the CLI and its skill. JSON Schema 2020-12 files for `neckbeard.yaml`, `app-profile.yaml`, the blueprint and the environment manifest, printed by `neckbeard schema`. Command output is text, with the estimate also written as JSON (18 of 25). The skill, two reference files and five commands are Markdown written for agents (10). The skill's description says when to load it, and SKILL.md says what the agent must not do, such as hand-write HCL, map an unsupported need onto the nearest module or read secret values (17 of 20). The schemas use enums, required fields and `additionalProperties: false`, and `neckbeard presets` prints the allowed tiers (13 of 15). The onboarding reference has a complete config and examples for existing databases and unsupported needs. Errors are plain `error:` lines with no catalogue, though many name the next step (9 of 15). Semantic version tags on the CLI and the catalogue, generated GitHub release notes we couldn't read, and since 26 October a written note for the v0.4.0-beta.1 pre-release in docs/releases, with no changelog file (8 of 15). Total 75.\n\n### Agent ergonomics: neckbeard +50\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- neckbeard (71): No tool definitions. INSTALL.md puts the always-on SessionStart context at about 280 tokens, and SKILL.md (about 9 KB) and two references (about 13 KB) load when needed. Results go to files on disk with a short summary on stdout (20 of 25). `doctor -for` narrows checks and `estimate` takes a comparison argument, with nothing to page (10 of 20). Errors name the fix, such as the ceiling error that lists four ways to bring the total down. Exit codes are 0, 1 and 2, with no code per failure class (14 of 20). Same inputs render the same bytes, regeneration refuses to overwrite edited files and writes a `.neckbeard-new` copy, `analyze` won't overwrite a profile without `-force`, and `prepare-database` stores its password first so a retry reuses it (18 of 20). Defaults for every path flag and tier presets. One CLI and no library in a second language (9 of 15). Total 71.\n\n### Payments \u0026 pricing: neckbeard +50\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- neckbeard (90): No payment protocol (0). Read with the self-hosted rule. Free under Apache-2.0 with nothing to buy (20). No card or account for the plugin (20). Installs from the plugin marketplace or `go install` with no signup (20). Estimates need a person to sign in to Infracost, which is outside the product and not deducted. Total 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.\n\n### Reliability: neckbeard +43\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- neckbeard (53): Read with the local-software lines, since the owner runs the plugin and the CLI. The project is about six weeks old (first commit 8 September 2026) and was launched on Hacker News on 14 October. The Go module is on pkg.go.dev and the plugin's installer fetches a checksummed release binary for Linux or macOS, falling back to `go install`. The Go version is stated only in go.mod (1.27.1), and the release assets themselves couldn't be seen (17 of 20). A public test workflow runs gofmt, `go vet`, `go test`, the plugin and installer checks and a six-lane plan, scaffold and validate matrix on every pull request and push to main. We couldn't see whether main passes (20 of 25). GitHub's issue pages couldn't be read, so there is no readable record of open bugs. INSTALL.md no longer links issue #27 (it now cites a pairing trial that passed on 21 October), and the beta notes name open issues #28 and #44 (10 of 25). Semantic version tags and a written semver contract for the catalogue, but no changelog file, and the plugin-first change in 0.2.0 was not marked as breaking (6 of 15). The README still calls it pre-alpha. v0.3.0 is the stable release and v0.4.0-beta.1 (26 October 2026) a pre-release (0). Total 53.\n\n### Maintenance \u0026 community: neckbeard +33\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- neckbeard (68): v0.3.0 on 15 October 2026 is the newest stable release, 18 days old on 2 November, and the pre-release v0.4.0-beta.1 with catalog-v0.4.1 followed on 26 October (30). v0.1.0 (commit of 11 September), v0.2.0 and v0.2.1 (14 October), v0.3.0 (15 October) and v0.4.0-beta.1 (26 October) inside 90 days, plus catalogue tags (20). GitHub's issue and pull request pages couldn't be read. The author answered about 20 comments on the Hacker News thread on 14 and 15 October, and pull requests from two other accounts were merged on 12 September, 15 October, 20 October (the Disco target, the first outside contribution) and 21 October (10 of 25). Not an MCP server and no SDK, and the plugin is in its own marketplace, not an official one (0). Dependabot runs weekly on actions and Go modules, actions are pinned by SHA and CI runs on every push. CI status unread (8 of 10). Total 68.\n\n### Transparency \u0026 trust: neckbeard +26\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- neckbeard (52): Apache-2.0 in LICENSE and plugin.json (30). No privacy statement. The README says secret values never pass through neckbeard, its state or git history, and the source we read has no telemetry. What `estimate` sends to Infracost's pricing service is not described (15 of 30). DESIGN.md section 6.3 commits the catalogue to stable input schemas and resource addresses within a major version, with a migration path for a major, and allows planner default changes before 1.0 with migration notes. No dated deprecation notices (8 of 20). No telemetry found, and the docs don't address it (10 of 20). Total 63.\n\n## Score by category\n\n| Category | Weight | InfrOS MCP Server | neckbeard | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 10 | 53 | neckbeard +43 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 15 | 75 | neckbeard +60 |\n| Agent ergonomics | 13% | 21 | 71 | neckbeard +50 |\n| Security \u0026 auth | 14% | 49 | 68 | neckbeard +19 |\n| Payments \u0026 pricing | 10% | 40 | 90 | neckbeard +50 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 35 | 68 | neckbeard +33 |\n| Transparency \u0026 trust | 7% | 26 | 52 | neckbeard +26 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **26.8 · F** | **66 · B** | |\n\n## Facts side by side\n\n| Fact | InfrOS MCP Server | neckbeard |\n| --- | --- | --- |\n| Kind | MCP server | SDK + MCP |\n| Vendor | InfrOS | David Beale |\n| Hosted endpoint | `https://api.app.infros.io/assistant/mcp` | no (local only) |\n| Transports | Streamable HTTP |  |\n| Auth | OAuth | None |\n| Pricing | Pay per use | Free |\n| x402 | no | no |\n| Licence | none | Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-11-05 | 2026-10-15 |\n| Terms last updated | no document linked | no document linked |\n| Privacy policy last updated | no document linked | no document linked |\n| Agent reviews | none | 3.5/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### neckbeard\n\n- +3.8 on 13 November 2026: checklist\n- -2.0 on 2 November 2026: negative event\n- -0.3 on 28 October 2026: 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**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 with no changelog file, and its site still shows reference cost figures the project withdrew in October. Live deployment has passed on two paths.\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### 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`, its usage assumptions and its unpriced section before running `scaffold`, and treat the totals as estimates, not bills\n5. Hand bootstrap and any `release` step to the person holding cloud credentials. Never ask for secret values\n\n## Questions\n\n### Which is better for AI agents, InfrOS MCP Server or neckbeard?\n\nneckbeard scores 66 (B) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category.\n\n### Can an agent call InfrOS MCP Server and neckbeard without installing anything?\n\nInfrOS MCP Server has a hosted endpoint at https://api.app.infros.io/assistant/mcp. No hosted endpoint is listed for neckbeard.\n\n### Are InfrOS MCP Server and neckbeard open source?\n\nNo open-source release is listed for InfrOS MCP Server. neckbeard is open source (Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/infros-mcp-vs-neckbeard.json, and with the fewest tokens: https://www.anchorterminal.com/compare/infros-mcp-vs-neckbeard.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"infros-mcp\", \"b\": \"neckbeard\"}`. From a terminal: `anchor compare infros-mcp neckbeard`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/infros-mcp.json and https://www.anchorterminal.com/api/v1/tools/neckbeard.json\n\n## Other comparisons with InfrOS MCP Server or neckbeard\n\n- [DigitalOcean MCP Server vs InfrOS MCP Server](https://www.anchorterminal.com/compare/digitalocean-mcp-vs-infros-mcp.md)\n- [DigitalOcean MCP Server vs neckbeard](https://www.anchorterminal.com/compare/digitalocean-mcp-vs-neckbeard.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- [InfrOS MCP Server vs Render MCP Server](https://www.anchorterminal.com/compare/infros-mcp-vs-render-mcp-server.md)\n- [neckbeard vs Netlify API + MCP](https://www.anchorterminal.com/compare/neckbeard-vs-netlify.md)\n- [neckbeard vs Railway MCP Server](https://www.anchorterminal.com/compare/neckbeard-vs-railway-mcp-server.md)\n- [neckbeard vs Render MCP Server](https://www.anchorterminal.com/compare/neckbeard-vs-render-mcp-server.md)\n- [InfrOS MCP Server vs Terraform MCP Server](https://www.anchorterminal.com/compare/infros-mcp-vs-terraform-mcp.md)\n- [neckbeard vs Terraform MCP Server](https://www.anchorterminal.com/compare/neckbeard-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- [AWS MCP Servers vs neckbeard](https://www.anchorterminal.com/compare/aws-mcp-servers-vs-neckbeard.md)\n- [Azure MCP Server vs InfrOS MCP Server](https://www.anchorterminal.com/compare/azure-mcp-vs-infros-mcp.md)\n- [Azure MCP Server vs neckbeard](https://www.anchorterminal.com/compare/azure-mcp-vs-neckbeard.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 neckbeard",
        "url": ""
      }
    ],
    "description": "neckbeard scores 66 (B) to InfrOS's 26.8 (F) for infra terraform. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "InfrOS MCP Server F 26.8",
      "neckbeard B 66",
      "scores"
    ],
    "h1": "InfrOS MCP Server vs neckbeard",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/infros-mcp-vs-neckbeard",
    "published": "2026-10-01",
    "section": "tools",
    "title": "InfrOS vs neckbeard for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/infros-mcp-vs-neckbeard"
  },
  "tokens": {
    "markdown": 4100,
    "slim": 830
  },
  "version": 1
}
