Linkguard Mcp

ai.linkguardPublished by linkguard.aiv0.1.0Updated Oct 24, 2026

Backlink tools for AI assistants: redirect, Google index, and backlink health checks.

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

A local MCP server that gives AI assistants backlink health checks, including redirect and Google index status, via the Linkguard API.

What you can do
Run backlink health checks on links and domains from an assistant conversation, covering redirect and Google index status. Results come from the Linkguard API, so the assistant can report on link quality without leaving the chat. No individual tools are listed in the supplied material, so exact operations are not documented here.
When to use it
Useful when you audit backlinks or outbound links and want an assistant to check redirects and Google index status while discussing link health. It suits SEO or site-maintenance work that already uses Linkguard.
Requirements
Runs as a local process installed from the PyPI package linkguard-mcp over stdio, so a Python environment is needed. Requires a Linkguard API key supplied in the LINKGUARD_API_KEY environment variable; the key is obtained from the Linkguard dashboard and requires a paid top-up. Network access to the Linkguard API is needed, and LINKGUARD_API_URL can override the default base URL.
Before you install
The server needs a secret API key in LINKGUARD_API_KEY, and obtaining it requires a paid top-up, so using it involves spending money. The key is sent to the Linkguard service, and link or domain queries are shared with that third party. LINKGUARD_API_URL can point the server at a different endpoint, so only change it to a trusted address.

Installation

In SourceWeft

  1. Open Linkguard Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.