McKesson: 67 of 100 on Ora's agent-readiness scan

In short

McKesson scores 67 of 100 on Ora's agent-readiness scan, grade C, read on 9 November 2026. 79 percent of the 132,085 domains Ora ranks score under 60, and the average score is 44. A readable distributor with no JSON-LD, scored on a Usability denominator of 24.

The score

McKesson is a pharmaceutical distributor and health technology company based in Texas.

  • 67of 100, grade C
    Ora's agent-readiness scan of mckesson.com, read 9 November 2026.
  • 9Discovery, of 10
    Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
  • 16Access, of 39
    Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
  • 18Usability, of 24
    Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
  • 0Payments, of 0
    No check in this layer applied to the site.

79 percent of the 132,085 domains Ora ranks score under 60, and the average score is 44.

Ora's one-line summary: Sitemap and robots.txt are well-configured, but WebMCP support is missing.

What an assistant meets at the door

Before an assistant can read, compare or buy, it has to get in. These rows are the door: whether the bot shield lets the main agents through, what robots.txt tells the search, training and user-triggered agents, and whether the home page has text without running JavaScript.

The door at mckesson.com
CheckResultWhat Ora saw
Not blocked by bot detectionPass, 2 of 2Site accessible to 6 AI agent user-agents
Agent crawler reachabilityPass, 2 of 2Reachable to all major AI crawlers - ChatGPT-User: reachable, ClaudeBot: reachable, Google-Extended: reachable, ora-agent: reachable, DeepSeekBot: reachable
robots.txt AI crawler policyPass, 2 of 2Training: 2/2. Search: 3/3 page/crawler pairs permitted. No applicable crawl or usage restriction found for 5 training and search crawlers (gptbot, claudebot, oai-searchbot, claude-searchbot).
robots.txt agent-user policyPass, 2 of 2No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://mckesson.com/. Declared policy only;
Content without JavaScriptPass, 3 of 32281 chars, semantic headings (1 H1 + 4 H2s + 6 H3s), 8.6% content ratio

What it can read, and what it can do

The reading layer is what an assistant takes away from the pages: a text file written for it, markdown on request, structured data about the company, a sitemap. The act layer is whether it can do anything through a published interface rather than by clicking through the site.

Reading mckesson.com
CheckResultWhat Ora saw
llms.txt existsFail, 0 of 1No llms.txt found at /llms.txt or /.well-known/llms.txt.
llms.txt formattingFail, 0 of 2No llms.txt found to evaluate quality
Markdown agent docsFail, 0 of 1Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md).
Bot-UA markdown servingFail, 0 of 1No probed bot User-Agent (GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended, ora-agent, DeepSeekBot) receives markdown when requesting HTML.
JSON-LD structured dataFail, 0 of 4No JSON-LD structured data found on homepage
Organization schema completenessFail, 0 of 2No JSON-LD found - Organization schema missing
Sitemap existsPass, 2 of 2Valid sitemap found at https://www.mckesson.com/sitemap.xml with 1009 entries
Metadata completenessPartial, 1 of 23/4 metadata signals present - missing: og:type
Page token budgetPass, 1 of 1All 1 measured page fit an agent context budget (largest ~1K tokens)
Acting through mckesson.com
CheckResultWhat Ora saw
MCP server / manifestDid not apply, 0 of 6No MCP server or manifest found
MCP well-known discoveryFail, 0 of 2No MCP server URL discovered
Public API with reachable endpointsDid not apply, 0 of 7No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated)
Public API/docs linked from homepageDid not apply, 0 of 3No public API or documentation page linked from homepage
OpenAPI spec publishedDid not apply, 0 of 7No OpenAPI/Swagger specification found
Developer portalDid not apply, 0 of 6No developer portal found
OAuth 2.0 supportPass, 5 of 5OpenID Connect discovery endpoint found at https://auth.mckesson.com
Scoped permissionsDid not apply, 0 of 5No declared OAuth scopes, security schemes, or scoped-permission documentation found
Multi-language SDK packagesDid not apply, 0 of 3No SDK packages found across language ecosystems
CLI tool availableDid not apply, 0 of 3No CLI tool found
WebMCP supportFail, 0 of 5No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 5 of 5 same-origin script bundle(s) for modelContext registrations)
Finding McKesson
CheckResultWhat Ora saw
Wikipedia / Wikidata entity presencePass, 4 of 4Wikipedia "McKesson" and Wikidata Q570473 both verified - domain confirmed on both sources
Brand name discoverabilityPass, 3 of 3mckesson.com appears at position #3 in a clean brand-name search for "McKesson" (1 total match)
Category share of voiceDid not apply, 0 of 6Category share of voice is in beta. It measures whether agents surface you for capability and use-case searches (not just your name).
Developer resource discoverabilityDid not apply, 0 of 3Agent struggled to find developer resources by name - only 1 result(s) out of 10. Not found in this search sample: API docs, OpenAPI spec, developer portal, auth docs, MCP server, SDK documentation

The six payment checks did not apply on this read: Ora did not read the site as a shop.

Three fixes to hand to the web team

Ora estimates how many points each open check would return. These are the largest on this read, in Ora's words where it gave them, so a leader can hand the list over without translating it.

  1. WebMCP support, worth about 9.3 points by Ora's estimate: No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 5 of 5 same-origin script bundle(s) for modelContext registrations).
  2. JSON-LD structured data, worth about 3.4 points by Ora's estimate: No JSON-LD structured data found on homepage.
  3. Agent instruction / when-to-use, worth about 2.6 points by Ora's estimate: No agent instruction file with when-to-use guidance found.

Our read

McKesson is the best-read health distributor in this series, and a C on a short denominator. Six AI agent user agents reach mckesson.com, robots.txt permits every training and search pair Ora checked, the home page gives 2,281 characters at an 8.6 percent text ratio under a proper heading tree, and the sitemap lists 1,009 pages, so the Access layer reads 16 of 39; there is no JSON-LD and no llms.txt, and the metadata lacks og:type. The act layer is thin by nature for a distributor, which is why the Usability layer has a maximum of 24 and the WebMCP estimate of 9.3 points means less than it looks; OpenID Connect discovery at auth.mckesson.com is the one surface Ora found, with no public API, no developer portal and no MCP server. The Discovery layer is 9 of 10, with Wikipedia and Wikidata confirmed. An Organization block is the fix with the most points a web team can ship in a day; the rest of this page is already in order.

Test your own site

Run the same scan on your own domain at ora.ai. The score, the layers and the fixes on this page come from its public result for mckesson.com; a scan of a public site takes a few minutes and needs no account.

Sources

  1. Ora report for mckesson.com (ora.ai/score/mckesson.com), read 9 Nov 2026. Vendor claim.

Last reviewed