HashiCorp: the 360 agent-readiness check
HashiCorp scores 60 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 1: OAuth. In the directory, HashiCorp no MCP endpoint on record. A half-open door and an MCP server that exists in documentation.
On 9 November 2026 the public site at hashicorp.com scored 60 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: HashiCorp offers developer resource discoverability, but lacks an OpenAPI specification.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 24 of 56 | 43% |
| Access | Can agents read it | 34 of 57 | 60% |
| Discovery | Can agents find and recommend it | 14 of 15 | 93% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade C | 60 of 100 | 60% |
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, HashiCorp 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.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| MCP server / manifest mcp-server | Partial | 2 of 6 | MCP mentioned at https://developer.hashicorp.com/terraform/mcp-server/deploy 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 | Partial | 3 of 7 | API described in documentation at https://developer.hashicorp.com but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://developer.hashicorp.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer documentation portal found at https://developer.hashicorp.com |
| 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.hashicorp.com |
| 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 tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 8 of 42 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 | Fail | 0 of 3 | No CLI tool found |
| 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.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Not blocked by bot detection bot-detection | Pass | 2 of 2 | Site accessible to 1 agent user-agents (Claude-User). Can't verify ChatGPT-User, OAI-SearchBot, PerplexityBot. A bot shield, rate limit, or timeout stopped our test request. |
| Agent crawler reachability agent-crawler-reachability | Pass | 2 of 2 | Reachable to Claude-User. A bot shield, rate limit, or timeout stopped our test request. Real crawlers come from their own networks and may get through. (ChatGPT-User: cannot verify, OAI-SearchBot: cannot verify, |
| 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://hashicorp.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. 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 | Pass | 3 of 3 | 6252 chars, semantic headings (1 H1 + 9 H2s + 1 H3s), 8.6% content ratio |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~6K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://hashicorp.com/sitemap.xml with 3897 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://hashicorp.com/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 (GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended, ora-agent, DeepSeekBot) receives markdown when requesting HTML. |
| 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 | Fail | 0 of 4 | No JSON-LD structured data found on homepage |
| Organization schema completeness org-schema-completeness | Fail | 0 of 2 | No JSON-LD found - Organization schema missing |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Fail | 0 of 2 | No JSON-LD found - no entity linking possible |
| 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 | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Partial | 2 of 3 | When-to-use guidance found at https://developer.hashicorp.com |
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 | Pass | 3 of 3 | hashicorp.com ranks #2 for "HashiCorp | An IBM Company cloud security" |
| Wikipedia / Wikidata entity presence wikipedia-presence | Pass | 4 of 4 | Wikipedia "HashiCorp" and Wikidata Q21463167 both verified - domain confirmed on both sources |
| 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 | Pass | 1 of 1 | no detail published |
| ARD discovery ard-catalog | Fail | 0 of 1 | No /.well-known/ard.json (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 hashicorp.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 HashiCorp, 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 4 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
- WebMCP support: fail, 0 of 5, about 4 points to gain. Ora saw: No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 8 of 42 same-origin script bundle(s) for modelContext registrations)
- JSON error responses: fail, 0 of 4, about 3.2 points to gain. Ora saw: API does not return JSON error responses (or no API detected)
- MCP server / manifest: partial, 2 of 6, about 3.2 points to gain. Ora saw: MCP mentioned at https://developer.hashicorp.com/terraform/mcp-server/deploy but no standard manifest endpoint found
Our read
HashiCorp's door is half open: Ora's probe reached the site as Claude-User and could not verify ChatGPT-User, OAI-SearchBot or PerplexityBot, so the reachability row is partly unverified rather than failed. Behind it the act layer is documented rather than published. The Terraform MCP server is described at developer.hashicorp.com with no standard manifest endpoint, scoring 2 of 6 for a mention; the APIs are described with no machine-verifiable surface; there is no OpenAPI specification and no CLI package in a registry, which for the maker of terraform and vault is a probe result worth a second look. OpenID Connect discovery at auth.hashicorp.com and SDKs in npm and rubygems are the surfaces that count. The reading side is the odd part: a well-built home page at an 8.6 percent text ratio with one H1 and nine H2s, and no llms.txt and no JSON-LD on it. The brand search already carries the IBM name.
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 70All 360 checks, one company a day. Corrections to the corrections page.