---
title: "Middesk agent readiness score: 66/100 · Agentrail"
description: "Access is the strongest area, with a published OpenAPI specification and a homepage link to the public API or documentation, but the company is not listed in MCP registries and lacks a developer portal."
canonical: "https://www.agentrail.co/agent-readiness/middesk.com?h=917TDYXY55YH300H"
---

Full report

## See what each check found, and how to fix it.

Evidence, step-by-step fixes and your score over time, for your own site.

[Get started →](https://app.agentrail.co/login?utm%5Fsource=agentrail.co&utm%5Fmedium=website&utm%5Fcampaign=agent-readiness%2Fmiddesk.com&utm%5Fcontent=company-report)

Free to start. No card.

Usability

20 to fix

- MCP auth mechanismRecommendedHow to fix →
- MCP OAuth metadataRecommendedHow to fix →
- Agent onboarding frictionRecommendedHow to fix →
- Web Bot Auth directoryEmergingHow to fix →

Fixes unlock with the full report

Where the score comes from

59 of 90 points

How middesk.com scores on each of the four questions agents ask.

Discovery13/20

Access22/30

Usability24/40

Paymentsnot scored yet

Strongest

### Access

Content without JavaScript, Agent instruction / when-to-use, and 4 more are missing.

22/30

Most to gain

### Usability

MCP auth mechanism, MCP OAuth metadata, and 10 more are missing.

24/40

Most to gain

### Discovery

ARD discovery, Wikipedia / Wikidata entity presence, and 2 more are missing.

13/20

Not scored yet

### Payments ( bonus )

Counts when scoring opens.

—

Every check

139checks

- Passed**27**
- To fix**22**
- Not in the score**90**

49 checks count toward the score. The other 90 are tracked for later.

Discovery13 of 204 to fix4 passed

ARD discoveryRequired0 / 1

Wikipedia / Wikidata entity presenceRecommended0 / 4

Listed in MCP registriesRecommended0 / 3

NPM/PyPI SDK packageRecommended0 / 1

Developer resource discoverabilityRecommended4 / 4

Brand name discoverabilityRequired3 / 3

robots.txt AI crawler policyRequired1 / 1

Homepage not hidden from searchRecommended1 / 1

\+ 7 checks not in the score

AI Catalog discoveryEmergingNot counted

ARD entry validityRecommendedNot counted

ARD trust manifestEmergingNot counted

Agent platform configsEmergingNot counted

Agent Plugins manifestEmergingNot counted

Registry brandingEmergingNot counted

ChatGPT app listedRecommendedNot counted

Access22 of 303 to fix3 partly14 passed

Agent instruction / when-to-useRequired0 / 1

Developer portalRecommended0 / 5

Markdown content negotiation (acceptmarkdown.com)Recommended0 / 1

Content without JavaScriptRequired1.7 / 5

Metadata completenessRequired0.5 / 1

Organization schema completenessRecommended0.5 / 1

Sitemap existsRequired1 / 1

Not blocked by bot detectionRequired2 / 2

robots.txt agent-user policyRequired1 / 1

llms.txt existsRequired1 / 1

llms.txt formattingRecommended2 / 2

JSON-LD structured dataRequired2 / 2

Public API/docs linked from homepageRequired4 / 4

JSON-LD entity linking (sameAs)Recommended1 / 1

Trust anchor pagesRequired1 / 1

llms.txt links resolveRecommended2 / 2

Redirect hygieneRecommended1 / 1

Content behind authRecommended1 / 1

OpenAPI spec publishedRequired8 / 8

Agent crawler reachabilityRecommended1 / 1

\+ 20 checks not in the score

Agent discovery fileEmergingNot counted

Agent Skills index conformance (v0.2.0)EmergingNot counted

A2A / agent-cardEmergingNot counted

Listed on skills.shEmergingNot counted

pricing.md existsEmergingNot counted

NLWeb Schema FeedsEmergingNot counted

MCP well-known discoveryEmergingNot counted

HTTP Link headers (RFC 8288)EmergingNot counted

Markdown URL fallbackEmergingNot counted

Modular llms.txt per product areaEmergingNot counted

Pricing info accessibleRequiredNot counted

Skills.sh skill qualityEmergingNot counted

Markdown alternate linkEmergingNot counted

Markdown frontmatter metadataEmergingNot counted

Page token budgetRecommendedNot counted

Code fence validityEmergingNot counted

API catalog (RFC 9727)EmergingNot counted

Markdown agent docsEmergingNot counted

Bot-UA markdown servingEmergingNot counted

Content starts near the topEmergingNot counted

Usability24 of 408 to fix4 partly9 passed

MCP OAuth metadataRecommended0 / 2

Agent onboarding frictionRecommended0 / 2

WebMCP supportRequired0 / 8

Rate limit response headersRecommended0 / 2

Idempotency-Key supportRecommended0 / 3

REST async-job patternRecommended0 / 2

CLI tool availableRecommended0 / 3

Sandbox / test environmentRecommended0 / 2

MCP auth mechanismRecommended1 / 2

MCP server / manifestRequired8.3 / 10

REST versioning / deprecation policyRecommended2 / 3

Agent-friendly 404sRecommended1 / 2

Public API with reachable endpointsRequired8 / 8

OAuth 2.0 supportRequired5 / 5

Scoped permissionsRecommended5 / 5

MCP PKCE S256 supportRecommended2 / 2

OAuth Protected Resource metadata (RFC 9728)Required2 / 2

JSON error responsesRequired3 / 3

REST typed error modelRecommended3 / 3

API schema complexity analysisRecommended2 / 2

Function calling compatibilityRecommended2 / 2

\+ 58 checks not in the score

MCP tool descriptionsRecommendedNot counted

MCP parameter schemasRecommendedNot counted

MCP server identityRecommendedNot counted

MCP tool listingRecommendedNot counted

MCP tool namingRecommendedNot counted

Web Bot Auth directoryEmergingNot counted

auth.md existsEmergingNot counted

auth.md structureEmergingNot counted

auth.md walkthrough simulationEmergingNot counted

Agent auth discovery metadataEmergingNot counted

Agent auth WWW-Authenticate hintEmergingNot counted

agent\_auth endpoints reachableEmergingNot counted

MCP error handlingRecommendedNot counted

MCP modern transportRecommendedNot counted

REST pagination patternRecommendedNot counted

NLWeb /ask endpointEmergingNot counted

NLWeb streaming supportEmergingNot counted

REST response schema coverageRecommendedNot counted

MCP tool annotationsRecommendedNot counted

MCP server-card.jsonEmergingNot counted

Product + docs MCP coverageRecommendedNot counted

MCP resources exposedRecommendedNot counted

GraphQL typed error modelRecommendedNot counted

GraphQL versioning / deprecation policyRecommendedNot counted

GraphQL pagination patternRecommendedNot counted

GraphQL async-job patternRecommendedNot counted

GraphQL schema description coverageRecommendedNot counted

Accessible document structureEmergingNot counted

Native interactive controlsEmergingNot counted

Accessible names on controlsEmergingNot counted

Form control labelingEmergingNot counted

Accessibility-tree injection safety (bonus)EmergingNot counted

MCP Apps supportRecommendedNot counted

A2UI / generative UI supportEmergingNot counted

MCP Apps UI qualityRecommendedNot counted

MCP App view reachableRecommendedNot counted

MCP App view CSPRecommendedNot counted

MCP resource qualityRecommendedNot counted

MCP server instructionsRecommendedNot counted

MCP tools are distinguishableRecommendedNot counted

MCP tool output schemasRecommendedNot counted

MCP Apps checkout viewEmergingNot counted

WebMCP schema validityRecommendedNot counted

WebMCP schema detailRecommendedNot counted

WebMCP real toolsRecommendedNot counted

WebMCP entry pointRecommendedNot counted

WebMCP tool namesRecommendedNot counted

WebMCP read-only hintsRecommendedNot counted

WebMCP honest hintsRecommendedNot counted

WebMCP untrusted content hintRecommendedNot counted

WebMCP consequential hintRecommendedNot counted

WebMCP coverageRecommendedNot counted

Personal Agent Protocol discovery fileEmergingNot counted

PAP issuer bindingEmergingNot counted

PAP sign-in and extension configEmergingNot counted

PAP API and agent entriesEmergingNot counted

PAP endpoints reject unauthenticated agentsEmergingNot counted

PAP agrees with ARD and auth.mdEmergingNot counted

PaymentsNot scored yet

\+ 5 checks not in the score

MPP payment protocolRequiredNot counted

x402 payment protocolRequiredNot counted

UCP - Universal Commerce ProtocolRequiredNot counted

ACP - Agentic Commerce ProtocolRequiredNot counted

Agent wallet checkoutRequiredNot counted
