Netlify: the 360 agent-readiness check

Netlify scores 90 of 100 on Ora's agent-readiness scan, an A, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 4: an OpenAPI specification, a public API, OAuth, a command line. An Access layer of 64 of 65, the highest share of the first sixty.

On 9 November 2026 the public site at netlify.com scored 90 of 100 on Ora's agent-readiness scan, an A, in Ora's Infrastructure category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: Netlify offers strong discovery and authentication support for agents, and adding WebMCP support with scoped OAuth permissions would close its biggest gaps.

The score

What an agent can do

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

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

At the door

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

What an agent can read

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

Found and recommended

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

Payments

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

The fixes worth most points

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

• WebMCP support: fail, 0 of 5, about 2.3 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 8 of 8 same-origin script bundle(s) for modelContext registrations)
• Brand name discoverability: partial, 1 of 3, about 1.9 points to gain. Ora saw: netlify.com ranks #8 for "Netlify" (searched your brand name alone: no main product term from your homepage qualified)
• Idempotency-Key support: fail, 0 of 3, about 1.4 points to gain. Ora saw: No REST Idempotency-Key support detected
• Scoped permissions: partial, 2 of 5, about 1.4 points to gain. Ora saw: OpenAPI declares security schemes but no named OAuth scopes - agents get all-or-nothing access. Declare per-scope grants (e.g. read:*, write:*) in the spec.
• REST versioning / deprecation policy: partial, 2 of 3, about 0.5 points to gain. Ora saw: API versioning found (URL versioning (servers or paths)) but no deprecation or sunset policy detected - add Sunset/Deprecation headers or a deprecation policy page

Our read

Netlify's 90 is built on an Access layer of 64 of 65, the highest share in this set. The MCP server at mcp.netlify.com/mcp answers and asks for authentication, its server card sits at /.well-known/mcp/, OAuth authorization server metadata is published, an OpenAPI 3.0.0 specification is at netlify.com/openapi.json, netlify-cli is on npm, SDKs are in three registries, an agent skills index lists 14 skills, and the documentation host serves an llms.txt and markdown twins with the right content type. The gaps Ora names are the ones most of this directory shares: no WebMCP registration in eight script bundles, security schemes without named scopes, no Idempotency-Key on REST, and a versioning policy with no deprecation or sunset terms. The brand search places the domain eighth for its own name, and the home page is 2.4 percent text. An A that is one specification detail from more.

Test your own surfaces

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

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

All 360 checks, one company a day. Corrections to the corrections page.