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.SEODesignLab/seo-tools

NPM · @SEODESIGNLAB/MCP-SERVER · SCANNED SEP 21

SEO tools via x402: briefs, keywords, SERP, backlinks, audits. $0.50-$3/req USDC on Base.

Available components

npm · @seodesignlab/mcp-server 84
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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 530 tokens (~106/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 Management97
  • Stability observed for 29 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.SEODesignLab/seo-tools MCP server?

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

npm · @seodesignlab/mcp-server

# add to Claude Code
claude mcp add seodesignlab-seo-tools -- npx -y @seodesignlab/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "seodesignlab-seo-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@seodesignlab/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "seodesignlab-seo-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@seodesignlab/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add seodesignlab-seo-tools -- npx -y @seodesignlab/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "seodesignlab-seo-tools": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@seodesignlab/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add seodesignlab-seo-tools --command npx --arg -y --arg @seodesignlab/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  seodesignlab-seo-tools:
    command: "npx"
    args: ["-y", "@seodesignlab/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "seodesignlab-seo-tools": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@seodesignlab/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add seodesignlab-seo-tools -t stdio -c npx -a -y @seodesignlab/mcp-server
// mcp.json
{
  "mcpServers": {
    "seodesignlab-seo-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@seodesignlab/mcp-server"
      ]
    }
  }
}
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.

  • 20 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.

  • 18 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 −3
    • Stability: pass → 0.83 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 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.

  • 13 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 12 Sept 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 9 Sept 26 −3
    • Stability: pass → 0.77 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/@seodesignlab/mcp-server@1.0.4

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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~530 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
backlink_profile ~88

Get the backlink profile for a domain — referring domains, link metrics, and anchor text analysis. Price: $3.00 (x402 on Base) Returns: - Referring domains count - Backlinks count - Domain rating / authority - Top referring domains with link metrics - Anchor text distribution

NameTypeReqDescription
domainstringyesDomain to analyze (e.g. 'example.com')

No output schema declared.

No examples provided.

get_content_brief ~125

Generate a POP (PageOptimizer Pro) content brief for a target keyword. Price: $2.00 (x402 on Base) Returns a detailed content brief including: - Target keyword analysis - Recommended word count and headings - LSI terms and semantic keywords - Title and meta description suggestions - Content structure guidelines

NameTypeReqDescription
keywordstringyesTarget keyword for the content brief
languagestring–Language code (default: 'en')
locationstring–Optional location/geo targeting (e.g. 'United States', 'Florida')

No output schema declared.

No examples provided.

keyword_research ~101

Research keyword metrics including search volume, CPC, and competition difficulty. Price: $1.50 (x402 on Base) Returns: - Monthly search volume - Cost per click (CPC) - Competition level / difficulty - Related keyword suggestions

NameTypeReqDescription
keywordstringyesTarget keyword to research
languagestring–Language code (default: 'en')
locationstring–Geo target (e.g. 'United States')

No output schema declared.

No examples provided.

on_page_audit ~100

Run a comprehensive on-page SEO audit for a URL. Price: $2.50 (x402 on Base) Returns: - Meta title and description analysis - Heading structure (H1-H6) - Image alt text coverage - Internal/external link counts - Page speed insights - Content quality metrics - Technical SEO issues

NameTypeReqDescription
urlstringyesFull URL to audit (e.g. 'https://example.com/page')

No output schema declared.

No examples provided.

serp_analysis ~116

Analyze the top 10 SERP results for a keyword with metrics. Price: $2.00 (x402 on Base) Returns: - Top 10 organic results with URLs - Domain authority / rating for each - Title and description snippets - SERP feature detection (featured snippets, PAA, etc.)

NameTypeReqDescription
keywordstringyesTarget keyword for SERP analysis
languagestring–Language code (default: 'en')
locationstring–Geo target (e.g. 'United States')

No output schema declared.

No examples provided.

Common questions

What is the io.github.SEODesignLab/seo-tools MCP server?

io.github.SEODesignLab/seo-tools is an MCP server listed in the public MCP registry as io.github.SEODesignLab/seo-tools. SEO tools via x402: briefs, keywords, SERP, backlinks, audits. $0.50-$3/req USDC on Base. This page covers its npm package (@seodesignlab/mcp-server).

Is the io.github.SEODesignLab/seo-tools MCP server safe to use?

io.github.SEODesignLab/seo-tools 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.SEODesignLab/seo-tools MCP server expose?

io.github.SEODesignLab/seo-tools exposes 5 tools: get_content_brief, keyword_research, serp_analysis, backlink_profile, on_page_audit. Their descriptions and schemas cost roughly 530 tokens of context every time the server is loaded.

Is the io.github.SEODesignLab/seo-tools MCP server still maintained?

io.github.SEODesignLab/seo-tools 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.SEODesignLab/seo-tools MCP server under?

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