LinkGuard MCP server: a backlink checker for Claude
Checking a backlink shouldn't mean leaving what you're writing. Connect the LinkGuard MCP server and ask Claude, in plain language: is this link live, dofollow, indexed in Google, or stuck in a redirect chain? The answer comes from your own LinkGuard account, in the same window.
What is an MCP backlink checker?
An MCP backlink checker is an MCP server that gives an AI assistant tools to inspect backlinks. This SEO MCP server hands Claude three tools and lets it pick the right one from your question. You just describe the link you care about.
- redirect_check traces a URL through every redirect hop and flags the SEO impact on link equity. "Trace the redirects on this link."
- backlink_index_check checks whether a page is in Google's index and returns the SERP snippet when there is one. "Is this backlink indexed in Google?"
- backlink_health_snapshot gives the full verdict in one call: live status, dofollow vs nofollow, indexation, canonical integrity, plus a score and the fixes. "Is this backlink still working?"
How to check backlinks from Claude
-
Get an API key. Create a free account, top up once to unlock API
access (the smallest top-up is $25), then open
Dashboard → API Keys and generate a key. It starts
with
lg_and is shown once. -
Add the server to your client. Paste the config below (Claude Desktop)
or run the command (Claude Code), with your key in place of
lg_your_key_here. - Restart and ask. Restart the client, then ask it to check a backlink. LinkGuard shows up in the tools panel.
Claude Desktop
Add this to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"linkguard": {
"command": "uvx",
"args": ["linkguard-mcp"],
"env": {
"LINKGUARD_API_KEY": "lg_your_key_here"
}
}
}
}
Claude Code
claude mcp add linkguard -- uvx linkguard-mcp
Then export your key before starting a session (or add it to your shell profile):
export LINKGUARD_API_KEY=lg_your_key_here
The server runs via uvx (from uv),
so there is nothing to install by hand. The package is fetched on first run.
What it costs
Pricing matches the web app. redirect_check and backlink_index_check are free on every call. backlink_health_snapshot is free too, except when a donor page is JavaScript-heavy and has to render in a real cloud browser. That single run costs 5 tokens, the same as on the website.
One thing differs from the web tools: MCP needs one top-up before it works, and the smallest top-up is $25. We're upfront about why. MCP is a programmatic channel; an assistant can call it in a loop. The gate stops automated usage from burning through the free signup-bonus tokens we keep for people trying the browser tools. Once you've topped up once, the free tools stay free per call.
If you only check a link now and then, you don't need any of this. The free web tools run the same checks with no setup at all.
Frequently asked questions
What is an MCP backlink checker?
An MCP backlink checker is an MCP server that gives an AI assistant tools to inspect backlinks. MCP (Model Context Protocol) is an open standard for letting assistants call external tools mid-conversation. The LinkGuard server hands Claude three backlink tools, so you can ask it to check a link instead of leaving the chat.
Which AI clients does it work with?
Any MCP-compatible client. It is tested with Claude Desktop and Claude Code, which run the server over stdio. The same package works in other clients that support stdio MCP servers.
Do I have to pay to use the MCP server?
You need a LinkGuard account and one top-up to unlock API access. The smallest top-up is $25. After that, redirect-check and index-check are free per call; backlink-health costs 5 tokens only on a real-browser render.
Why does MCP require a top-up first?
To stop a runaway agent loop from eating the free signup tokens we reserve for people trying the web tools. The smallest top-up ($25) clears the gate for good, and per-call pricing does not change after that.
What does each call cost in tokens?
Same as the web app: redirect_check and backlink_index_check are free; backlink_health_snapshot costs 5 tokens only when it has to render a page in a real browser.
What does the MCP server store about my checks?
The package stores nothing on your machine. The API logs anonymous usage metrics for analytics: which tool you ran, a hashed IP, timing, and the domain you checked (the hostname only, never the full URL or the page content).
How is this different from the free web tools?
Same checks, different place. The web tools run in your browser; the MCP server runs the same checks inside your AI assistant, against your account, so you can ask in plain language and keep working in one window.
Where do I get an API key?
Create a free account, top up once to unlock API access, then open Dashboard → API Keys and generate a key. Keys start with lg_ and are shown once.
Last updated: 2026-05-21