Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Backlink Guard is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
11
downloads a day
local
runs on your machine
329
downloads in 30d
What it does
Vet link sources before you submit, verify listings, and audit your backlinks for link spam.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user backlink-guard-mcp '--' uvx --with mcp 'backlink-guard[mcp]' mcp
# 2 — ask your agent for something these tools do
# verify, submissions, vet and 7 more
Backlink Guard costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ZHAll 2 servers
zhuyansen2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Backlink Guard as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user backlink-guard-mcp '--' uvx --with mcp 'backlink-guard[mcp]' mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take GLASSER_API_KEY (Optional, the first choice for the paid checks: spam scores, search history, backlinks, competitors' links, AI Overviews.), AISA_API_KEY (Optional. The same checks without a Glasser key; the only source of questions, asked and --deep's Ahrefs and Semrush numbers.), GOANYAPI_API_KEY (Optional. A site's rating, a year of visits and whether Google still lists it.), BACKLINK_GUARD_STATE (Optional. Absolute path to the directory that holds the log, the cache and the networks seen before.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Whether page_url links to domain, whether the link passes ranking credit (followed; or nofollow, sponsored, ugc; or only a redirect through the site's own page) and where on the page it sits: body text, header, navigation, sidebar, footer, comments. Free: one request to the page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_url | string | yes | — |
| domain | string | yes | — |
The user's submission log on this machine (ledger.jsonl), with its warnings: more than five a week, one anchor used over and over. Free and instant.
Takes no parameters.
Check link sources (directories, lists, guest-post sites) before submitting to them: each gets an action (skip, look first, free only, low value, submit), a verdict (avoid, caution, ok) and the evidence for each finding.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sites | array | yes | — |
| deep | boolean | no | — |
| free | boolean | no | — |
| topics | array | no | — |
| newcomers | boolean | no | — |
The pages that rank on Google (US) for the keywords and are not the user's: directories, lists, articles, videos, threads, repositories, sorted by the visitors they get from these searches, each with what can honestly be done there. site: the user's own domain, left out. Paid: about 0.005 USD a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keywords | array | yes | — |
| site | string | no | — |
The user's own backlink profile: totals, new and lost referring domains by week, backlinks read one by one with the referring domains behind each anchor, site-wide links counted once, the spam score of the sites linking in, and the sites one owner runs among them. Paid: about 0.12 USD, with deep…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | — |
| deep | boolean | no | — |
| rows | integer | no | — |
The user's backlinks that land on pages of the user's that are gone (404, 410) or redirect, most referring domains first: each dead page with the closest live page in the user's sitemaps to 301 it to, each redirect followed hop by hop and judged. Nothing is redirected. Paid: about 0.06 USD,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | — |
Links the user's competitors earned and the user lacks: each rival's referring domains first seen in the last days days, and the sites linking to two or more rivals but not to the user, each with a linking page and what to do there. Paid: about 0.025 USD a call, 2N + 2 calls for N rivals (three:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | — |
| rivals | array | yes | — |
| days | integer | no | — |
| limit | integer | no | — |
| max_usd | number | no | — |
| early | boolean | no | — |
| vetted | integer | no | — |
Which sites Google's AI Overview cites for each keyword (US, English), whether the user's domain is among them and where it ranks, then the sites cited most: the places to be mentioned on. Paid: 0.002 USD a keyword through AIsa (0.004 when the overview loads late), 0.004 through Glasser (0.006),…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | — |
| keywords | array | yes | — |
| max_usd | number | no | — |
How buyers would ask an AI assistant for what the user makes: ChatGPT, Claude and Gemini each write count questions without searching the web. what: what the user makes, the way a buyer would put it. Paid (AIsa):
| Parameter | Type | Required | Notes |
|---|---|---|---|
| what | string | yes | — |
| count | integer | no | — |
| max_usd | number | no | — |
The user's questions put to ChatGPT, Google's AI Mode, Perplexity, Claude and Gemini: what each searched for, the pages it cited, the tools it named and whether it named or cited the user; then the sites and pages cited most. names: other names the answers may call the user by. rank: also look up…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | — |
| questions | array | yes | — |
| names | array | no | — |
| rank | boolean | no | — |
| max_usd | number | no | — |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Backlink Guard or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 0.11.2 · scanned 31 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest7daa508a3807a1006b9089af98155463f4b6a865f8ec47975b1c233959d3e654
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| verify | no tags | |
| submissions | no tags | |
| vet | no tags | |
| find | no tags | |
| audit | no tags | |
| lost | no tags | |
| competitors | no tags | |
| cited | no tags | |
| questions | no tags | |
| asked | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest7daa508a3807a100
Scanned2026-10-31
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.11.2. Pin a release below and the command asks for exactly that one.
0.11.2
31 Oct 2026
latestNo release note was published with this version.
0.11.1
28 Oct 2026
No release note was published with this version.
0.11.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Backlink Guard can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.