Skip to content

VS Code backlink checker link_audit

How to: VS Code backlink checker link_audit

client:VS Code transport:streamable-http tool:link_audit

Add backlink checker to VS Code

  1. 01

    Open .vscode/mcp.json and merge this in. Keep any servers already there.

{
  "servers": {
    "backlink-checker": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/backlink-checker"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

    Ask for something link_audit does. VS Code lists the server's tools on connect and calls link_audit itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that backlink checker's identifier in your config matches the one above exactly.

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Set these first

backlink checker will not start until these are set, so link_audit never becomes available.

  • MCP_LICENSE_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.