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

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

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

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

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

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Usability | Can agents use it | 50 of 67 | 75% |
| Access | Can agents read it | 55 of 63 | 87% |
| Discovery | Can agents find and recommend it | 12 of 14 | 86% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 81 of 100 | 81% |

## 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](https://agentmcpdirectory.com/directory/intercom-com/). 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 | 5 of 6 | MCP server detected at https://mcp.intercom.com/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery mcp-well-known-discovery | Pass | 2 of 2 | MCP server discoverable via server-card.json at /.well-known/mcp/ |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | REST API documentation found at /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.intercom.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /developers |
| OpenAPI spec published openapi-spec | Partial | 5 of 7 | OpenAPI spec (YAML) found at https://developers.intercom.com/_bundle/docs/references/@2.15/rest-api/api.intercom.io.yaml |
| API catalog (RFC 9727) api-catalog-rfc9727 | Partial | 1 of 2 | api-catalog linkset[0] has no 'item' entries |
| 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 | OAuth authorization server metadata at https://mcp.intercom.com |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Pass | 2 of 2 | no detail published |
| 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 |
| NLWeb /ask endpoint nlweb-ask | Pass | 1 of 1 | NLWeb /ask endpoint exists but requires authentication (HTTP 403, via POST) |
| CLI tool available cli-tool | Partial | 2 of 3 | CLI tool mentioned in llms.txt |
| Multi-language SDK packages rest-sdk-packages | Partial | 2 of 3 | SDK packages found in npm, go |
| 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 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://intercom.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.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript content-no-js | Partial | 2 of 3 | Homepage: 7283 chars with H1, but 2.0% content ratio is below the 5% target. 1 of 1 sampled inner page has text without JavaScript (4 skipped). |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~4K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://www.intercom.com/sitemap.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Fail | 0 of 1 | None of the 77 sampled sitemap entries carries a lastmod date. Add <lastmod> (W3C datetime) so agents can prioritize fresh content. |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://www.intercom.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Pass | 2 of 2 | The llms.txt is well-formatted: 173 lines with markdown links, 10,277 characters in total. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Pass | 1 of 1 | Returns markdown when requested via Accept header |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://intercom.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 (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 | Pass | 4 of 4 | Rich JSON-LD identity: Product with name, description, url, and offers/brand (1 block(s)) |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: contactPoint, address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Pass | 2 of 2 | no detail published |
| Schema type breadth schema-type-breadth | Partial | 1 of 2 | Some extended schema types found: ItemList, BreadcrumbList - add 1 more type that matches what the homepage shows, for full coverage |
| 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://www.intercom.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.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability brand-search-accuracy | Pass | 3 of 3 | intercom.com ranks #3 for "Intercom" (searched your brand name alone: no main product term from your homepage qualified) |
| Wikipedia / Wikidata entity presence wikipedia-presence | Partial | 2 of 4 | Wikidata Q48965215 (Intercom) 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 |
| Listed in MCP registries mcp-registry-listed | Fail | 0 of 1 | 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, |
| 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 |
| Registry branding registry-branding | Fail | 0 of 2 | No registry branding (name, icon, description) found |
| 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, 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.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| UCP - Universal Commerce Protocol ucp-support | Partial | 0 of 3 | no UCP (Universal Commerce Protocol) signals detected |
| ACP - Agentic Commerce Protocol acp-support | Partial | 0 of 3 | no ACP (Agentic Commerce Protocol) signals detected |
| ACP delegate payment acp-delegate-payment | Partial | 0 of 3 | No ACP Delegate Payment signals detected |
| AP2 - Agent Payments Protocol ap2-support | Partial | 0 of 3 | No AP2 (Agent Payments Protocol) signals detected |
| x402 payment protocol x402-support | Partial | 0 of 2 | No x402 payment protocol support detected |
| MPP payment protocol mpp-support | Partial | 0 of 2 | No MPP (Machine Payments Protocol) support detected |

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

## Sources

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

Last reviewed 9 November 2026