Backlink Checker: Referring Domains & Anchor Text

io.github.NadaHoPublished by GitHub account NadaHov1.0.0Updated Oct 29, 2026

Bulk backlinks of any domain or URL: anchors, dofollow, spam score, referring domains.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Apify-hosted remote MCP server that lets an assistant pull bulk backlink data for any domain or URL, including anchors, dofollow status, spam score and…

What you can do
  • Retrieve bulk backlinks for a domain or URL
  • Inspect anchor text, dofollow status and spam score of links
  • List referring domains behind a target site
  • No individual tools are documented; the server is described only as a backlink lookup for domains and URLs
When to use it
Useful for SEO or link-profile research when you want an assistant to gather backlink and referring-domain data for a site inside a conversation, without building your own crawler or API integration.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. Authentication is required: an Authorization header with an Apify API token, or OAuth sign-in to Apify for clients that support it. An Apify account is needed, and runs are billed to it.
Before you install
Runs are billed to your Apify account, so repeated lookups cost money. The Authorization header carries an Apify API token, which should be kept secret. Queries about a domain are sent to Apify's hosted service.

Installation

In SourceWeft

  1. Open Backlink Checker: Referring Domains & Anchor Text in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.NadaHo%2Fbacklink-checker/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "backlink-checker-referring-domains-ancho": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=plainrows/backlink-checker"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.