---
title: "Netlify: the 360 agent-readiness check | Agent MCP Directory"
description: "Netlify on Ora's agent-readiness scan, read 2026-11-09: 90 of 100, grade A, with the MCP, API and OAuth surfaces an agent can call."
canonical: https://agentmcpdirectory.com/blog/netlify-agent-readiness
site: "Agent MCP Directory"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# Netlify: the 360 agent-readiness check | Agent MCP Directory

> Netlify on Ora's agent-readiness scan, read 2026-11-09: 90 of 100, grade A, with the MCP, API and OAuth surfaces an agent can call.

Source: https://agentmcpdirectory.com/blog/netlify-agent-readiness
Site: Agent MCP Directory
Last reviewed: 2026-11-09

# 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](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) 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

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Usability | Can agents use it | 79 of 96 | 82% |
| Access | Can agents read it | 64 of 65 | 98% |
| Discovery | Can agents find and recommend it | 21 of 23 | 91% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade A | 90 of 100 | 90% |

## 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](https://agentmcpdirectory.com/directory/netlify-com/). 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.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| MCP server / manifest mcp-server | Partial | 5 of 6 | MCP server detected at https://mcp.netlify.com/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery mcp-well-known-discovery | Pass | 2 of 2 | MCP server discoverable via server-card.json at /.well-known/mcp/ |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | REST API documentation found at https://docs.netlify.com/build/functions/overview.md. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://docs.netlify.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at https://docs.netlify.com |
| OpenAPI spec published openapi-spec | Pass | 7 of 7 | OpenAPI spec found at https://netlify.com/openapi.json (version: 3.0.0) |
| API catalog (RFC 9727) api-catalog-rfc9727 | Pass | 2 of 2 | no detail published |
| A2A / agent-card a2a-agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file agent-discovery-file | Pass | 2 of 2 | Agent Skills index (agentskills.io) found at /.well-known/agent-skills/index.json with 14 skill(s) |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OAuth authorization server metadata at https://mcp.netlify.com/ |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Pass | 2 of 2 | no detail published |
| auth.md exists auth-md-exists | Pass | 2 of 2 | no detail published |
| WebMCP support webmcp | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 8 of 8 same-origin script bundle(s) for modelContext registrations) |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Pass | 3 of 3 | CLI package found on npm: netlify-cli |
| Multi-language SDK packages rest-sdk-packages | Pass | 3 of 3 | SDK packages found across 3 ecosystems: npm, go, rubygems |
| Rate limit response headers rate-limit-headers | Partial | 1 of 2 | REST rate-limit headers documented in auth docs (https://netlify.com/auth.md), but not observed on a live response. |
| Idempotency-Key support idempotency-key-support | Fail | 0 of 3 | No REST Idempotency-Key support detected |
| JSON error responses json-error-responses | Pass | 4 of 4 | no detail published |

## At the door

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

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection bot-detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability agent-crawler-reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| robots.txt AI crawler policy robots-ai-policy-quality | Pass | 2 of 2 | AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 2 of 2 checks (2 crawlers on 1 page), not scored. |
| robots.txt agent-user policy robots-agent-user-policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://netlify.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (5 with substantive content) |
| Homepage not hidden from search noindex-directives | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
| Redirect hygiene redirect-hygiene | Pass | 1 of 1 | no detail published |
| Web Bot Auth directory web-bot-auth-directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |

## 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.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript content-no-js | Partial | 2 of 3 | Homepage: 6604 chars with H1, but 2.4% content ratio is below the 5% target. 5 of 5 sampled inner pages have text without JavaScript. |
| Page token budget page-token-budget | Pass | 1 of 1 | All 8 measured pages fit an agent context budget (largest ~5K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://www.netlify.com/sitemap-index.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Pass | 1 of 1 | no detail published |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://docs.netlify.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Pass | 2 of 2 | The llms.txt is well-formatted: 35 lines with markdown links, 2,971 characters in total. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Pass | 1 of 1 | Path-suffix markdown docs served with text/markdown content-type: /auth.md, /index.md |
| Markdown URL fallback markdown-url-fallback | Pass | 2 of 2 | no detail published |
| Bot-UA markdown serving agent-ua-markdown | Fail | 0 of 1 | No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. |
| Agent mode view agent-mode-view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| JSON-LD structured data json-ld | Pass | 4 of 4 | Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block(s)) |
| Organization schema completeness org-schema-completeness | Pass | 2 of 2 | no detail published |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Pass | 2 of 2 | no detail published |
| Schema type breadth schema-type-breadth | Pass | 2 of 2 | no detail published |
| Metadata completeness metadata-completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Pass | 3 of 3 | no detail published |

## Found and recommended

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

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability brand-search-accuracy | Partial | 1 of 3 | netlify.com ranks #8 for "Netlify" (searched your brand name alone: no main product term from your homepage qualified) |
| Wikipedia / Wikidata entity presence wikipedia-presence | Pass | 4 of 4 | Wikipedia "Netlify" and Wikidata Q56102498 both verified - domain confirmed on both sources |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Pass | 1 of 1 | no detail published |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Pass | 2 of 2 | no detail published |
| Registry branding registry-branding | Pass | 2 of 2 | no detail published |
| Listed on skills.sh skills-sh-listed | Pass | 1 of 1 | no detail published |
| ARD discovery ard-catalog | Pass | 1 of 1 | no detail published |

## 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](https://agentmcpdirectory.com/mcp-checks/) 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](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) 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](https://agentmcpdirectory.com/test-your-mcp-server/) 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.

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

[All 360 checks](https://agentmcpdirectory.com/blog/), one company a day. Corrections to [the corrections page](https://agentmcpdirectory.com/corrections/).

Edition

4 November 2026

Method

[How rows are verified](https://agentmcpdirectory.com/method/)

Data

[CSV and JSON](https://agentmcpdirectory.com/data/)

Markdown

[This page as markdown](https://agentmcpdirectory.com/blog/netlify-agent-readiness/index.md)

## Sources

-   [Ora's scan of netlify.com, GET /api/score (vendor)](https://ora.ai/api/score/netlify.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 9 November 2026
-   [Ora check catalogue, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 5 November 2026
-   [netlify.com, the company's site](https://www.netlify.com/), read 9 November 2026

Last reviewed 9 November 2026