Linkguard Mcp

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

Linkguard MCP is a Model Context Protocol server that provides AI assistants with backlink auditing capabilities. It is distributed as a Python package on PyPI at version 0.1.0 and communicates over stdio transport, making it suitable for local agent workflows that support that transport.

The server is configured through two environment variables: LINKGUARD_API_KEY, which authenticates requests to the Linkguard API, and LINKGUARD_API_URL, which points to the API endpoint. Both must be set before the server can function.

The package description states the server covers three functional areas. First, it checks redirect chains on URLs, which is useful for detecting broken or misconfigured redirects that can harm backlink equity. Second, it verifies whether URLs are indexed by Google, allowing an agent to identify pages that have been de-indexed. Third, it assesses the overall health of backlinks, supporting programmatic audits of a site’s link profile without manual URL-by-URL review.

These three capabilities make the server relevant to SEO-focused agent workflows. An agent can call the server to audit large sets of backlinks, flag redirect issues, or confirm indexation status as part of a broader content or site-health pipeline.

No tool definitions were included in the published metadata, so the exact callable interface cannot be described in further detail here. Access requires a valid Linkguard API key, meaning a Linkguard account is a prerequisite. The server is not appropriate for database queries, general web scraping, or any task outside backlink and indexation auditing.

Use cases

  • Check whether a list of backlink URLs have been indexed by Google
  • Detect redirect chains on inbound links that may dilute link equity
  • Audit backlink health as part of an automated SEO monitoring workflow
  • Identify de-indexed or redirected pages across a link profile
  • Integrate backlink health checks into a site-quality agent pipeline

When to use it

  • When an AI agent needs to audit backlink health programmatically
  • When verifying Google index status for a set of URLs
  • When detecting redirect issues on inbound links at scale
  • When the host environment supports stdio MCP transport

When not to use it

  • When no Linkguard API key is available, as authentication is required
  • When the agent runtime does not support stdio transport
  • When the task involves general web crawling or scraping unrelated to backlinks
  • When database connectivity such as Postgres is the actual requirement
  • When a full-featured SEO platform with its own UI is preferred over an API-driven agent tool