Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
BACKLNK 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.
93/100
tool-list score
6
tools declared
remote
at its publisher
—
calls last 7d
What it does
Free technical SEO, AEO, LLMO and GEO checks for AI agents: check a page, fix it, verify the fix.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http backlnk-mcp https://backlnk.com/mcp --header 'Authorization: Bearer ${BACKLNK_API_KEY}'
# 2 — ask your agent for something these tools do
# list_checks, run_checks, get_report and 3 more
It needs BACKLNK_API_KEY (Your free BACKLNK API key (bk_...), from https://backlnk.com/developers): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.
BACKLNK costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BAAll 1 server
backlnk1 server
1 category
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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads BACKLNK_API_KEY (Your free BACKLNK API key (bk_...), from https://backlnk.com/developers) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx BACKLNK_API_KEY … and open a new terminal (Windows).
claude mcp add --scope user --transport http backlnk-mcp https://backlnk.com/mcp --header 'Authorization: Bearer ${BACKLNK_API_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Your free BACKLNK API key (bk_...), from https://backlnk.com/developers. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 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.
Lists every check BACKLNK can run (id, what it looks at, its scope and limits). Use the ids with run_checks.
No parameter schema on file.
Runs BACKLNK checks on one public URL and waits up to about 40 seconds. Returns, per check, its state, summary, counts and the issues and warnings to fix (most important first, with evidence and a recommendation), plus the audit ids for get_report and verify_fixes. Default checks: meta-tags, page-structure, ai-crawler-access, redirects-headers, entity-schema.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Public page or website URL, e.g. https://example.com/pricing |
| checks | array | no | Check ids (see list_checks). Omit for the quick default set. |
| mode | string | no | Source reads the HTML as served; Rendered runs JavaScript first; Auto decides per page. |
| fresh | boolean | no | Re-run even if the same check ran on this URL very recently (default false). |
Returns the compact report of an earlier check: state, summary, counts and findings (detail "actions": issues and warnings only, the default; "all": every finding).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | yes | Audit id returned by run_checks (a UUID). |
| detail | string | no | Default "actions". |
After the fixes are deployed: re-runs the same check fresh on the same URL and options, waits up to about 40 seconds and returns the comparison with the original run: fixed, new, still open and not re-checked findings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | yes | Audit id returned by run_checks (a UUID). |
Builds robots.txt lines that allow or block AI crawlers from BACKLNK's reviewed crawler catalog, with what each line does and warnings. Use a preset (block-training: Block AI training, stay in AI search; block-ai: Block AI crawlers, keep search engines; allow-all: Allow every crawler) or decide per purpose and per crawler token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| preset | string | no | — |
| purposes | object | no | Decision per purpose; purposes not named stay allowed when no preset is given. |
| crawlers | object | no | Per-crawler overrides by token, e.g. { "GPTBot": "allow" }. |
How many checks this API key has used and has left today and this hour.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 BACKLNK 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: —
ATool-list grade · score 93 / 100
Release 1.0.3 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
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 score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest81494ce9c7124b4f8cd2d0b0c51e1751ae29482a34b74b0f154415bbf9059d27
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_checks | no tags | |
| run_checks | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_report | no tags | |
| verify_fixes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ai_crawler_policy | no tags | |
| usage | 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 digest81494ce9c7124b4f
Scanned2026-11-07
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.3.
1.0.3
undated
latestNo release note was published with this version.
—
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 BACKLNK 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.