Asana: the 360 agent-readiness check
Asana scores 74 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. A live MCP server, three SDK registries and no file that describes the API.
On 9 November 2026 the public site at asana.com scored 74 of 100 on Ora's agent-readiness scan, a B, 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: Asana offers excellent developer discoverability and SDK availability, but lacks an OpenAPI specification.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 43 of 72 | 60% |
| Access | Can agents read it | 48 of 61 | 79% |
| Discovery | Can agents find and recommend it | 17 of 18 | 94% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 74 of 100 | 74% |
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.
In the directory, Asana 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.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| MCP server / manifest mcp-server | Partial | 5 of 6 | MCP server detected at https://mcp.asana.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 | Partial | 1 of 2 | MCP server at https://mcp.asana.com/mcp - list its server card, hosted on your own domain, in /.well-known/ai-catalog.json so MCP clients can discover it |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | REST API documentation found at https://developers.asana.com/docs/. GraphQL endpoint at https://api.asana.com/graphql is reachable; introspection requires authentication (API key / OAuth), |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://asana.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /developers |
| OpenAPI spec published openapi-spec | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| 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.asana.com (issuer=https://mcp.asana.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 (scanned 64 of 64 same-origin script bundle(s) for modelContext registrations) |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Fail | 0 of 3 | No CLI tool found |
| Multi-language SDK packages rest-sdk-packages | Pass | 3 of 3 | SDK packages found across 3 ecosystems: npm, pypi, rubygems |
| Rate limit response headers rate-limit-headers | Partial | 1 of 2 | The live API at https://developers.asana.com/ returns legacy x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset headers. Adopting the IETF RateLimit-* standard would earn full credit. |
| Idempotency-Key support idempotency-key-support | Fail | 0 of 3 | GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages |
| JSON error responses json-error-responses | Pass | 4 of 4 | no detail published |
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 18 of 18 checks (3 crawlers on 6 pages). AI training crawlers: allowed in 12 of 12 checks (2 crawlers on 6 pages), 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://asana.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 | 7375 chars with H1, but heading hierarchy skips H1 to H4; 4.6% content ratio is below the 5% target |
| Page token budget page-token-budget | Pass | 1 of 1 | All 8 measured pages fit an agent context budget (largest ~2K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://asana.com/sitemap-index.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Pass | 1 of 1 | no detail published |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://asana.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Pass | 2 of 2 | The llms.txt is well-formatted: 55 lines with markdown links, 5,691 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 | Path-suffix markdown docs served with text/markdown content-type: /developers.md, /index.md |
| Markdown URL fallback markdown-url-fallback | Pass | 2 of 2 | no detail published |
| 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 | Pass | 2 of 2 | no detail published |
| JSON-LD structured data json-ld | Pass | 4 of 4 | Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block(s)) |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Partial | 1 of 2 | Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub) |
| Schema type breadth schema-type-breadth | Partial | 1 of 2 | Some extended schema types found: BreadcrumbList - add 2 more types that match 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 | Pass | 3 of 3 | no detail published |
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 | asana.com ranks #2 for "Asana work management" |
| Wikipedia / Wikidata entity presence wikipedia-presence | Pass | 4 of 4 | Wikipedia "Asana, Inc." and Wikidata Q4468073 both verified - domain confirmed on both sources |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Pass | 1 of 1 | no detail published |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Pass | 2 of 2 | no detail published |
| 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. None of the 6 payment checks applied to asana.com.
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 Asana, 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.8 points to gain. Ora saw: No OpenAPI/Swagger specification found
- WebMCP support: fail, 0 of 5, about 3.1 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 64 of 64 same-origin script bundle(s) for modelContext registrations)
- CLI tool available: fail, 0 of 3, about 1.9 points to gain. Ora saw: No CLI tool found
- GraphQL typed error model: fail, 0 of 3, about 1.9 points to gain. Ora saw: GraphQL introspection auth-gated and no typed graphql error model documentation found on GraphQL-tagged pages
- Idempotency-Key support: fail, 0 of 3, about 1.9 points to gain. Ora saw: GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages
Our read
Asana's act layer is live and incompletely described, which is the pattern of this directory's middle. The MCP server at mcp.asana.com/mcp answers and requires authentication, with OAuth authorization server metadata on the same host; REST documentation is at developers.asana.com, SDKs are in npm, PyPI and rubygems, asana.com serves an llms.txt and markdown twins at /developers.md and /index.md with the right content type. Ora found no OpenAPI specification, which is about 4 points, no CLI, and a GraphQL endpoint that keeps introspection behind authentication with no typed error model or idempotency documentation on the pages that mention it. None of the 64 script bundles registers a WebMCP tool. The reading side is strong, with a complete Organization block, a 7,375-character home page and a brand search that places the domain second, though the heading tree skips from H1 to H4. A specification and a server card would make this an A.
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 70All 360 checks, one company a day. Corrections to the corrections page.