MCP server: scan any public website for SEO, AI search (GEO), local signals, trust, conversion and speed, read any page of buildmydigital.co.uk as Markdown, and list Build My Digital's services with published prices.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"build-my-digital-website-scanner","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 6 h ago | mcp initialize | ok | 200 | 448 ms | server build-my-digital 1.1.0 · protocol 2025-06-18 · 3 tools |
| 13 h ago | mcp initialize | ok | 200 | 177 ms | server build-my-digital 1.1.0 · protocol 2025-06-18 · 3 tools |
| 20 h ago | mcp initialize | ok | 200 | 181 ms | server build-my-digital 1.1.0 · protocol 2025-06-18 · 3 tools |
| 27 h ago | mcp initialize | ok | 200 | 178 ms | server build-my-digital 1.1.0 · protocol 2025-06-18 · 3 tools |
| 33 h ago | mcp initialize | ok | 200 | 233 ms | server build-my-digital 1.1.0 · protocol 2025-06-18 · 3 tools |
| 2 d ago | mcp initialize | ok | 200 | 405 ms | server build-my-digital 1.1.0 · protocol 2025-06-18 · 3 tools |
| 2 d ago | mcp initialize | ok | 200 | 175 ms | server build-my-digital 1.1.0 · protocol 2025-06-18 · 3 tools |
| 2 d ago | mcp initialize | ok | 200 | 195 ms | server build-my-digital 1.1.0 · protocol 2025-06-18 · 3 tools |
| 2 d ago | mcp initialize | ok | 200 | 189 ms | server build-my-digital 1.1.0 · protocol 2025-06-18 · 3 tools |
| 3 d ago | mcp initialize | ok | 200 | 218 ms | server build-my-digital 1.1.0 · protocol 2025-06-18 · 3 tools |
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.