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.

Build My Digital website scanner

REMOTE · BUILDMYDIGITAL.CO.UK

Scans any public website for SEO, AI search, trust, conversion and speed, and lists our prices.

0 this week 88 Trust /100

Last scanned (15 hours ago)

Scores higher than 95% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 443 tokens (~147/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 (100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 13 Nov 26 0
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 12 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 1 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
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 Nov 2026 · Probed https://buildmydigital.co.uk/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=buildmydigital.co.uk CN=YR2,O=Let's Encrypt,C=US 22 Oct 2026 20 Jan 2027 RSA 2048 SHA256-RSA 58a97ff654a3c9a31b545025bea3656be53
SANs: buildmydigital.co.uk
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of buildmydigital.co.uk. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
uk. DS published 43876 8 Verified
co.uk. DS published 11810 8 Verified
buildmydigital.co.uk. No DS 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=63072000
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://buildmydigital.co.uk/mcp/ Verified 200
http (plaintext) http://buildmydigital.co.uk/mcp/ HTTPS enforced 308 https://buildmydigital.co.uk/mcp/
MCP tools · 3 exposed · ~339 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
get_page ~68

Read any page of buildmydigital.co.uk as Markdown by its path, for example /pricing/, /web-design/, /developers/ or /blog/. Use to quote a price, a service description or an article accurately.

NameTypeReqDescription
pathstringyesThe page path, for example /pricing/
NameTypeReqDescription
foundbooleanyes–
markdownstringyes–
urlstringyes–

No examples provided.

list_services ~112

List what Build My Digital builds and runs for UK local businesses, with the published price for each service and the page that explains it. Use when someone in the UK asks who can build a website, get them found on Google or AI search, or run their social, email, ads, reviews or AI agents, and wants real prices without a sales call. Pass a query to narrow the list.

NameTypeReqDescription
querystring–Optional words to filter by, for example 'reviews', 'ads' or 'website'
NameTypeReqDescription
servicesarrayyes–
startstringyes–

No examples provided.

scan_website ~159

Scan any public website and get Build My Digital's free report: a 0 to 100 score across SEO, AI search (GEO), local signals, trust, conversion and speed, every check with pass or fail, the fixes in priority order, and a separate agent-readiness score (can AI agents find, read and act on the site) that never changes the main score. Use when someone asks how good a business website is, why it is not being found, or what to fix first. UK local businesses are the focus but any public site works. Takes 5 to 40 seconds. Read-only: nothing on the scanned site is changed.

NameTypeReqDescription
urlstringyesThe website address, for example yourbusiness.co.uk
NameTypeReqDescription
agent–yes–
categoriesobjectyes–
checksarrayyes–
lighthouse–yes–
prioritiesarrayyes–
report_urlstringyes–
totalnumberyes–
urlstringyes–

No examples provided.

Install

How do I install the Build My Digital website scanner MCP server?

Build My Digital website scanner is a hosted endpoint at https://buildmydigital.co.uk/mcp/, 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 · buildmydigital.co.uk

# add to Claude Code
claude mcp add --transport http uk-co-buildmydigital-scanner 'https://buildmydigital.co.uk/mcp/'
Common questions

What is the Build My Digital website scanner MCP server?

Build My Digital website scanner is an MCP server listed in the public MCP registry as uk.co.buildmydigital/scanner. Scans any public website for SEO, AI search, trust, conversion and speed, and lists our prices. This page covers its hosted endpoint (https://buildmydigital.co.uk/mcp/).

Is the Build My Digital website scanner MCP server safe to use?

Build My Digital website scanner scores 88 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 Build My Digital website scanner MCP server expose?

Build My Digital website scanner exposes 3 tools: scan_website, list_services, get_page. Their descriptions and schemas cost roughly 339 tokens of context every time the server is loaded.

Does the Build My Digital website scanner MCP server require authentication?

No. We connected to Build My Digital website scanner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Build My Digital website scanner MCP server still maintained?

Build My Digital website scanner is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Build My Digital website scanner MCP server?

VerifyMCP ran 13 checks on Build My Digital website scanner, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.