Home · Setup · Cursor

MCP Backlink Checker in Cursor

Check backlinks from a chat: does a page link to your domain, dofollow or nofollow, anchor text and robots guards. You give it referring page URLs and a target domain. link_check fetches one page and reports whether it links to the domain, dofollow or nofollow, the anchor text, HTTP status and page-level robots guards (meta robots and X-Robots-Tag noindex/nofollow). link_audit runs the same check across a list of URLs and returns one table row per link found. robots_guard_check reports just the robots signals on a URL without extracting links. The server makes one outbound GET per URL and stores nothing.

Cursor's agent can interleave link checks with the codebase work that earned the links, so the sentence is one turn: ship the page, then check it landed as dofollow.

What you get in Cursor

You say	Tool
Check whether https://example.com/blog/roundup links to mydomain.com and if it is dofollow.	`link_check`
Audit these 20 guest-post pages against mydomain.com.	`link_audit`
Is that link page even indexable, or is it noindexed?	`robots_guard_check`

The suite is 8 tests, 8 passing, 0 failing (node --test), covering link extraction and classification, rel-splitting, page-level robots guards and the Pro gate on batch size. The smoke and license-gate tests sit alongside it.

Install it in Cursor

The file is .cursor/mcp.json, and the key inside it is mcpServers.

Scope	Path
This project only	`<project>/.cursor/mcp.json`
Every project	`~/.cursor/mcp.json`

If you also run Claude Desktop, the shortest path there is one click: backlink-checker.mcpb from the latest release opens as an extension, with no JSON and no terminal. Cursor reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "backlink-checker": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/backlink-checker/dist/index.js"]
    }
  }
}

The node command above wants a built file. From a clone, once:

git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/backlink-checker

That writes servers/backlink-checker/dist/index.js, and its absolute path is the one argument the config needs.

The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:

{
  "mcpServers": {
    "backlink-checker": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-backlink-checker"]
    }
  }
}

The Customize page shows the server and its tools once it has started.

Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the latest release, a clone and build, or the hosted URL.

No install: the hosted endpoint

The same server runs at https://mcp.zovo.one/mcp/backlink-checker over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.

{
  "mcpServers": {
    "backlink-checker": {
      "url": "https://mcp.zovo.one/mcp/backlink-checker",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Cursor notes worth knowing first

The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.

Free: link_check and robots_guard_check are free and unlimited; link_audit covers up to 3 URLs per call on the free tier. Reads are free on every tier. Pro is $19 once, verified offline.

Questions

Project config or global config?

<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.

Why does my stdio entry not start?

The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.

Is there a one-click install link?

Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Backlink Checker pasting the config block above is the supported route.

MCP Backlink Checker in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro