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

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

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

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

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

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Usability | Can agents use it | 31 of 60 | 52% |
| Access | Can agents read it | 31 of 55 | 56% |
| Discovery | Can agents find and recommend it | 10 of 13 | 77% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade C | 59 of 100 | 59% |

## 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](https://agentmcpdirectory.com/directory/elastic-co/). 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 | 2 of 6 | MCP mentioned at https://www.elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server-api-keys but no standard manifest endpoint found |
| MCP well-known discovery mcp-well-known-discovery | Fail | 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | REST API documentation found at /docs/api. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://www.elastic.co |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /docs |
| OpenAPI spec published openapi-spec | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| 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 | Fail | 0 of 2 | No agent discovery file found |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OpenID Connect discovery endpoint found at https://auth.elastic.co |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 8 of 14 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: @elastic/cli |
| Multi-language SDK packages rest-sdk-packages | Partial | 2 of 3 | SDK packages found in npm, rubygems |
| JSON error responses json-error-responses | Fail | 0 of 4 | API does not return JSON error responses (or no API detected) |

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

| 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://elastic.co/. Declared policy only; |
| 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. One check in this group does not apply to this site and is left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript content-no-js | Partial | 2 of 3 | 10025 chars with H1, but 1.9% content ratio is below the 5% target |
| Page token budget page-token-budget | Pass | 1 of 1 | All 1 measured page fit an agent context budget (largest ~3K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://www.elastic.co/sitemap.xml with 13822 entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Pass | 1 of 1 | no detail published |
| llms.txt exists llms-txt-exists | Fail | 0 of 1 | No llms.txt found at /llms.txt or /.well-known/llms.txt. |
| llms.txt formatting llms-txt-formatting | Fail | 0 of 2 | No llms.txt found to evaluate quality |
| Markdown agent docs markdown-negotiation | Fail | 0 of 1 | Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md, |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://elastic.co/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| 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 | Partial | 1 of 4 | JSON-LD found (1 block(s)) but no identity type - use SoftwareApplication, Product, Organization, Person, or Article so agents can tell what this site is |
| Organization schema completeness org-schema-completeness | Fail | 0 of 2 | No Organization type found in JSON-LD |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Fail | 0 of 2 | No sameAs entity linking in JSON-LD - agents cannot disambiguate your brand |
| Schema type breadth schema-type-breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness metadata-completeness | Partial | 1 of 2 | 3/4 metadata signals present - missing: og:type |
| Agent instruction / when-to-use agent-instruction | Partial | 2 of 3 | When-to-use guidance found at https://www.elastic.co |

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

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability brand-search-accuracy | Partial | 1 of 3 | elastic.co ranks #9 for "Elastic search database" |
| Wikipedia / Wikidata entity presence wikipedia-presence | Partial | 2 of 4 | Wikidata Q22074922 (Elastic) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Listed on skills.sh skills-sh-listed | Fail | 0 of 1 | No official skills self-published on skills.sh |
| ARD discovery ard-catalog | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |

## 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](https://agentmcpdirectory.com/mcp-checks/) 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](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/elastic-agent-readiness/index.md)

## Sources

-   [Ora's scan of elastic.co, GET /api/score (vendor)](https://ora.ai/api/score/elastic.co?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
-   [elastic.co, the company's site](https://www.elastic.co/), read 9 November 2026

Last reviewed 9 November 2026