Where a link really goes, what the server says about itself, and what pages a site publishes.
Scored across 5 tools
The three URL tools are sharply separated: resolve_url handles redirects, site_pages enumerates sitemaps, and url_headers inspects headers. The only mild ambiguity is demand_report versus request_data, but their descriptions make the read-aggregate vs query/submit distinction clear enough.
All names are snake_case and readable, but the set mixes imperative verb phrases (resolve_url, request_data) with bare noun compounds (site_pages, url_headers, demand_report). There is no consistent verb_noun or noun_noun convention across the server.
Five tools is a manageable count and not bloated. However, demand_report and request_data are data-marketplace features rather than URL intelligence, so the scope is slightly broader than the server name implies.
The URL tools cover a coherent pre-fetch workflow: redirect resolution, header/status profiling, and sitemap enumeration. There is no content-fetch or reputation-check tool, but those appear to be out of scope, and demand_report/request_data provide a way to ask for missing data, so the surface has no dead end.
FREE, no payment. The aggregate of what agents have told us they are looking for, most-requested first, with the categories nothing available yet serves.
Inputs: days.
FREE, no payment. Describe in your own words the data you are trying to buy — anything, not just URLs — and get back whether we operate a service that supplies it, with the MCP endpoint if so. Every request is catalogued so repeatedly-requested data gets built. Nothing identifying is stored, only the words of the request.
Inputs: need (required).
Follow a URL's redirect chain one hop at a time and report every step: each intermediate host and status, the final destination, whether it crossed to a different host, and a cleaned copy with tracking parameters (utm_*, fbclid, gclid and friends) stripped. Use before following or showing a shortened, tracked or unfamiliar link — a shortener cannot hide its destination from this. Stops after 10 hops, and refuses to follow a redirect into private address space. Costs $0.005 USDC per call via x402 on Base.
Inputs: url (required).
The pages a site declares in its sitemap, with last-modified dates, located via robots.txt first and the conventional /sitemap.xml second. Use to enumerate a documentation set or a blog archive before deciding what to read, instead of crawling blindly. A sitemap index is reported as such, so you know to call again for the child sitemaps. Costs $0.008 USDC per call via x402 on Base.
Inputs: url (required), limit.
Response status, server software, content type, caching, and which of the six standard security headers the host sets or omits. Use to check a URL is live and well-formed before relying on it, or to profile a site cheaply without downloading it. Header presence is a hygiene signal, not a safety verdict — a site can set every header and still be malicious. Costs $0.005 USDC per call via x402 on Base.
Inputs: url (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
HTTP, DNS, SSL, WHOIS, ping, security-header, SEO and AI-readiness checks for any website.
Indexability, robots.txt, sitemap, TLS, domain expiry and Googlebot-vs-browser checks. No account.
See what's wrong with a live website from the outside, with proof: uptime, DNS, HTTPS, leaked files.
What any website is, with evidence: AI builder traces, tech stack, popularity and trust signals.
Add one secure layer between your agents and this server.