Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mouhabmzibra-rgb/seo-backlinks

NPM · SEO-BACKLINKS-MCP · SCANNED SEP 21

Backlinks, Domain Rating & expired-domain drops via seo-backlinks.net (Common Crawl)

Available components

0 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 402 tokens (~80/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.mouhabmzibra-rgb/seo-backlinks MCP server?

io.github.mouhabmzibra-rgb/seo-backlinks runs locally as an npm package, launched with npx -y seo-backlinks-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · seo-backlinks-mcp

# add to Claude Code
claude mcp add mouhabmzibra-rgb-seo-backlinks -- npx -y seo-backlinks-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "mouhabmzibra-rgb-seo-backlinks": {
      "command": "npx",
      "args": [
        "-y",
        "seo-backlinks-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mouhabmzibra-rgb-seo-backlinks": {
      "command": "npx",
      "args": [
        "-y",
        "seo-backlinks-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mouhabmzibra-rgb-seo-backlinks -- npx -y seo-backlinks-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mouhabmzibra-rgb-seo-backlinks": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "seo-backlinks-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mouhabmzibra-rgb-seo-backlinks --command npx --arg -y --arg seo-backlinks-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mouhabmzibra-rgb-seo-backlinks:
    command: "npx"
    args: ["-y", "seo-backlinks-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mouhabmzibra-rgb-seo-backlinks": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "seo-backlinks-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mouhabmzibra-rgb-seo-backlinks -t stdio -c npx -a -y seo-backlinks-mcp
// mcp.json
{
  "mcpServers": {
    "mouhabmzibra-rgb-seo-backlinks": {
      "command": "npx",
      "args": [
        "-y",
        "seo-backlinks-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −4
    • Stability: pass → 0.77 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/seo-backlinks-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~402 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_domain ~114

Check backlink authority for any domain. Returns Domain Rating (DR 0-100), harmonic centrality rank, PageRank, and total referring domains count. Data comes from Common Crawl (4.3B backlinks indexed, 262M hosts). Use this when the user asks about a site's backlink profile, authority, or wants to compare domains.

NameTypeReqDescription
domainstringyesThe domain to check (e.g., 'nytimes.com', 'openai.com'). Omit protocol and 'www.' prefix — they're stripped automatically.

No output schema declared.

No examples provided.

get_domain_info ~47

Get detailed sitemap-style info for a domain: metadata, page count, content categories, and structural info. Useful for on-page SEO audits.

NameTypeReqDescription
domainstringyesDomain to inspect

No output schema declared.

No examples provided.

get_expired_domains ~83

Get today's freshly-expired domains that have real backlinks. Useful for domain investors, PBN builders, and content marketers hunting for aged domains with existing authority. Returns rank + backlink count for each drop.

NameTypeReqDescription
datestringDate in YYYY-MM-DD format (default: latest available)
limitnumberMax drops to return (default 20)

No output schema declared.

No examples provided.

get_referring_domains ~97

List domains that link TO the target domain, sorted by authority. Returns backlinks with anchor context and rank of each referring site. Use this when the user wants to see WHO links to a site, do competitor research, or find link-building opportunities.

NameTypeReqDescription
domainstringyesTarget domain (e.g., 'stripe.com')
limitnumberNumber of referring domains to return (default 10, max depends on plan)

No output schema declared.

No examples provided.

get_top_hosts ~61

Get the top-ranked hosts across the entire web (from Common Crawl). Useful for research, comparison baselines, or finding top players in a niche.

NameTypeReqDescription
limitnumberNumber of top hosts to return (default 25, max 1000)

No output schema declared.

No examples provided.

Common questions

What is the io.github.mouhabmzibra-rgb/seo-backlinks MCP server?

io.github.mouhabmzibra-rgb/seo-backlinks is an MCP server listed in the public MCP registry as io.github.mouhabmzibra-rgb/seo-backlinks. Backlinks, Domain Rating & expired-domain drops via seo-backlinks.net (Common Crawl). This page covers its npm package (seo-backlinks-mcp).

Is the io.github.mouhabmzibra-rgb/seo-backlinks MCP server safe to use?

io.github.mouhabmzibra-rgb/seo-backlinks scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.mouhabmzibra-rgb/seo-backlinks MCP server expose?

io.github.mouhabmzibra-rgb/seo-backlinks exposes 5 tools: check_domain, get_referring_domains, get_domain_info, get_expired_domains, get_top_hosts. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.

Is the io.github.mouhabmzibra-rgb/seo-backlinks MCP server still maintained?

io.github.mouhabmzibra-rgb/seo-backlinks is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.mouhabmzibra-rgb/seo-backlinks MCP server under?

io.github.mouhabmzibra-rgb/seo-backlinks declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.