Elastic: the 360 agent-readiness check

Elastic scores 59 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 3: a public API, OAuth, a command line. A documented MCP server with no address, on a domain with no llms.txt.

On 9 November 2026 the public site at elastic.co scored 59 of 100 on Ora's agent-readiness scan, a C, 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: Elastic offers strong developer resource discovery and SDK packages, but lacks an OpenAPI specification.

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, Elastic no MCP endpoint on record; 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. One check in this group does not apply to this site and is 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. One check in this group does not apply to this site and is left out.

Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. 2 checks in this group do not apply to this site and are left out.

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 elastic.co.

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 Elastic, 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.2 points to gain. Ora saw: No OpenAPI/Swagger specification found
• Scoped permissions: fail, 0 of 5, about 3.7 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• WebMCP support: fail, 0 of 5, about 3.7 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 8 of 14 same-origin script bundle(s) for modelContext registrations)
• Brand name discoverability: partial, 1 of 3, about 3.4 points to gain. Ora saw: elastic.co ranks #9 for "Elastic search database"
• JSON error responses: fail, 0 of 4, about 3 points to gain. Ora saw: API does not return JSON error responses (or no API detected)

Our read

Elastic's MCP server is documented at elastic.co/docs under the Agent Builder pages and reachable at no URL Ora could discover, so the check scores for a mention rather than a server. The older surfaces are present, with REST documentation scoring 7 of 7 at /docs/api, OpenID Connect discovery at auth.elastic.co, @elastic/cli on npm and SDKs in npm and rubygems, and the files around them are not: Ora found neither an OpenAPI specification nor declared scopes, there is no llms.txt at either location, and the endpoints it tried do not answer errors as JSON. The reading side pulls the score down further, with a JSON-LD block that has no identity type and a 10,025-character home page that is 1.9 percent text, while the brand search places elastic.co ninth for its product term. The WebMCP check could read only 8 of 14 script bundles. For the company behind the search engine in half the world's applications, the text file an agent reads first is the odd omission.

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.