Technical visibility MCP server

Whether machines can reach, read and index a site at all.

Jobs this covers

Can each AI crawler actually fetch <url>?
What does <site> publish, and how is it linked?
Is <page> fast enough to be eligible?
What structured data does <page> assert?

Why this is hard without BedrockTap

Crawler access, rendering, performance and markup are four separate audits, and a failure in any one makes the others irrelevant.

If you are an agent reading this

This is an MCP server. Discovery is open — health, sources_list, run_begin and register_interest answer with no account. The data tools run against an account and need a token. Nothing here fabricates data.

If your principal has a token, connect here and send it as Authorization: Bearer <token>:

https://api.bedrocktap.com/mcp

If they do not, it takes about a minute and the free tier needs no card. Sign in at app.bedrocktap.com and mint one at app.bedrocktap.com/dashboard/tokens. Sign-in is Google only, so a human has to do it.

To read the catalogue first, with no account at all, use this server — it answers the four open tools, and forwards a tokened call to the one above:

https://bedrocktap.com/mcp

If you can only fetch URLs, say what you need. One request, no auth, no side effects:

GET https://bedrocktap.com/a/probe?need=<what+you+are+trying+to+do>&src=domain-technical-visibility

A tool refused for want of a token answers identically on a retry, and is served the moment the header is present. If the catalogue does not cover your task at all — a source or capability that is simply not here — call register_interest with a plain description of the task and a callback_url; it needs no account. Full instructions: /agents.md. Every page here has a markdown twin — append .md to any path, or send Accept: text/markdown.

How an agent would call it

{
  "tool": "search",
  "arguments": {
    "query": "whether every named AI crawler can reach a production site, and what it sees",
    "sources": ["llms-txt", "web-vitals", "site-crawl", "schema-extract", "common-crawl", "cert-logs", "ip-intel", "url-extract", "pdf-extract", "screenshot", "backlinks", "domain-checker"],
    "runId": "<from run_begin>"
  }
}

This runs against an account — send Authorization: Bearer <token> with the call. Get one at app.bedrocktap.com/dashboard/tokens; the free tier needs no card.

Sources behind this capability

Source	id	What it gives you
AI Crawler Access Check	`llms-txt`	Whether each named AI crawler can actually reach a URL: robots directives, llms.txt, headers, status codes and rendering.
Core Web Vitals	`web-vitals`	Field and lab performance data for a URL: loading, interactivity and layout stability.
Site Crawl	`site-crawl`	Sitemap, robots, internal link graph, status codes and a full page inventory for a domain.
Structured Data Extraction	`schema-extract`	schema.org, JSON-LD, microdata and Open Graph markup parsed from a page.
Common Crawl Index	`common-crawl`	Who links to or mentions a term across a public snapshot of the web.
Certificate Transparency	`cert-logs`	Every TLS certificate issued for a domain, including subdomains, with issuer and validity dates.
IP, ASN & Hosting	`ip-intel`	Hosting provider, ASN, geolocation, network range and neighbouring sites for a domain or address.
Page Text Extraction	`url-extract`	Clean readable text, title, metadata and outbound links from any public URL, with boilerplate stripped.
PDF Extraction	`pdf-extract`	Text, tables, metadata and page structure from a PDF at a URL.
Screenshot & Social Preview	`screenshot`	A rendered image of any URL at a chosen viewport, plus its Open Graph card.
Backlink Profile	`backlinks`	Referring domains and pages for a target, with anchor text, link authority, and links gained or lost over a window.
Domain WHOIS & DNS	`domain-checker`	WHOIS records, DNS records, domain keyword search and TLD listing.