agenticweb.wiki

scrapfly.io agentic web readiness

A+ Manifest validity: 83% (5/6 valid, 4 errors, 12 warnings) · Surface score 75 (coverage 50 + breadth 15 + conformance 10). 9 standards observed across 5 of 9 steps; 6 manifests present (+ security.txt), 4 errors, 12 warnings. Checked 2026-10-25 22:05:23 UTC. This grades the agent-facing files published at scrapfly.io, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/scrapfly.io.svg) · JSON · Markdown · Re-check now

Coverage by step

01 DiscoverRFC 972702 Identifynothing observed03 PermitAI Crawler User-Agent Tokens in robots.txt, OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)04 Readllms.txt, Markdown for Agents05 ActAgent Skills06 CoordinateA2A07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json
absent HTTP 404
AI Catalog well-known file
/.well-known/ai-catalog.json
absent HTTP 404
MCP Server Cards (SEP-2127)
/.well-known/mcp/server-card.json
errors
  • $schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json)
  • name missing
  • version missing
  • description missing
  • Content-Type is application/json; SEP-2127 says serve application/mcp-server-card+json
  • pre-final card shape (url/transport/tools); the final SEP-2127 card uses name, version, description and remotes[]
  • remotes missing: a card with no remotes gives clients nothing to connect to
  • no Access-Control-Allow-Origin: * (required for browser clients)
  • no Cache-Control max-age; clients should be able to cache the card
  • no ETag
  • legacy /.well-known/mcp.json is still live and may shadow /.well-known/mcp/server-card.json in older scanners
View valid /mcp/server-card template for scrapfly.io
{
  "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
  "name": "io.scrapfly/scrapfly",
  "title": "Scrapfly",
  "version": "1.0.0",
  "description": "Scrapfly and what it offers to agents",
  "websiteUrl": "https://scrapfly.io/",
  "icons": [
    {
      "src": "https://scrapfly.io/icon.png",
      "mimeType": "image/png",
      "sizes": [
        "180x180"
      ]
    }
  ],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://scrapfly.io/mcp",
      "supportedProtocolVersions": [
        "2025-11-25",
        "2025-06-18",
        "2025-03-26"
      ]
    }
  ]
}
Agent2Agent Protocol
/.well-known/agent-card.json
valid
  • supportedInterfaces missing; A2A 1.0 cards declare interfaces there (url, protocolBinding, protocolVersion) and the top-level url is the 0.3 shape
  • protocolVersion is "0.3" (pre-1.0 legacy shape; A2A 1.0 uses protocolVersion "1.0" and supportedInterfaces[])
llms.txt
/llms.txt
valid
  • no Markdown links: list the pages an agent should read
AGENTS.md
/AGENTS.md
absent HTTP 404
Agent Skills
/.well-known/agent-skills/index.json
valid
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
/.well-known/api-catalog
valid
AI Crawler User-Agent Tokens in robots.txt
/robots.txt
valid
  • no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
  • no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
security.txt (RFC 9116)
/.well-known/security.txt
valid
auth.md
/auth.md
absent HTTP 404
Open Knowledge Format
/okf/index.md
absent HTTP 404

What an agent can call

Standards observed

Cheapest next steps

  1. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "scrapfly.io"}))
  2. AGENTS.md: instructions for coding agents working on or with the site
    Generate starter /AGENTS.md for scrapfly.io
    # Scrapfly for agents
    
    Scrapfly and what it offers to agents
    
    ## Read the data, not the HTML
    - Index: https://scrapfly.io/llms.txt
    - API description: https://scrapfly.io/openapi.json
    - Discovery catalog: https://scrapfly.io/.well-known/ard.json
    
    ## Calling
    - MCP server (Streamable HTTP): https://scrapfly.io/mcp
    - Rate limits and authentication: describe them here
    
    ## Conventions
    - How to cite or attribute content
    - What not to do (no scraping of /account/, no automated sign-ups, etc.)
    
    Contact: security@scrapfly.io
    

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback openapi). Call the MCP endpoint at https://mcp.scrapfly.io/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://mcp.scrapfly.io/mcp POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.

Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0, HTML-to-llms.txt token ratio 3.202×.

AI crawler posture: search_allowed_training_blocked · Assistant access: OpenAI partial, Anthropic partial, Google partial, Perplexity partial, Exa partial.

Readiness subscores: reach 18/20, readability 30/30, capabilities 35/35, conformance 10/15, total 93/100, grade A+.

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules