Is amung.us agent ready?

amung.us is not yet agent ready: it scores 26/100 (grade F) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Discovery (0), Structured Data (20), Agent Protocols (30), Content Quality (34), Bot Accessibility (48).

26/ 100
Grade: F

Last checked

Scored Oct 14, 2026 · Rubric v3.0

Changed since last check

No change in score since the previous check (2026-09-16)

Category scores

Technical
71
Agent Auth
0
Agent Discovery
0
Agent Protocols
30
Content Quality
34
Structured Data
20
Bot Accessibility
48

Agent protocol panel

  • A2A agent cardNot found
  • OAuth discoveryNot measured
  • MCP discoveryNot found
  • llms.txt validityNot measured

Check results

Bot Accessibility

  • ✓No error status codespass
  • ~Response timepartial
  • ✗XML sitemap existsfail
  • ✓AI agent accesspass
  • ✓Edge treatment of agent user-agentstracked, not scoredpass
  • ✗robots.txt existsfail
  • ✗Content negotiation (Markdown)fail
  • —Declared AI usage preferencestracked, not scoredskip

Structured Data

  • ✓OpenGraph meta tagspass
  • ~Semantic HTML elementspartial
  • ✗Appropriate Schema.org typefail
  • —JSON-LD validskip
  • ✗Heading hierarchyfail
  • ✗Schema.org JSON-LD presentfail
  • ✗Schema.org completenessfail

Content Quality

  • ✗FAQ contentfail
  • ✗Answer-first contentfail
  • ✓Content lengthpass
  • ~Token efficiency (HTML-to-text ratio)partial
  • ✗Freshness signalsfail
  • ✗Author attributionfail
  • ~Citation readinesspartial
  • ✓Lists and tables for structured infopass

Agent Discovery

  • —llms.txt follows specskip
  • ✗llms.txt existsfail
  • —MCP server cardtracked, not scoredskip
  • ✗Markdown alternate linksfail
  • ✗/.well-known/agent-card.jsonfail
  • —llms.txt links resolveskip

Agent Protocols

  • ✗Discoverable API endpointsfail
  • ✗MCP endpointfail
  • ✗Action schemasfail
  • —/.well-known/ucpskip
  • —Structured formsskip
  • —WebMCP imperative APItracked, not scoredskip
  • —WebMCP declarative APItracked, not scoredskip
  • ✓Reachable as Google-Agentpass
  • ✓Reachable as ChatGPT-Userpass
  • ✓Reachable as Perplexity-Userpass

Agent Auth

  • —MCP authorization (401 challenge → protected resource metadata)skip
  • —PKCE S256 supportskip
  • ✗Public API surfacefail
  • —Client ID Metadata Documents (bonus)skip
  • —OpenAPI specificationskip
  • —Agent/bot auth documentationskip
  • —OAuth discovery chain (RFC 9728 → RFC 8414)skip
  • —Developer portalskip
  • —Scoped API permissionsskip
  • —API catalog (RFC 9727)skip
  • —Agent operator signing directorytracked, not scoredskip

Technical

  • ✓HTTPSpass
  • ✓UTF-8 charsetpass
  • ✗Canonical URLsfail
  • ✓Mobile viewportpass
  • ✓Content accessible without JSpass
  • ~Security headerspartial

Score history

  • 26/100 · rubric v3.0
  • 26/100 · rubric v3.0
  • 26/100 · rubric v3.0
  • 39/100 · rubric v2.0
  • 39/100 · rubric v2.0
  • 39/100 · rubric v2.0
  • 39/100 · rubric v2.0

Related websites

Is your own site agent ready?

Check your own site →

Re-audit amung.us