McpStamp Backlink Checker
MCPB · BACKLINK-CHECKER.MCPB · 2 COMPONENTS
Check whether a page links to your domain: dofollow or nofollow, anchor text, link list audits.
Available components
Last scanned (13 hours ago)
Scores higher than 98% of MCPB servers
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 48 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 345 tokens (~69/item across 5 items; 5 tools + 0 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityNo malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Provenance: unverified → fail ▼ security
- Stability: pass → 0.93 functional
- 2 Nov 26 +58
- Install scripts: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → 0.85 ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Nov 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 31 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 30 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 17 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 14 Oct 26 −54
- Tool safety: pass → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- Known CVEs: partial → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.84 → unverified ▼ functional
- License: pass → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- Package version: 0.22.0 → 0.22.5 functional
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 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/backlink-checker.mcpb@0.22.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
license_activate Activate license ~71
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
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.
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 ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, ebae4fedfcc57e85df651f04af371f2ab1f8914d651f3fd30d71096315b95637; the commands to do that are on this page. If it does not match, do not open it.
mcpb · backlink-checker.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
ebae4fedfcc57e85df651f04af371f2ab1f8914d651f3fd30d71096315b95637
macOS / Linux
echo "ebae4fedfcc57e85df651f04af371f2ab1f8914d651f3fd30d71096315b95637 backlink-checker.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\backlink-checker.mcpb).Hash -eq "ebae4fedfcc57e85df651f04af371f2ab1f8914d651f3fd30d71096315b95637"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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 MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/backlink-checker.mcpb).
Is the McpStamp Backlink Checker MCP server safe to use?
McpStamp Backlink Checker scores 63 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 5 tools: link_check, link_audit, robots_guard_check, license_status, license_activate. Their descriptions and schemas cost roughly 345 tokens of context every time the server is loaded.
What licence is the McpStamp Backlink Checker MCP server under?
McpStamp Backlink Checker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the McpStamp Backlink Checker MCP server?
VerifyMCP ran 15 checks on McpStamp Backlink Checker, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about McpStamp Backlink Checker: Malware scan. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.