McpStamp Backlink Checker
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS
Check whether a page links to your domain: dofollow or nofollow, anchor text, link list audits.
Available components
Last scanned (4 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 747 tokens (~83/item across 9 items; 8 tools + 1 resources), lean.Pass
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 71 → 83 ▼ functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://mcp.zovo.one/mcp/backlink-checker
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 39e1adfa4eb6500e0e3d48868766e3e9 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/backlink-checker"
Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/backlink-checker"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/backlink-checker |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one/mcp/backlink-checker |
| Authorisation server | https://mcp.zovo.one |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/backlink-checker | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/backlink-checker | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/backlink-checker |
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 →
anchor_profile Extract anchor text profile from a page ~73
Fetch one referring page and list every outbound link with its anchor text and dofollow/nofollow classification, so you can see how a site links out before requesting a link change.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max links to return (default 50) |
| page_url | string | yes | Page URL, including https:// |
No output schema declared.
No examples provided.
license_activate Activate license ~76
Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
link_audit Audit a list of backlinks ~77
Check up to N referring pages against one target domain and return a per-URL table: HTTP status, dofollow/nofollow, anchor text, robots guards. Free tier: 3 URLs per call.
| Name | Type | Req | Description |
|---|---|---|---|
| page_urls | array | yes | Referring page URLs |
| target_domain | string | yes | Domain the backlinks should point at |
No output schema declared.
No examples provided.
link_check Check one backlink ~93
Fetch a referring page and report whether it links to the target domain, whether that link is dofollow or nofollow, the anchor text, HTTP status and robots guards (meta robots / X-Robots-Tag noindex, nofollow).
| Name | Type | Req | Description |
|---|---|---|---|
| page_url | string | yes | Referring page URL, including https:// |
| target_domain | string | yes | Domain the backlink should point at, e.g. example.com |
No output schema declared.
No examples provided.
outreach_queue Check a list of pages for a link back to your domain ~96
Batch link check for outreach follow-ups: pass up to 10 page URLs and your domain, get one line per page (status, linked or not, dofollow). Built for the Monday-morning question: which of the sites that promised a link actually shipped it?
| Name | Type | Req | Description |
|---|---|---|---|
| page_urls | array | yes | Up to 10 page URLs, including https:// |
| target_domain | string | yes | Your domain, e.g. example.com |
No output schema declared.
No examples provided.
referring_domain_summary Summarize one referring domain from its page ~75
Fetch a page and summarize the referring domain: HTTP status, indexability, outbound link count, and whether the target domain appears anywhere in the text (brand mention without a link).
| Name | Type | Req | Description |
|---|---|---|---|
| page_url | string | yes | Page URL, including https:// |
| target_domain | string | yes | Domain to look for, linked or mentioned |
No output schema declared.
No examples provided.
robots_guard_check Check robots guards on a page ~50
Fetch one URL and report HTTP status plus meta robots / X-Robots-Tag noindex and nofollow signals, without extracting links.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Page URL, including https:// |
No output schema declared.
No examples provided.
How do I install the McpStamp Backlink Checker MCP server?
McpStamp Backlink Checker is a hosted endpoint at https://mcp.zovo.one/mcp/backlink-checker, 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 · mcp.zovo.one
claude mcp add --transport http theluckystrike-backlink-checker 'https://mcp.zovo.one/mcp/backlink-checker'
What is the McpStamp Backlink Checker MCP server?
McpStamp Backlink Checker is an MCP server listed in the public MCP registry as io.github.theluckystrike/backlink-checker. Check whether a page links to your domain: dofollow or nofollow, anchor text, link list audits. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/backlink-checker).
Is the McpStamp Backlink Checker MCP server safe to use?
McpStamp Backlink Checker scores 95 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 McpStamp Backlink Checker MCP server expose?
McpStamp Backlink Checker exposes 8 tools: link_check, link_audit, anchor_profile, referring_domain_summary, outreach_queue, and 3 more. Their descriptions and schemas cost roughly 595 tokens of context every time the server is loaded.
Does the McpStamp Backlink Checker MCP server require authentication?
Yes. McpStamp Backlink Checker asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the McpStamp Backlink Checker MCP server still maintained?
McpStamp Backlink Checker is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.