Skip to content

CrawlWitness MCP server

com.crawlwitness/oraclecrawlwitness.comstreamable-httpv1.0.52Scanned

AI consent & licensing check for any domain, with signed on-chain receipts. Paid via x402.

6 tools: 5 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 5 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the CrawlWitness MCP server can do

The CrawlWitness MCP server is published by crawlwitness.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: check_ai_consent, can_ai_use, ai_consent_score, signal_history and 1 more), but cannot delete data. 1 tool only reads.

4 tools bring in text other people can write (check_ai_consent, can_ai_use, ai_consent_score and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 1.0.52.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 5Claude Code: ask
  • can_ai_useFast yes/no verdict for one domain, one AI bot and one use (train, rag or search), from robots.txt, IETF AIPREF, W3C TDMRep, noai directives and RSL licenses, with the reasons and …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Fast yes/no verdict for one domain, one AI bot and one use (train, rag or search), from robots.txt, IETF AIPREF, W3C TDMRep, noai directives and RSL licenses, with the reasons and a signed receipt. Use it in a crawler or RAG pipeline before fetching each new domain. Costs 0.001 USD on Base (0.002 on Solana) via x402. Invalid domain or unknown bot is never charged.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Can AI use
  • check_walletSanctions screening of a crypto address against the US OFAC SDN list (all its digital-currency addresses: EVM, BTC, TRX, SOL, USDT, USDC…).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Sanctions screening of a crypto address against the US OFAC SDN list (all its digital-currency addresses: EVM, BTC, TRX, SOL, USDT, USDC…). Use it before an agent pays, receives from or interacts with a wallet. Returns sanctioned true/false, the listed entity and programs, the exact list version used and a signed receipt. Costs 0.005 USD via x402. Screening aid, not legal advice.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Check wallet
  • signal_historyWhat a domain's robots.txt (or llms.txt, tdmrep.json, RSL license, homepage headers) said at a given instant, with the SHA-256 of each version and its EAS attestation anchored on B…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What a domain's robots.txt (or llms.txt, tdmrep.json, RSL license, homepage headers) said at a given instant, with the SHA-256 of each version and its EAS attestation anchored on Base. Without `source` it returns the index of versions; with `source` (and optional `at`, RFC 3339) the document in force at that instant. Covers only domains already analysed.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Signal history
Only reads 1Show 1 read-only tool
  • verify_receiptReturns the signed EAS attestation of a paid query and, once anchored, its Merkle proof (OpenZeppelin format) and the on-chain attestation on Base that contains it.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Returns the signed EAS attestation of a paid query and, once anchored, its Merkle proof (OpenZeppelin format) and the on-chain attestation on Base that contains it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Verify receipt

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:21 UTC, unchanged since Nov 2, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.crawlwitness.com/mcp: tools/list returned 6 tools to an anonymous client, including check_ai_consent (write), can_ai_use (write), ai_consent_score (write), signal_history (write), check_wallet (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.52. Values in angle brackets are yours to fill in.

claude mcp add --transport http oracle https://api.crawlwitness.com/mcp
claude mcp add --transport http oracle https://api.crawlwitness.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__oracle__verify_receipt"
    ],
    "ask": [
      "mcp__oracle__check_ai_consent",
      "mcp__oracle__can_ai_use",
      "mcp__oracle__ai_consent_score",
      "mcp__oracle__signal_history",
      "mcp__oracle__check_wallet"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as oracle. Review it before you use it.

Capability tags behind 4 rules
  • mcp__oracle__check_ai_consent untrusted-input
  • mcp__oracle__can_ai_use untrusted-input
  • mcp__oracle__ai_consent_score untrusted-input
  • mcp__oracle__check_wallet untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.crawlwitness/oracle/verify?hash=e1d993288699a3737f2ea30bb4b75a85790540baa0b9a50930e5f28346ea8c66" | jq -e '.changed == false'

Pinned hash e1d993288699, from Nov 15, 2026, 01:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.crawlwitness/oracle/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.crawlwitness/oracle
[![Anlyon Radar](https://radar.anlyon.com/badge/com.crawlwitness/oracle.svg)](https://radar.anlyon.com/servers/com.crawlwitness/oracle)

Source: MCP Registry. Synced Nov 2, 2026, 00:17 UTC.

CrawlWitness MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the CrawlWitness MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the CrawlWitness MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the CrawlWitness MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the CrawlWitness MCP server have?

6 tools: 5 write, 1 read. check_ai_consent, can_ai_use, ai_consent_score, signal_history, check_wallet and verify_receipt.

Does the CrawlWitness MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the CrawlWitness MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the CrawlWitness MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.