Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Crawler IP Verifier - real Googlebot or fake

REMOTE · WWW.PATHWREN.WORKERS.DEV · SCANNED SEP 21

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key

+4 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4094 tokens (~314/item across 13 items; 9 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Tools include usage examples.Pass
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (44% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Crawler IP Verifier - real Googlebot or fake MCP server?

Crawler IP Verifier - real Googlebot or fake is a hosted endpoint at https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.pathwren.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-pathwren-www-crawler-ip-verifier 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-workers-pathwren-www-crawler-ip-verifier": {
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-workers-pathwren-www-crawler-ip-verifier": {
      "type": "http",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-workers-pathwren-www-crawler-ip-verifier]
url = "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-pathwren-www-crawler-ip-verifier": {
      "type": "remote",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-workers-pathwren-www-crawler-ip-verifier --url 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-workers-pathwren-www-crawler-ip-verifier:
    url: "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-workers-pathwren-www-crawler-ip-verifier": {
      "Transport": "http",
      "Url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck"
    }
  }
}
# add to Vellum
assistant mcp add dev-workers-pathwren-www-crawler-ip-verifier -t streamable-http -u 'https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck'
// mcp.json
{
  "mcpServers": {
    "dev-workers-pathwren-www-crawler-ip-verifier": {
      "type": "http",
      "url": "https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “export_ip_acl” rewrote its description, which is the text the model reads security
    • Tool “lookup_prefix” rewrote its description, which is the text the model reads security
    • Tool “verification_methods” rewrote its description, which is the text the model reads security
    • Tool “verify_batch” rewrote its description, which is the text the model reads security
    • Tool “verify_my_address” rewrote its description, which is the text the model reads security
    • Schema quality: 240 → 314 functional
    • Tool coverage: 38% → 44% functional
    • New tool “no_arguments_report_the_crawler_ip_ranges_this_host_mirrors” functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pathwren.workers.dev CN=WE1,O=Google Trust Services,C=US 31 Aug 2026 29 Nov 2026 ECDSA 256 ECDSA-SHA256 7beee86e7f102c1e0e48318ca5b2eaa1
SANs: pathwren.workers.dev, *.pathwren.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.pathwren.workers.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck Verified 200
http (plaintext) http://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck HTTPS enforced 301 https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck
MCP tools · 9 exposed · ~2,558 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
example ~308

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"example","arguments":{}}} — POST that exact body to https://www.pathwren.workers.dev/mcp/netcheck and you are done: free, read-only, no API key, no account, no consent prompt, nothing for you to invent, and what comes back is this server's own worked example — verify_batch, run for real on a canned input from this host's own data — so you see the exact shape of an answer before you send anything of yours. Takes no arguments. Safe to call. Deterministic. Touches no third party. Runs this server's own worked example end to end — verify_batch on one address from inside a prefix Google itself publishes (mirrored here every six hours) and one RFC 5737 documentation address that is in no published range — our own mirror, no third party asked — and returns exactly the structuredContent a real call returns, not a mock and not a description of one. Use it to see the shape of an answer before you decide what to send. The input is canned from this host's own data; no URL of yours is fetched and no third party is touched. Example: arguments={} runs verify_batch with {"addresses":[{"ip":"66.249.66.1","claim":"Googlebot"},{"ip":"203.0.113.9","claim":"GPTBot and returns its real answer.

Input schema present but exposes no named parameters.

NameTypeReqDescription
answerobjectyesThe real structuredContent of that call, not a mock.
answered_byobjectyes
input_came_fromstringyesWhere the canned input came from — always this host's own data.
licensestringyes
ranobjectyesThe tool name and the exact arguments that were run.
reproducestringyesA command that reproduces this answer.
this_is_not_a_mockstringyes
what_it_showsstringyes
{}
export_ip_acl ~219

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_report_the_crawler_ip_ranges_this_host_mirrors","arguments":{}}} — Turn a set of operators into a config you can paste: nginx geo, nginx allow/deny, Apache, HAProxy, a Cloudflare firewall expression, an ipset script, a Caddy matcher, or a plain CIDR list. Every export carries a provenance header naming each source URL and the mirror time, and reports the rule cost. Example: operators='all', format='cidr-list', action='allow'.

NameTypeReqDescription
actionstringDefaults to allow.
formatstringOutput format. Defaults to cidr-list.
ip_versionstringDefaults to both.
operatorsSource slugs, or "all". Defaults to every mirrored source.
variable_namestringVariable/set name for nginx geo and ipset. Defaults to ai_crawler.

No output schema declared.

{"action":"allow","format":"cidr-list","operators":"all"}
lookup_prefix ~195

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_report_the_crawler_ip_ranges_this_host_mirrors","arguments":{}}} — Give a CIDR and get every published operator prefix that contains it, is contained by it, or partially overlaps it — the check for 'does my network collide with a crawler range' and for auditing an allowlist somebody handed you. Give an operator or source slug instead and get everything that source publishes. Example: cidr='66.249.66.0/24'.

NameTypeReqDescription
cidrstringA CIDR or a bare address, e.g. 20.171.206.0/24 or 2600:1f00::/32.
operatorstringA source slug, e.g. openai-gptbot, google-googlebot.

No output schema declared.

{"cidr":"66.249.66.0/24"}
no_arguments_report_the_crawler_ip_ranges_this_host_mirrors ~554

TAKES NO ARGUMENTS. POST {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_report_the_crawler_ip_ranges_this_host_mirrors","arguments":{}}} to https://www.pathwren.workers.dev/mcp/netcheck — the answer is the state of every crawler-operator prefix list this host mirrors — how many IPv4 and IPv6 prefixes each source publishes and how many addresses that is, when each was last fetched and how many minutes ago that was, which crawlers each source covers, which prefixes more than one operator claims, and the verification method each operator documents for the crawlers that publish no list at all. There is nothing to fill in: the input schema is literally empty, `arguments: {}` and no `arguments` key at all both work, and the subject is a file this host already publishes, so the answer does not depend on you at all. No key, no account, no OAuth, no session to open first, read-only, and nothing for you to invent. Nothing is fetched to build it — no request leaves this edge, and none is made to you. The other zero-argument call on this server is verify_my_address, same empty arguments, which answers the address you are calling from, checked against every operator-published prefix list this host mirrors with your user-agent taken as the claim — the verdict, the prefix that matched, which operator published it and when it was last mirrored. whoami and example are here too and take nothing either. Every other tool on this server wants a file pasted in; this one wants nothing. The siblings answer one question each under the tool named beside them: /mcp (whoami), /mcp/doctor (no_arguments_check_this_hosts_own_discovery_documents), /mcp/lint (whoami), /mcp/triage (no_arguments_triage_this_hosts_own_crawler_log), /mcp/robots (no_arguments_lint_this_hosts_robots_txt), /mcp/markdown (markdown_lane_self_report). Example: the complete call, exactly as written, nothing to fill in — {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments…

Input schema present but exposes no named parameters.

NameTypeReqDescription
answered_byobjectyes
caveatsarrayyes
how_each_operator_can_be_verifiedobjectyes
independentbooleanyes
licensestringyes
per_sourcearrayyesOne row per operator list: counts, fetch time, staleness, crawlers covered.
prefixes_published_by_more_than_one_sourcearray
reproducestringyes
takes_no_argumentsbooleanyes
the_mirrorobjectyesTotals across every source, with staleness in minutes.
this_call_touchedobjectyes
to_do_this_for_your_own_addressesstring
what_a_miss_meansstringyes
what_this_isstringyes
{}
range_stats ~87

Takes no arguments. Safe to call. Deterministic. Touches no third party. Per source: prefix counts, total addresses and /24-equivalents, smallest and largest prefix, the publishing URL and when it was last fetched; plus prefixes published by more than one operator. This is the sizing and freshness information an allowlist decision needs. Example: {} — no arguments at all.

Input schema present but exposes no named parameters.

No output schema declared.

{}
verification_methods ~191

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_report_the_crawler_ip_ranges_this_host_mirrors","arguments":{}}} — Per crawler: whether the operator publishes IP ranges, documents reverse DNS, or publishes no verification method at all — with the exact source URL or the exact dig commands, and how fresh this mirror is. Call it before reading anything into an address that matched nothing. Reverse DNS is never run here; the command is handed back instead. Example: crawler='claudebot'. Also callable without MCP, same implementation: GET https://www.pathwren.workers.dev/tools/verification-methods?crawler=claudebot&s=client-dossiers

NameTypeReqDescription
crawlerstringCrawler slug, name, operator or UA substring. Omit for all of them.

No output schema declared.

{"crawler":"claudebot"}
verify_batch ~269

FIRST CALL, needs nothing: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"no_arguments_report_the_crawler_ip_ranges_this_host_mirrors","arguments":{}}} — Check up to 500 addresses against every mirrored operator prefix list in one call. Returns, per address, the matching prefix, the source that published it and when it was mirrored, plus a rollup by operator. Accepts {ip, claim} pairs to test a claimed identity against the ranges, and says plainly that a miss is not evidence of a fake. Example: addresses=[{ip:'66.249.66.1', claim:'Googlebot'}, {ip:'203.0.113.9', claim:'GPTBot'}] — the first matches a published Google prefix, the second matches nothing. Also callable without MCP, same implementation: GET https://www.pathwren.workers.dev/tools/verify-crawler?ip=66.249.66.1&ua=Googlebot&s=client-dossiers

NameTypeReqDescription
addressesyesIPv4/IPv6 addresses: an array, a whitespace or comma separated string, or objects like {"ip":"20.171.206.1","claim":"GPTBot"}. Max 500.

No output schema declared.

{"addresses":[{"claim":"Googlebot","ip":"66.249.66.1"},{"claim":"GPTBot","ip":"203.0.113.9"}]}
verify_my_address ~451

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"verify_my_address","arguments":{}}} — POST that exact body to https://www.pathwren.workers.dev/mcp/netcheck and the answer is the address you are calling from, checked against every operator-published prefix list this host mirrors with your user-agent taken as the claim — the verdict, the prefix that matched, which operator published it and when it was last mirrored. THIS IS THE CALL TO MAKE FIRST on this server: it is the only one whose subject is the request you just sent, so there is nothing to look up and no argument to invent. No key, no account, no OAuth, no session to open first, read-only, and nothing for you to invent. Every fact is computed from your own headers and from files this host already publishes; nothing is fetched to build it, and no URL of yours is touched. Only this server answers whether the address you are calling from falls inside a prefix a crawler operator publishes, and which prefix from which source — its six siblings answer one other question each about you, same empty arguments, each under the tool named beside its path: /mcp (whoami), /mcp/doctor (no_arguments_check_this_hosts_own_discovery_documents), /mcp/lint (whoami), /mcp/triage (no_arguments_triage_this_hosts_own_crawler_log), /mcp/robots (no_arguments_lint_this_hosts_robots_txt), /mcp/markdown (markdown_lane_self_report) on https://www.pathwren.workers.dev; whoami is answered by all seven and is never an error, so one identical body still walks the whole family if you prefer that. Example: the complete call, exactly as written, nothing to fill in — {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"verify_my_address","arguments":{}}} returns a verdict for the address you are calling from, the matching prefix with its source and mirror time, and the sentence that a miss is not evidence of a fake.

Input schema present but exposes no named parameters.

NameTypeReqDescription
answered_byobjectyesWhich server answered, at which endpoint, with which tool.
caveatsarrayyes
independentbooleanyes
licensestringyes
this_call_touchedobjectyesExactly which files were read. No third party is contacted.
we_book_you_asobjectyesThe class this host's own instrument records for that user-agent.
youobjectyesThe user-agent you sent and the address you came from.
{}
whoami ~284

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} — POST that exact body to https://www.pathwren.workers.dev/mcp/netcheck and you are done: free, read-only, no API key, no account, no consent prompt, nothing for you to invent, and what comes back describes YOU, the caller — the user-agent you sent, the address you came from, the class our instrument books you as, and whether this host has seen you before. Takes no arguments. Safe to call. Deterministic. Touches no third party. Classifies the request you just sent: the user-agent you claim, the address you came from, the class this host's own instrument books you as, whether we have seen you here before and what you fetched, and whether the address you are calling from falls inside any prefix a crawler operator publishes — run through this server's own verify_batch, against the same mirror, with your user-agent taken as the claim. Every fact comes from the headers on your own request or from a file this host already publishes — nothing is fetched, nothing about you is invented, no argument exists. Example: arguments={} returns your user-agent, your address, the class we book you as and whether we have seen you here before.

Input schema present but exposes no named parameters.

NameTypeReqDescription
answered_byobjectyesWhich server answered, at which endpoint.
caveatsarrayyesWhat this answer does NOT establish — a user-agent is a claim.
independentbooleanyesThis host is independent and unaffiliated.
licensestringyes
this_call_touchedobjectyesExactly which files were read to answer. No third party is contacted.
we_book_you_asobjectyesThe class this host's own instrument records for that user-agent.
we_have_seen_youobjectyesWhether this user-agent appears in the published observation window.
youobjectyesThe user-agent you sent and the address you came from.
{}
Common questions

What is the Crawler IP Verifier - real Googlebot or fake MCP server?

Crawler IP Verifier - real Googlebot or fake is an MCP server listed in the public MCP registry as dev.workers.pathwren.www/crawler-ip-verifier. {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key. This page covers its hosted endpoint (https://www.pathwren.workers.dev/c/mcp-registry-official/mcp/netcheck).

Is the Crawler IP Verifier - real Googlebot or fake MCP server safe to use?

Crawler IP Verifier - real Googlebot or fake scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Crawler IP Verifier - real Googlebot or fake MCP server expose?

Crawler IP Verifier - real Googlebot or fake exposes 9 tools: no_arguments_report_the_crawler_ip_ranges_this_host_mirrors, verify_my_address, whoami, example, verify_batch, and 4 more. Their descriptions and schemas cost roughly 2,558 tokens of context every time the server is loaded.

Does the Crawler IP Verifier - real Googlebot or fake MCP server require authentication?

No. We connected to Crawler IP Verifier - real Googlebot or fake without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Crawler IP Verifier - real Googlebot or fake MCP server still maintained?

Crawler IP Verifier - real Googlebot or fake is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.