Contentful: the 360 agent-readiness check

Contentful scores 74 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 3: a public API, OAuth, a command line. A door Ora could not test, in front of a live but undescribed act layer.

On 9 November 2026 the public site at contentful.com scored 74 of 100 on Ora's agent-readiness scan, a B, in Ora's Developer Tools 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: Contentful offers a solid developer ecosystem and passes most discovery checks, but lacks a published OpenAPI specification for agents to build against.

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. 2 checks in this group do not apply to this site and are left out.

In the directory, Contentful 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. 2 checks in this group do not apply to this site and are left out.

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.

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 Contentful, 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.

• OpenAPI spec published: fail, 0 of 7, about 4.1 points to gain. Ora saw: No OpenAPI/Swagger specification found
• Scoped permissions: fail, 0 of 5, about 3.3 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• WebMCP support: fail, 0 of 5, about 3.3 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 32 of 32 same-origin script bundle(s) for modelContext registrations)
• Brand name discoverability: partial, 1 of 3, about 2.5 points to gain. Ora saw: contentful.com ranks #9 for "Contentful content management system"
• Agent instruction / when-to-use: fail, 0 of 3, about 1.8 points to gain. Ora saw: No agent instruction file with when-to-use guidance found

Our read

Contentful's door could not be tested: Ora's probe was refused, and the site also refused a normal browser visit, so the reachability row is unverified rather than failed and the first rows of the checklist are open questions on this read. What Ora did reach is a working act layer: the MCP server at mcp.contentful.com/mcp answers and requires authentication, llms.txt references it, OAuth authorization server metadata is on the MCP host, the REST documentation scores 7 of 7, contentful-cli is on npm and SDKs are in npm, PyPI and rubygems. Ora found no OpenAPI specification and no declared scopes, about 7 points, and no agent instruction file, and none of the 32 script bundles registers a WebMCP tool. The home page gives 7,162 characters with a heading tree that skips from H1 to H4, and the Organization block lacks its description; the brand search places the domain ninth for its own product term. A second scan would settle the door.

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.