New · Self-serve audits are live — real Claude Code & Cursor runs against your MCP server, SDK, or CLI →
F0/100

Static pre-check · Fri, 07 Aug 2026 06:57:14 GMT

things.app

0 pass · 0 warn · 1 fail · 41 n/a
Discovery
n/a
Accessibility
0/100
Usability
n/a
Payments
n/a

Discovery not applicable — excluded from the score

  • API reference linked from the homepagedetailsN/A

    target did not respond — nothing downstream could be observed

  • Brand findable in agent searchdetailsN/A

    target did not respond — nothing downstream could be observed

  • Canonical URL declareddetailsN/A

    target did not respond — nothing downstream could be observed

  • Documentation linked from the homepagedetailsN/A

    target did not respond — nothing downstream could be observed

  • Homepage has a meta descriptiondetailsN/A

    target did not respond — nothing downstream could be observed

  • Homepage has a descriptive titledetailsN/A

    target did not respond — nothing downstream could be observed

  • Listed in an MCP registrydetailsN/A

    target did not respond — nothing downstream could be observed

  • Open Graph tags presentdetailsN/A

    target did not respond — nothing downstream could be observed

  • robots.txt allows agent crawlersdetailsN/A

    target did not respond — nothing downstream could be observed

  • robots.txt existsdetailsN/A

    target did not respond — nothing downstream could be observed

  • robots.txt points at the sitemapdetailsN/A

    target did not respond — nothing downstream could be observed

  • sitemap.xml exists and parsesdetailsN/A

    target did not respond — nothing downstream could be observed

Accessibility 0/100

  • Homepage responds to an agent requestdetailsFAIL

    agent request failed: ConnectError: [Errno 8] nodename nor servname provided, or not known

    Fix: The homepage must answer a plain HTTPS GET. Check DNS, TLS and any WAF rule that drops non-browser clients.

  • Docs are readable without JavaScriptdetailsN/A

    target did not respond — nothing downstream could be observed

  • Served over HTTPSdetailsN/A

    target did not respond — nothing downstream could be observed

  • Structured data (JSON-LD) on the homepagedetailsN/A

    target did not respond — nothing downstream could be observed

  • llms-full.txt is publisheddetailsN/A

    target did not respond — nothing downstream could be observed

  • llms.txt is publisheddetailsN/A

    target did not respond — nothing downstream could be observed

  • Links in llms.txt resolvedetailsN/A

    target did not respond — nothing downstream could be observed

  • llms.txt is structured markdowndetailsN/A

    target did not respond — nothing downstream could be observed

  • Serves markdown when asked for itdetailsN/A

    target did not respond — nothing downstream could be observed

  • Same response for agents and browsersdetailsN/A

    target did not respond — nothing downstream could be observed

  • Homepage has readable text without JavaScriptdetailsN/A

    target did not respond — nothing downstream could be observed

  • Content-to-markup ratio is reasonabledetailsN/A

    target did not respond — nothing downstream could be observed

  • No long redirect chain on the homepagedetailsN/A

    target did not respond — nothing downstream could be observed

Usability not applicable — excluded from the score

  • agents.md is publisheddetailsN/A

    target did not respond — nothing downstream could be observed

  • The /api root behaves predictablydetailsN/A

    target did not respond — nothing downstream could be observed

  • A documentation endpoint respondsdetailsN/A

    target did not respond — nothing downstream could be observed

  • Errors are machine-readabledetailsN/A

    target did not respond — nothing downstream could be observed

  • MCP server completes the initialize handshakedetailsN/A

    target did not respond — nothing downstream could be observed

  • MCP tool parameters are typed and describeddetailsN/A

    target did not respond — nothing downstream could be observed

  • Every MCP tool has a descriptiondetailsN/A

    target did not respond — nothing downstream could be observed

  • MCP server lists toolsdetailsN/A

    target did not respond — nothing downstream could be observed

  • OpenAPI declares its auth schemedetailsN/A

    target did not respond — nothing downstream could be observed

  • OpenAPI operations are describeddetailsN/A

    target did not respond — nothing downstream could be observed

  • OpenAPI document publisheddetailsN/A

    target did not respond — nothing downstream could be observed

  • OpenAPI documents error responsesdetailsN/A

    target did not respond — nothing downstream could be observed

  • OpenAPI document is structurally validdetailsN/A

    target did not respond — nothing downstream could be observed

  • .well-known/mcp.json advertises an MCP serverdetailsN/A

    target did not respond — nothing downstream could be observed

Payments not applicable — excluded from the score

  • Serves a 402 payment challengedetailsN/A

    target did not respond — nothing downstream could be observed

  • Declares AP2 / ACP supportdetailsN/A

    target did not respond — nothing downstream could be observed

  • Publishes x402 payment metadatadetailsN/A

    target did not respond — nothing downstream could be observed

Badge

Shows the current scan score and grade for this domain, straight from the latest static pre-check.

agent readiness badge for things.app
[![agent ready](/api/badge/things.app)](/score/things.app)
<a href="/score/things.app"><img src="/api/badge/things.app" alt="agent readiness score" /></a>

The target did not respond, so nothing about its agent-readiness could be observed. This is a scan failure, not a grade of F earned on merit.