Linear: the 360 agent-readiness check

Linear scores 69 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 2: a public API, OAuth. Agent files done well, under a name that a search engine reads as a word.

On 9 November 2026 the public site at linear.app scored 69 of 100 on Ora's agent-readiness scan, a C, in Ora's Productivity 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: Linear offers strong agent-ready discovery and a published SDK, but lacks an OpenAPI specification for its API.

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, Linear 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. None of the 6 payment checks applied to linear.app.

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 Linear, 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 3.7 points to gain. Ora saw: No OpenAPI/Swagger specification found
• Scoped permissions: fail, 0 of 5, about 3.4 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• WebMCP support: fail, 0 of 5, about 3.4 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found
• Brand name discoverability: partial, 1 of 3, about 3.2 points to gain. Ora saw: linear.app ranks #9 for "Linear" (searched your brand name alone: no main product term from your homepage qualified)
• 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)

Our read

Linear does the agent files better than companies ten times its size and still reads as a C. The domain serves an llms.txt and an agents.md, with markdown twins at /agents.md, /developers.md and /index.md delivered as text/markdown; the MCP server at mcp.linear.app/mcp answers and requires authentication, with OAuth metadata on the same host and the server referenced in llms.txt; the REST documentation scores 7 of 7 and an SDK is on npm. The deductions are an OpenAPI specification that is not published, endpoints that do not answer errors as JSON, no declared scopes and no WebMCP registration, about 13 points between them, plus a brand search that places linear.app ninth for a word that means something else. The home page carries no JSON-LD and skips from H1 to H3 at a 1.3 percent text ratio. The act layer is live; the specification and an Organization block are what the checklist asks for next.

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.