mcp.linear.app agentic web readiness

A Manifest validity: 100% (1/1 valid, 0 errors, 6 warnings) · Surface score 49 (coverage 30 + breadth 9 + conformance 10). 5 standards observed across 3 of 9 steps; 1 manifest present (+ robots.txt), 0 errors, 6 warnings. Checked 2026-10-25 22:05:16 UTC. This grades the agent-facing files published at mcp.linear.app, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/mcp.linear.app.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), ID-JAG, CIMD 04 Readllms.txt 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`	valid	no blockquote summary under the title no Markdown links: list the pages an agent should read
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`	no AI tokens	no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (partial) no Sitemap: line no Agentmap: line (optional convention pointing agents at /.well-known/ard.json) no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
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.linear.app (streamable-http) — from /.well-known/oauth-protected-resource
llms.txt: linear-mcp, 0 links
robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed on public paths (subpaths disallowed under User-agent: *)
OAuth protected resource https://mcp.linear.app, authorization servers: https://mcp.linear.app

Standards observed

llms.txt https://mcp.linear.app/llms.txt
OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://mcp.linear.app/.well-known/oauth-protected-resource
Identity Assertion JWT Authorization Grant https://mcp.linear.app/.well-known/oauth-authorization-server
OAuth Client ID Metadata Document https://mcp.linear.app/.well-known/oauth-authorization-server
Model Context Protocol

Cheapest next steps

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.linear.app"}))

AGENTS.md: instructions for coding agents working on or with the site

Generate starter /AGENTS.md for mcp.linear.app

# Mcp for agents

Mcp and what it offers to agents

## Read the data, not the HTML
- Index: https://mcp.linear.app/llms.txt
- API description: https://mcp.linear.app/openapi.json
- Discovery catalog: https://mcp.linear.app/.well-known/ard.json

## Calling
- MCP server (Streamable HTTP): https://mcp.linear.app/mcp
- Rate limits and authentication: describe them here

## Conventions
- How to cite or attribute content
- What not to do (no scraping of /account/, no automated sign-ups, etc.)

Contact: security@mcp.linear.app

api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description (conditional spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "api-catalog-rfc9727", "domain": "mcp.linear.app"}))

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback llms_txt). Call the MCP endpoint at https://mcp.linear.app first. Do not scrape the HTML when a tool can answer.

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

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

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

Readiness subscores: reach 20/20, readability 10/30, capabilities 18/35, conformance 10/15, total 58/100, grade B.

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