mcp.intercom.com agentic web readiness

C Manifest validity: 0 manifests published (0 errors, 0 warnings) · Surface score 20 (coverage 20 + breadth 0 + conformance 0). 2 standards observed across 2 of 9 steps; 0 manifests present, 0 errors, 0 warnings. Checked 2026-10-25 22:03:31 UTC. This grades the agent-facing files published at mcp.intercom.com, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/mcp.intercom.com.svg) · JSON · Markdown · Re-check now

Coverage by step

01 Discovernothing observed 02 Identifynothing observed 03 PermitOAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)04 Readnothing observed 05 Act 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	absent HTTP 404
AI Catalog well-known file `/.well-known/ai-catalog.json`	absent HTTP 404
MCP Server Cards (SEP-2127) `/mcp/server-card`	absent HTTP 401
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 404
llms.txt `/llms.txt`	absent HTTP 404
AGENTS.md `/AGENTS.md`	absent HTTP 404
Agent Skills `/.well-known/agent-skills/index.json`	absent HTTP 404
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs `/.well-known/api-catalog`	absent HTTP 404
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	absent HTTP 404
security.txt (RFC 9116) `/.well-known/security.txt`	absent HTTP 404
auth.md `/auth.md`	absent HTTP 404
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

MCP endpoint https://mcp.intercom.com (streamable-http) — from /.well-known/oauth-protected-resource
OAuth protected resource https://mcp.intercom.com, authorization servers: https://mcp.intercom.com

Standards observed

OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://mcp.intercom.com/.well-known/oauth-protected-resource
Model Context Protocol

Cheapest next steps

llms.txt: one Markdown index file; the most widely read agent-facing file

Generate starter /llms.txt for mcp.intercom.com

# Mcp

> Mcp and what it offers to agents

Short notes an agent should know before using the site: what it is for, who runs it, how to cite it.

## Docs
- [Getting started](https://mcp.intercom.com/docs/getting-started): the first page to read
- [API reference](https://mcp.intercom.com/openapi.json): OpenAPI description

## Optional
- [Changelog](https://mcp.intercom.com/changelog): what changed, newest first

AI Crawler User-Agent Tokens in robots.txt: state what AI crawlers may do in robots.txt you already serve

Generate starter /robots.txt for mcp.intercom.com

# search and answer-engine crawlers
User-agent: Googlebot
User-agent: bingbot
User-agent: OAI-SearchBot
User-agent: Claude-SearchBot
User-agent: PerplexityBot
User-agent: ExaSearchBot
User-agent: TavilyBot
Allow: /

# model-training crawlers: choose Allow or Disallow and keep it explicit
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: Google-Extended
User-agent: Applebot-Extended
User-agent: CCBot
User-agent: meta-externalagent
User-agent: Bytespider
Disallow: /

# user-triggered fetchers (a person asked for this page)
User-agent: ChatGPT-User
User-agent: Claude-User
User-agent: Perplexity-User
Allow: /

# default fallback for unlisted crawlers (RFC 9309 §2.2.1: specific groups above take precedence over *)
User-agent: *
Allow: /
Disallow: /account/
Content-Signal: ai-train=no, search=yes, ai-input=yes

Sitemap: https://mcp.intercom.com/sitemap.xml
Agentmap: https://mcp.intercom.com/.well-known/ard.json

Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "mcp.intercom.com"}))

Agent pre-flight & practical readiness

Preferred mode: mcp. Call the MCP endpoint at https://mcp.intercom.com first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://mcp.intercom.com POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.

Practical readability: exa_parsable no, markdown negotiation no, render none, HTML quality none.

AI crawler posture: unspecified · Assistant access: OpenAI unspecified, Anthropic unspecified, Google unspecified, Perplexity unspecified, Exa unspecified.

Readiness subscores: reach 0/20, readability 0/30, capabilities 14/35, conformance 0/15, total 14/100, grade F.

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules