Intercom: the 360 agent-readiness check

Intercom scores 81 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 2: a public API, OAuth. Markdown on request, a server card and a specification: the shape to copy.

On 9 November 2026 the public site at intercom.com scored 81 of 100 on Ora's agent-readiness scan, a B, in Ora's Communication & Support 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: Intercom offers strong REST API coverage and a published OpenAPI spec, but lacks WebMCP support, which would let agents interact with its pages directly.

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

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

• 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
• JSON error responses: fail, 0 of 4, about 2.7 points to gain. Ora saw: API does not return JSON error responses (or no API detected)
• Scoped permissions: partial, 2 of 5, about 2 points to gain. Ora saw: Scoped permissions described at https://www.intercom.com, but no machine-readable scope declaration found (OpenAPI oauth2 scopes or RFC 9728 scopes_supported)
• ARD discovery: fail, 0 of 1, about 1.6 points to gain. Ora saw: No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json
• Listed in MCP registries: fail, 0 of 1, about 1.6 points to gain. Ora saw: No verified entry in the official MCP Registry or on Smithery, and no npm or PyPI package of yours that runs as an MCP server. To pass,

Our read

Intercom's 81 is one of the few in this directory earned on the older and the newer surfaces at once. The MCP server at mcp.intercom.com/mcp answers and requires authentication, its server card sits at /.well-known/mcp/, OAuth authorization server metadata is on the same host, an OpenAPI specification in YAML is published, the REST documentation scores 7 of 7, SDKs are in npm and Go, intercom.com serves an llms.txt and returns markdown when an agent asks for it with an Accept header, which almost no company here does. The points left are small and specific: the endpoints Ora tried did not answer errors as JSON, scopes are described in prose rather than declared, there is no ARD catalog and no entry in the official MCP Registry or on Smithery, and no WebMCP registration. The home page is 2 percent text. For a support platform that agents will be asked to read and write, this is the shape to copy.

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.