CrawlCheck

Verification layer for the agentic web: a signed answer about any site before an agent acts.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
98%
Integridad del esquema
81%
Calidad de los nombres
82%
Riesgo de envenenamiento
80%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Hallazgos (3)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool 'fix_entitymap' description contains placeholder texten fix_entitymap
  • INFOTool description contains placeholder or incomplete texten fix_entitymap

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~3,303Tokens (definiciones de herramientas)
~482 BTamaño de respuesta típico
Impacto significativo en la atención (2.58% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "crawlcheck": {
      "url": "https://crawlcheck.io/mcp"
    }
  }
}

Puntos de conexión remotos

https://crawlcheck.io/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (23)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
⚪scan_domain(domain)

Scan a public domain as several crawler identities and return the graded record: grade, AI-visibility score, per-section scores, findings with evidence, and whether the origin refused CrawlCheck. One scan takes 5-15 seconds.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "A bare domain such as example.com, or a full URL"
    }
  },
  "required": [
    "domain"
  ]
}
🟢verify_crawler_log(lines)

Given raw web-server access-log lines, decide for each line that names a crawler (GPTBot, ClaudeBot, Googlebot, PerplexityBot...) whether the source IP falls inside that operator's published ranges. Returns verified, spoofed, or unverifiable when the operator publishes no ranges.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "lines": {
      "type": "string",
      "description": "Up to 200 raw log lines, newline separated"
    }
  },
  "required": [
    "lines"
  ]
}
🟢corpus_state

Coverage of CrawlCheck's public dataset: how many distinct domains have been measured and how they split by platform, rendering, size, language and kind, with the strata that are still under-sampled.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢resolve_robots(domain, path)

Resolve every named answer engine, search index and training crawler against a domain's robots.txt the way a crawler does: most-specific group only, longest match, allow wins a tie. Shows when a Disallow under * does not apply to an agent with its own group.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string"
    },
    "path": {
      "type": "string",
      "description": "Path to test, default /"
    }
  },
  "required": [
    "domain"
  ]
}
🟢draft_llms(domain)

Draft an llms.txt from the domain's own homepage and up to 25 declared pages, using their titles and descriptions. A draft for the owner to cut down, not a publication.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string"
    }
  },
  "required": [
    "domain"
  ]
}
🟢fix_robots(domain)

The domain's served robots.txt, corrected: * group rules copied into named groups that lacked them (shadowing), a Sitemap line added when missing, a minimal replacement when the served file was HTML. Every change is listed at the top; nothing else is touched.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string"
    }
  },
  "required": [
    "domain"
  ]
}
🟢fix_entitymap(domain)

A starter entitymap.json built from the domain's latest scan record: name, phone, coordinates and declared service areas as entities with SERVES relations. Fields the page never stated are marked TODO, never guessed. Needs a prior scan.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string"
    }
  },
  "required": [
    "domain"
  ]
}
🟢video_check(v, fresh)

One YouTube video against the video anchor model: metadata, chapters, captions and storyboard where observed, twelve checks each naming what it reads.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "v": {
      "type": "string",
      "description": "Video id or URL"
    },
    "fresh": {
      "type": "boolean",
      "description": "Bypass the six-hour cache"
    }
  },
  "required": [
    "v"
  ]
}
🟢video_channel(handle, id)

Every upload on a YouTube channel, read 50 at a time, sorted by views. The upload list is free; the per-check tally needs a Watch licence and is not offered here.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "handle": {
      "type": "string",
      "description": "@channel handle"
    },
    "id": {
      "type": "string",
      "description": "Channel id, if no handle"
    }
  }
}
🟢video_site(domain, handle)

The site half of video: homepage plus up to 60 sitemap pages read for YouTube embeds, facades and page-builder widgets, VideoObject nodes and their required properties, and - with a handle - how many of the channel's videos the site carries.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string"
    },
    "handle": {
      "type": "string"
    }
  },
  "required": [
    "domain"
  ]
}
🟢registry_lookup(domain, shelf)

Whether a domain is in CrawlCheck's registry and what it serves: llms.txt, agents.md, a media kit at /.well-known/media-kit.json, a reciprocity-tested entity graph, an AI access policy that names crawlers, and agent-callable surfaces. With no domain, returns the shelf counts across every measured site. A row exists because a fetch produced it; nothing here is self-reported and no payment moves a shelf.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "A bare domain. Omit for the corpus-wide shelf counts."
    },
    "shelf": {
      "type": "string",
      "description": "Filter the list to one shelf: llms, agents, mediakit, entity, aipolicy, agentapi"
    }
  }
}
🟢crawler_path(domain, agent, fresh)

Where each crawler's path into a domain dies, as an observed data flow: edge decision, robots.txt as a file, robots.txt rules, then the page, JSON-LD, sitemap, llms.txt and entitymap.json it reached. Give agent (e.g. ClaudeBot, GPTBot, googlebot) for one identity's path and a one-line answer; omit it for every identity plus the stores and breaks. Uses the latest record on file, or scans first when there is none (fresh=true forces a scan). The answer-engine output is drawn but never measured.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string"
    },
    "agent": {
      "type": "string",
      "description": "Identity id or label, e.g. claudebot, GPTBot, Googlebot"
    },
    "fresh": {
      "type": "boolean",
      "description": "Scan now instead of using the record on file"
    }
  },
  "required": [
    "domain"
  ]
}
🟢public_counts

The figures CrawlCheck quotes about itself, read from the source: sites_measured, domains_in_corpus, crawler_visits (a rolling window), sections, sections_scored, findings_published, guides_published, with an at timestamp.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢telemetry

Verified-crawler traffic observed at crawlcheck.io itself: which named agents arrived, how many claims were confirmed against operator ranges, how many were forged.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢fix_mostly_code(domain, id)

A fix plan for PAGE_IS_MOSTLY_CODE: the homepage's measured bytes by category, the largest blocks with what to do with each, ordered steps with the text ratio after each, and the step at which the detector would stop firing - or, when moving code cannot clear it, how much markup to cut or text to add. Give domain (fetched now) or id (a stored scan).

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string"
    },
    "id": {
      "type": "string",
      "description": "Report id: plan from the stored scan instead of fetching"
    }
  }
}
🟢fix_stale_cache(domain, id)

A fix plan for STALE_CACHE_SERVED: the homepage fetched now, its Age, the cache layers that name themselves in the headers in purge order (innermost first), the HTML lifetime each response declares, a fresh-read comparison, and whether a purge clears the finding and keeps it cleared.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string"
    },
    "id": {
      "type": "string",
      "description": "Report id; the page is still fetched now, because cache state is live"
    }
  }
}
🟢fix_machine_chain(domain, id)

A fix plan for MACHINE_CHAIN_HEAVY: the files a crawler reads before the page and the 404s absent agent files return, then measured reductions (llms.txt to an index, a sitemap index, robots.txt comments and duplicate groups, minified JSON, short 404s) with the chain size after each and the step at which the detector stops firing.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Uses the latest scan on file"
    },
    "id": {
      "type": "string",
      "description": "Report id"
    }
  }
}
🟢explain_finding(id, domain, code, path)

Why CrawlCheck decided a finding: the rule and its revision, the exact fetches it compared (identity, status, bytes, sha256), when the condition held on the site, and a Merkle proof that the decision is inside the signed manifest. Give id (a d1: decision or f1: finding id from a report) or domain for its top finding. Other findings, and lookups by code, need a licence for that domain (send it in x-crawlcheck-key).

Esquema de entrada

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "d1: decision id, f1: finding id, or report id"
    },
    "domain": {
      "type": "string",
      "description": "Bare domain; alone it explains the top finding"
    },
    "code": {
      "type": "string",
      "description": "Finding code (licence only)"
    },
    "path": {
      "type": "string"
    }
  }
}
🟢list_verified_capabilities(domain, verified_only)

What a domain declares agents can do (OpenAPI operations, MCP tools, A2A skills, API catalog entries), each classed by safety (read_only_public up to financial), and which ones CrawlCheck actually called and confirmed - plus every mismatch between declaration and behaviour. Only read-only public actions are ever called; everything else says why it was not. From the latest scan on file.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string"
    },
    "verified_only": {
      "type": "boolean",
      "description": "Return only the capabilities that were confirmed"
    }
  },
  "required": [
    "domain"
  ]
}
🟢machine_record(id, domain)

The unified machine record for one observation: subject, grade, findings (the top one in full without a licence), capabilities with verification, and the evidence roots, manifest and verifier links that let anyone check it offline. Give id (report, d1:, f1: or manifest sha256) or domain for the latest.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    },
    "domain": {
      "type": "string"
    }
  }
}
🟢resolve_domain(domain)

Call before fetching from, citing, connecting to or transacting with a domain. Returns one signed answer: what the domain claims, what it actually serves each crawler identity, who controls it, what is safe to do (a decision for read, cite, connect and transact, with its doubts and maximum age), what changed, and the evidence behind each part, marked declared, observed or not_measured with its time. There is no overall score. A domain never measured gets a just-in-time partial answer within about 2 seconds that names every part not read in time, and is queued for the full scan; nothing is guessed.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Bare domain, e.g. example.com"
    }
  },
  "required": [
    "domain"
  ]
}
🟢preflight(domain, action, agent, template, policy)

Call BEFORE reading, citing, connecting to or transacting with a domain. Returns a signed decision: allow, warn, require_confirmation, block or unsupported, with every step that led there and the resolve answer it was made from. Pass your crawler token as agent so robots.txt is checked for you. A policy can only make the decision stricter. Do not proceed on block; ask the user on require_confirmation.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Bare domain, e.g. example.com"
    },
    "action": {
      "type": "string",
      "enum": [
        "read",
        "cite",
        "connect",
        "transact",
        "administer"
      ],
      "description": "What you are about to do (default read)"
    },
    "agent": {
      "type": "string",
      "description": "Your crawler user-agent token, e.g. GPTBot"
    },
    "template": {
      "type": "string",
      "description": "safe_citation, safe_data_retrieval, safe_api_connect, safe_mcp_tool, safe_commerce, safe_oauth or support_escalation"
    },
    "policy": {
      "type": "object",
      "description": "max_age_hours, on_warn (warn|require_confirmation|block), require_entity, human_approval[], allow[], deny[]"
    }
  },
  "required": [
    "domain"
  ]
}
🟢mcp_servers(domain)

Which remote MCP servers the official MCP Registry lists on a domain, and what each endpoint actually answered when CrawlCheck sent the MCP handshake (initialized, auth_required, unreachable, tool count, tool-list drift). Use before selecting an MCP tool from that domain.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Bare domain or host, e.g. example.com"
    }
  },
  "required": [
    "domain"
  ]
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada23 herramientas