HonestClaw · What is Agent Readiness?
Limited. Agents will struggle to discover or use this site without human help.
HonestClaw measured how well withjoy.com's site and APIs work for AI agents — across 9 dimensions and 45 automated checks. Score: 25/100 (Limited).
Scanned Aug 28, 2026, 12:47 UTC · scanner v1.48.0 · 39 of 45 checks conclusive.
All 8 scored areas have measured gaps. Identity & safeguards is furthest along; Interfaces & data has the largest measured point gap.
59 additional observations provide context and do not affect the score.
Reachable entry points
Could not conclusively check for an API Catalog (endpoint unreachable, rate-limited, or behind auth). Blocked by robots.txt for a generic compliant agent (Disallow: /).
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No DNS-AID index found at _index._agents.withjoy.com.
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
An agent-relevant subdomain is live (dev.withjoy.com).
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
No RFC 8288 Link headers found on any probed response.
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Could not conclusively check /.well-known/ descriptors (unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
https://withjoy.com/blog/sitemap.xml is a valid sitemap with lastmod and real (non-homepage) URLs.
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Root and www converge on withjoy.com, with a matching canonical tag.
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Equivalent readable representations
No markdown twin found alongside probed docs HTML surfaces.
These are recorded points before the total is normalized to 100.
Only representations the site offers; all sites can satisfy readable-content outcome with HTML
Headers, routes and frontmatter support one readable representation. Plain HTML must be able to receive full content-access credit.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No reachable candidate HTML page declared a text/markdown alternate.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Only representations the site offers; all sites can satisfy readable-content outcome with HTML
Headers, routes and frontmatter support one readable representation. Plain HTML must be able to receive full content-access credit.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
No direct .md or /index.md representation was found for reachable candidate pages.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Only representations the site offers; all sites can satisfy readable-content outcome with HTML
Headers, routes and frontmatter support one readable representation. Plain HTML must be able to receive full content-access credit.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
No reachable candidate page served Markdown to the scanner agent without an Accept header.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Only representations the site offers; all sites can satisfy readable-content outcome with HTML
Headers, routes and frontmatter support one readable representation. Plain HTML must be able to receive full content-access credit.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
No reachable candidate page negotiated from HTML to Markdown.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Only representations the site offers; all sites can satisfy readable-content outcome with HTML
Headers, routes and frontmatter support one readable representation. Plain HTML must be able to receive full content-access credit.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
No readable Markdown representation began with YAML frontmatter.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Only representations the site offers; all sites can satisfy readable-content outcome with HTML
Headers, routes and frontmatter support one readable representation. Plain HTML must be able to receive full content-access credit.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Content available to the tested client
Moderate-to-strong main content (69% of visible text) is extractable from raw HTML on the homepage.
These are recorded points before the total is normalized to 100.
Public pages; distinguish HTTP and browser clients
Critical content available in the response is a direct prerequisite for the tested client. An extraction ratio alone does not prove that the needed facts were captured.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Retrieval cost
No crawl-cost signals found (no sitemap URL inventory or Crawl-delay directive).
Useful context, outside the readiness score. Adoption, payment support and retrieval cost are not readiness quality by themselves.
Measured retrieval path
Tokens, bytes and elapsed time explain retrieval cost and tradeoffs. They are context and do not affect the readiness score.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Reachable critical content
Static same-site links led to substantive HTML content two crawl hops from the homepage.
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Sites with linked public content
Bounded path traversal can explain missing content. Absolute clicks from the homepage is not a validated universal quality scale.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Observed client access
All 5 agent crawler probes passed. ChatGPT-User=200, ClaudeBot=200, Google-Extended=200, PerplexityBot=200, DeepSeekBot=200
Additional observation. It adds no points and its absence does not lower the score.
Up to three first-party pages; ChatGPT-User, Claude-User and Perplexity-User token markers on an explicitly identified HonestClaw client
One combined access contribution measures substantive initial content in completed identified HonestClaw HTTP probes. Refusals and incomplete observations remain unknown. This does not establish access from vendor infrastructure.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
All 5 bot-detection probes passed. ChatGPT-User=clear, ClaudeBot=clear, Google-Extended=clear, PerplexityBot=clear, DeepSeekBot=clear
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
The same named public HTTP sample and network vantage as the access check
Reuses the scored public HTTP sample to explain denials, challenges and degraded content. The same responses earn no second contribution.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Clear and consistent publisher policy
robots.txt is readable but declares no RSL License directive.
These are recorded points before the total is normalized to 100.
Publisher-declared policy; no obligation to permit training, indexing or licensing
Published licensing, indexing and training preferences remain inspectable without separate readiness points. User-directed policy legibility is measured once; observed public HTTP access is separate.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
robots.txt is readable but declares no Content-Signal line.
These are recorded points before the total is normalized to 100.
Publisher-declared policy; no obligation to permit training, indexing or licensing
Published licensing, indexing and training preferences remain inspectable without separate readiness points. User-directed policy legibility is measured once; observed public HTTP access is separate.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Could not conclusively check for a TDMRep policy (unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
Publisher-declared policy; no obligation to permit training, indexing or licensing
Published licensing, indexing and training preferences remain inspectable without separate readiness points. User-directed policy legibility is measured once; observed public HTTP access is separate.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Could not conclusively check for an ai.txt file (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
Publisher-declared policy; no obligation to permit training, indexing or licensing
Published licensing, indexing and training preferences remain inspectable without separate readiness points. User-directed policy legibility is measured once; observed public HTTP access is separate.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
robots.txt at https://withjoy.com/robots.txt declares a sitemap. Declared sitemap https://withjoy.com/sitemaps/sitemap.xml resolves as valid XML.
These are recorded points before the total is normalized to 100.
Published policy for the relevant use: indexing, training or user retrieval
Different policy syntaxes and business permissions are not independent readiness capabilities. Blocking training should not imply that an agent cannot use a public API.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
robots.txt declares explicit rules for 7 AI bot(s): gptbot, oai-searchbot, chatgpt-user, claudebot, perplexitybot, perplexity-user, google-extended.
These are recorded points before the total is normalized to 100.
ChatGPT-User, Claude-User and Perplexity-User access declarations
A small legibility contribution for explicit user-directed access rules, including wildcard defaults. Permission and denial earn equal legibility; training-only groups add no points.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Usable API reference and examples
API reference documentation lacks depth or was not found.
These are recorded points before the total is normalized to 100.
A documented API or tool interface
Reference depth and valid fenced examples contribute to the same documentation outcome. Parsing an example is weaker than executing it successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No fenced code blocks were found across 1 readable Markdown document(s).
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
A documented API or tool interface
Reference depth and valid fenced examples contribute to the same documentation outcome. Parsing an example is weaker than executing it successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Usable documentation entry and references
Could not conclusively check for an llms-full.txt file (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
Public documentation; llms files optional
An index, full text and modular files offer different routes to documentation. Useful content and working references matter more than the number of formats.
Current guidance · 2026-09-29. Recorded scores are unchanged.
A curated llms.txt index is published at https://withjoy.com/llms.txt: 1256 links across 6 sections.
These are recorded points before the total is normalized to 100.
Public documentation; llms files optional
An index, full text and modular files offer different routes to documentation. Useful content and working references matter more than the number of formats.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No scoped llms.txt was found.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Public documentation; llms files optional
An index, full text and modular files offer different routes to documentation. Useful content and working references matter more than the number of formats.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
5/5 sampled on-domain llms.txt links resolved to real, non-shell content.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Public documentation; llms files optional
An index, full text and modular files offer different routes to documentation. Useful content and working references matter more than the number of formats.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Machine-readable facts
No machine-readable pricing endpoint found (HTML pricing pages do not qualify).
These are recorded points before the total is normalized to 100.
Facts relevant to the product; pricing only when there is a price to disclose
Structured facts can help agents interpret a page. Markup volume and the number of schema types alone do not establish accuracy, consistency or task success.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Observed 1 JSON-LD script(s); 1 parsed as JSON-LD objects.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Facts relevant to the product; pricing only when there is a price to disclose
Structured facts can help agents interpret a page. Markup volume and the number of schema types alone do not establish accuracy, consistency or task success.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Observed 6 resolvable identifier(s) and 4 verified entity link(s).
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Facts relevant to the product; pricing only when there is a price to disclose
Structured facts can help agents interpret a page. Markup volume and the number of schema types alone do not establish accuracy, consistency or task success.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Observed 3 Schema.org type(s): organization, webpage, website; 3 meaningfully populated.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Facts relevant to the product; pricing only when there is a price to disclose
Structured facts can help agents interpret a page. Markup volume and the number of schema types alone do not establish accuracy, consistency or task success.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Document freshness evidence
Freshness signals present: Last-Modified header, ETag header.
These are recorded points before the total is normalized to 100.
Resources whose currency can be assessed
A timestamp or ETag supports freshness provenance; it does not by itself prove factual accuracy or current behavior.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Usable agent guidance
No v0.2.0 index could be read.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Only a declared agent-guide surface
Alternative guide files may help agents locate instructions; file presence is supporting evidence and must not be required in every format.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No usable Agent Skills discovery index was found.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Only a declared agent-guide surface
Alternative guide files may help agents locate instructions; file presence is supporting evidence and must not be required in every format.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
The guidance is structured, but lacks both specific when-to-use and invocation guidance.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Only a declared agent-guide surface
Alternative guide files may help agents locate instructions; file presence is supporting evidence and must not be required in every format.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Complete and usable operation contracts
No published structured-data contract found (no typed spec response schemas).
These are recorded points before the total is normalized to 100.
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No data export or bulk API documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
The shared spec probe could not read a valid OpenAPI/Swagger artifact.
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
The shared spec probe could not read a valid OpenAPI/Swagger artifact.
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
The shared spec probe could not read a valid OpenAPI/Swagger artifact.
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
The shared spec probe could not read a valid OpenAPI/Swagger artifact.
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Usable supported interface
No API endpoint found at common paths (only HTML pages or 404s).
These are recorded points before the total is normalized to 100.
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No OpenAPI/Swagger specification found.
These are recorded points before the total is normalized to 100.
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Could not conclusively discover or check first-party MCP support documentation and likely endpoints.
Unverified points are excluded from the score denominator and reduce observed coverage.
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No SDK or client library documentation found.
These are recorded points before the total is normalized to 100.
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
A GraphQL transport surface is advertised at https://withjoy.com/graphql (GraphiQL/Playground or Apollo markers).
These are recorded points before the total is normalized to 100.
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Emerging interface declarations
Could not conclusively check for an MCP Server Card (endpoints unreachable, rate-limited, or behind auth). Blocked by robots.txt for a generic compliant agent (Disallow: /).
These are recorded points before the total is normalized to 100.
Only a positively identified matching protocol
Versioned interface declarations are observable signals. Broad adoption and cross-client utility are not established by declaration presence.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Could not conclusively check for an A2A Agent Card (endpoints unreachable, rate-limited, or behind auth). Blocked by robots.txt for a generic compliant agent (Disallow: /).
These are recorded points before the total is normalized to 100.
Only a positively identified matching protocol
Versioned interface declarations are observable signals. Broad adoption and cross-client utility are not established by declaration presence.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
WebMCP browser probing is not yet available in this scanner release.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Only a positively identified matching protocol
Versioned interface declarations are observable signals. Broad adoption and cross-client utility are not established by declaration presence.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
MCP discovery evidence
Could not conclusively check for an MCP descriptor (locations unreachable, rate-limited, or behind auth). Blocked by robots.txt for a generic compliant agent (Disallow: /).
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
MCP surface
An MCP descriptor helps clients locate a service. This additional observation does not earn separate points for evidence already represented by the scored MCP check.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Usable MCP tools and resources
MCP tool listing could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected MCP server and advertised tool/resource capability
Live listings and contracts help agents discover tools and understand their inputs. These related observations remain unscored pending calibration of their contribution to successful tool use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP tool naming could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected MCP server and advertised tool/resource capability
Live listings and contracts help agents discover tools and understand their inputs. These related observations remain unscored pending calibration of their contribution to successful tool use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP tool descriptions could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected MCP server and advertised tool/resource capability
Live listings and contracts help agents discover tools and understand their inputs. These related observations remain unscored pending calibration of their contribution to successful tool use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP tool annotations could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected MCP server and advertised tool/resource capability
Live listings and contracts help agents discover tools and understand their inputs. These related observations remain unscored pending calibration of their contribution to successful tool use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP parameter schemas could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected MCP server and advertised tool/resource capability
Live listings and contracts help agents discover tools and understand their inputs. These related observations remain unscored pending calibration of their contribution to successful tool use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP resource listing could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected MCP server and advertised tool/resource capability
Live listings and contracts help agents discover tools and understand their inputs. These related observations remain unscored pending calibration of their contribution to successful tool use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP resource quality could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected MCP server and advertised tool/resource capability
Live listings and contracts help agents discover tools and understand their inputs. These related observations remain unscored pending calibration of their contribution to successful tool use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected MCP server and advertised tool/resource capability
Live listings and contracts help agents discover tools and understand their inputs. These related observations remain unscored pending calibration of their contribution to successful tool use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Compatible MCP transport
MCP transport modernity could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Detected MCP transport and negotiated version
A compatible negotiated protocol version helps clients and servers communicate. An older supported transport can still be usable.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP application UI
MCP Apps could not be checked because endpoint discovery was incomplete. This metadata-only check did not call tools or read app resources.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected application UI surface
An embedded interface can support interactive workflows. Many tools work without a user interface, so its absence is not a general readiness failure.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP Apps could not be checked because endpoint discovery was incomplete. This metadata-only check did not call tools or read app resources.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected application UI surface
An embedded interface can support interactive workflows. Many tools work without a user interface, so its absence is not a general readiness failure.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP Apps could not be checked because endpoint discovery was incomplete. This metadata-only check did not call tools or read app resources.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected application UI surface
An embedded interface can support interactive workflows. Many tools work without a user interface, so its absence is not a general readiness failure.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Payment capabilities
Could not conclusively inspect published API specifications for Agentic Commerce Protocol checkout support.
Useful context, outside the readiness score. Adoption, payment support and retrieval cost are not readiness quality by themselves.
Payment-enabled business model
Payment support describes what the business offers. It must not make a research publication or free public service appear less ready.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Could not conclusively inspect published API specifications for ACP delegated-payment support.
Useful context, outside the readiness score. Adoption, payment support and retrieval cost are not readiness quality by themselves.
Payment-enabled business model
Payment support describes what the business offers. It must not make a research publication or free public service appear less ready.
Current guidance · 2026-09-29. Recorded scores are unchanged.
The UCP discovery location could not be checked conclusively.
Useful context, outside the readiness score. Adoption, payment support and retrieval cost are not readiness quality by themselves.
Payment-enabled business model
Payment support describes what the business offers. It must not make a research publication or free public service appear less ready.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Could not conclusively inspect the UCP profile and published API specifications for AP2.
Useful context, outside the readiness score. Adoption, payment support and retrieval cost are not readiness quality by themselves.
Payment-enabled business model
Payment support describes what the business offers. It must not make a research publication or free public service appear less ready.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No machine-payment signal observed (no HTTP 402, no payment-required response header, and no /.well-known/x402.json manifest). Payment support cannot be ruled out from an unauthenticated probe.
Useful context, outside the readiness score. Adoption, payment support and retrieval cost are not readiness quality by themselves.
Payment-enabled business model
Payment support describes what the business offers. It must not make a research publication or free public service appear less ready.
Current guidance · 2026-09-29. Recorded scores are unchanged.
NLWeb support
An NLWeb /ask operation could not be checked conclusively across the shared OpenAPI discovery surface.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected NLWeb service
Useful protocol observations; optional implementation is not universal readiness.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
NLWeb streaming support could not be checked conclusively across the shared OpenAPI discovery surface.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected NLWeb service
Useful protocol observations; optional implementation is not universal readiness.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
No valid HTTPS SchemaMap directive was found in robots.txt.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected NLWeb service
Useful protocol observations; optional implementation is not universal readiness.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Usable least-privilege authentication
No programmatic authentication documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Protected operations; anonymous access is valid when intended
Discovery, documentation and credential lifecycle jointly support a usable authorization flow. A public read-only service need not require OAuth.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No authentication documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Protected operations; anonymous access is valid when intended
Discovery, documentation and credential lifecycle jointly support a usable authorization flow. A public read-only service need not require OAuth.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No credential management documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Protected operations; anonymous access is valid when intended
Discovery, documentation and credential lifecycle jointly support a usable authorization flow. A public read-only service need not require OAuth.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Agent-native auth discovery: a valid RFC 9728 PRM (via challenge) or a PRM plus a valid AS/OIDC descriptor.
These are recorded points before the total is normalized to 100.
Protected operations; anonymous access is valid when intended
Discovery, documentation and credential lifecycle jointly support a usable authorization flow. A public read-only service need not require OAuth.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Safe integration environment
No sandbox or test environment documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Operations whose side effects or onboarding require a safe test environment
A sandbox helps validate consequential integrations; it is not necessary for every public content site or read-only API.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
MCP authorization evidence
MCP authentication mechanism could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Protected HTTP MCP; OAuth/PKCE only for applicable flow
Authentication metadata and challenges help clients understand how to obtain access. Observing a declaration does not prove that credentials can be issued or used successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP OAuth metadata could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Protected HTTP MCP; OAuth/PKCE only for applicable flow
Authentication metadata and challenges help clients understand how to obtain access. Observing a declaration does not prove that credentials can be issued or used successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP PKCE support could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
Protected HTTP MCP; OAuth/PKCE only for applicable flow
Authentication metadata and challenges help clients understand how to obtain access. Observing a declaration does not prove that credentials can be issued or used successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Emerging authentication guidance
The root auth.md document does not satisfy the structured criteria.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected emerging authentication scheme
An auth.md file is one possible guide. Reachable metadata and bounded simulation are not proof that credentials can be issued successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
The root auth.md document does not satisfy the exists criteria.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected emerging authentication scheme
An auth.md file is one possible guide. Reachable metadata and bounded simulation are not proof that credentials can be issued successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
The root auth.md document does not satisfy the walkthrough criteria.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected emerging authentication scheme
An auth.md file is one possible guide. Reachable metadata and bounded simulation are not proof that credentials can be issued successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No conforming public Agent Auth discovery document was found.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected emerging authentication scheme
An auth.md file is one possible guide. Reachable metadata and bounded simulation are not proof that credentials can be issued successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No conforming public Agent Auth discovery document was found.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected emerging authentication scheme
An auth.md file is one possible guide. Reachable metadata and bounded simulation are not proof that credentials can be issued successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No observed API response advertised an AgentAuth discovery challenge.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected emerging authentication scheme
An auth.md file is one possible guide. Reachable metadata and bounded simulation are not proof that credentials can be issued successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Actionable limits
No rate limit documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
An interface with quotas or throttling
Published limits and response headers help clients pace requests and recover from throttling. They describe related aspects of the same service constraint.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No confirmed live API response was available for rate-limit header inspection.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
An interface with quotas or throttling
Published limits and response headers help clients pace requests and recover from throttling. They describe related aspects of the same service constraint.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Change and compatibility information
No versioning signal found (no spec info.version, version header, /vN API surface, or versioning docs).
These are recorded points before the total is normalized to 100.
Maintained interface or evolving product
Version identifiers and change records help clients manage compatibility as an interface evolves.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No changelog or release notes found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Maintained interface or evolving product
Version identifiers and change records help clients manage compatibility as an interface evolves.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Observable outcomes and recovery
No webhook or event documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No error documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No retry or idempotency documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Could not conclusively check for health or status endpoints (unreachable, rate-limited, or behind auth). Blocked by robots.txt for a generic compliant agent (Disallow: /).
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
The missing path returned HTTP 404 with a readable explanation, but no agent-followable recovery link.
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
MCP error handling could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Attributable identity and consistent claims
Could not conclusively check for security.txt (unreachable or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
Public company/service identity; MCP identity only for MCP
These establish provenance, disclosure routes and consistency. They cannot certify prompt-injection resistance or safe transactions.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
At least one legal policy page is discoverable.
These are recorded points before the total is normalized to 100.
Public company/service identity; MCP identity only for MCP
These establish provenance, disclosure routes and consistency. They cannot certify prompt-injection resistance or safe transactions.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Homepage exposes three org-identity signal types (legal_name, social, support_email).
These are recorded points before the total is normalized to 100.
Public company/service identity; MCP identity only for MCP
These establish provenance, disclosure routes and consistency. They cannot certify prompt-injection resistance or safe transactions.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
Homepage metadata (canonical, Open Graph, schema) is present and consistent.
These are recorded points before the total is normalized to 100.
Public company/service identity; MCP identity only for MCP
These establish provenance, disclosure routes and consistency. They cannot certify prompt-injection resistance or safe transactions.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
MCP server identity could not be checked because endpoint discovery was incomplete. Live MCP probe: 79 ms, 0 protocol request(s).
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
Public company/service identity; MCP identity only for MCP
These establish provenance, disclosure routes and consistency. They cannot certify prompt-injection resistance or safe transactions.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
Application isolation declarations
MCP Apps could not be checked because endpoint discovery was incomplete. This metadata-only check did not call tools or read app resources.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected MCP application UI
Declared origins and CSP are relevant safeguards for an embedded UI, but declarations alone do not establish effective isolation.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check
MCP Apps could not be checked because endpoint discovery was incomplete. This metadata-only check did not call tools or read app resources.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Detected MCP application UI
Declared origins and CSP are relevant safeguards for an embedded UI, but declarations alone do not establish effective isolation.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-09-29. Recorded scores are unchanged.
No public evidence URL recorded for this check