Home / MCP registry index / dev.workers.adamhaleworks.tools/web-research

Adam Hale Tools: Web Research and Open Data

dev.workers.adamhaleworks.tools/web-research in the official MCP registry. Endpoint https://tools.adamhaleworks.workers.dev/mcp.

The registry describes it as: Free web lookups; PDF to Markdown, audio transcripts, screenshots, WHOIS/DNS paid per call via x402.

We read its 12 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

tech_stack_lookup seo_meta_tags_check url_status_check sitemap_urls rss_to_json ted_tender_search page_to_markdown domain_intel robots_txt_check document_to_markdown transcribe_short_audio website_screenshot

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/dev-workers-adamhaleworks-tools-web-research/badge.svg)](https://lazaretto.dev/mcp-registry/dev-workers-adamhaleworks-tools-web-research)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.