Back to Browse

Seo MCP Server

Developer ToolsUse Caution4.8MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

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

About

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

Security Report

4.8
Use Caution4.8High Risk

This is a well-structured MCP server for SEODesignLab's x402-protected SEO endpoints. Authentication is handled via environment-configured wallet addresses and x402 payment headers rather than traditional API keys. Code is clean with proper input validation using Zod, appropriate error handling, and permissions that align with its purpose as a developer tool for SEO API access. No malicious patterns, hardcoded credentials, or dangerous operations detected. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

3 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub README.

@seodesignlab/mcp-server

MCP (Model Context Protocol) server for SEODesignLab's x402-protected SEO endpoints.

Expose professional SEO tools — content briefs, keyword research, SERP analysis, backlink profiles, and on-page audits — to any MCP-compatible AI agent (Claude Desktop, Cursor, VS Code Copilot, etc.) with automatic x402 micropayment handling on Base.


Tools

ToolEndpointPriceDescription
get_content_brief/api/briefs/$2.00Generate a POP content brief with keyword analysis, LSI terms, and content structure
keyword_research/api/dataforseo/keywords/$1.50Search volume, CPC, and competition difficulty for a keyword
serp_analysis/api/dataforseo/serp/$2.00Top 10 organic results with domain metrics and SERP features
backlink_profile/api/dataforseo/backlinks/$3.00Referring domains, link metrics, and anchor text distribution
on_page_audit/api/dataforseo/audit/$2.50Full on-page SEO audit — meta, headings, images, links, speed

All prices are in USDC on Base and settled via the x402 protocol.


Quick Start

Install

npm install @seodesignlab/mcp-server
# or
npx @seodesignlab/mcp-server

Environment Variables

VariableDefaultDescription
SEO_API_BASEhttps://seodesignlab-paywall.seodesignlab.workers.devBase URL of the SEO API (CF Worker paywall)
X402_PAY_TO(none)Base wallet address for x402 payments. When set, payment headers are attached automatically.
X402_NETWORKbaseNetwork for x402 settlement

Configuration

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "seodesignlab-seo": {
      "command": "npx",
      "args": ["-y", "@seodesignlab/mcp-server"],
      "env": {
        "SEO_API_BASE": "https://seodesignlab-paywall.seodesignlab.workers.dev",
        "X402_PAY_TO": "0xc78e3D02622061961156a18E10bbbF07d8e94529",
        "X402_NETWORK": "base"
      }
    }
  }
}

Config file locations:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Cursor

Add to your Cursor MCP settings (.cursor/mcp.json in your project root or global settings):

{
  "mcpServers": {
    "seodesignlab-seo": {
      "command": "npx",
      "args": ["-y", "@seodesignlab/mcp-server"],
      "env": {
        "SEO_API_BASE": "https://seodesignlab-paywall.seodesignlab.workers.dev",
        "X402_PAY_TO": "0xc78e3D02622061961156a18E10bbbF07d8e94529",
        "X402_NETWORK": "base"
      }
    }
  }
}

VS Code (Copilot)

Add to your VS Code MCP settings (.vscode/mcp.json):

{
  "servers": {
    "seodesignlab-seo": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@seodesignlab/mcp-server"],
      "env": {
        "SEO_API_BASE": "https://seodesignlab-paywall.seodesignlab.workers.dev",
        "X402_PAY_TO": "0xc78e3D02622061961156a18E10bbbF07d8e94529",
        "X402_NETWORK": "base"
      }
    }
  }
}

Usage Examples

Once configured, the SEO tools appear automatically in your AI agent. Just ask:

Content Brief

Generate a content brief for "HVAC repair Brooklyn"

→ Calls get_content_brief → Returns POP brief with LSI terms, word count targets, heading structure.

Keyword Research

What's the search volume and CPC for "roofing contractor Tampa"?

→ Calls keyword_research → Returns monthly volume, CPC, competition score.

SERP Analysis

Show me the top 10 results for "dentist near me" in Rockville Centre

→ Calls serp_analysis → Returns top 10 results with domain authority, titles, descriptions.

Backlink Profile

Analyze the backlink profile of seodesignlab.com

→ Calls backlink_profile → Returns referring domains, link counts, domain rating.

On-Page Audit

Audit https://drbrattrvc.com/services/teeth-whitening/

→ Calls on_page_audit → Returns meta analysis, heading structure, image coverage, technical issues.


x402 Payment Flow

AI Agent (Claude, Cursor, etc.)
    │
    ▼
MCP Server (this package)
    │
    ▼  Adds X-Payment-* headers
Cloudflare Worker (x402 paywall)
    │
    ├── Payment valid? ──► YES ──► Proxy to SEO API ──► Return data
    │
    └── No payment? ──► 402 + x402 settlement instructions

When X402_PAY_TO is configured, the MCP server attaches payment headers to every request. The Cloudflare Worker validates the x402 payment and either:

  1. Paid → Forwards the request to the SEO backend on Render, returns the result.
  2. Unpaid → Returns a 402 Payment Required with the price, wallet address, and settlement instructions.

x402 Client Integration

For production use, pair this MCP server with an x402-compatible client that can automatically settle micropayments. The server is designed to be payment-agnostic — it works with or without an x402 client.


API Endpoints

The MCP server proxies to these backend endpoints at SEO_API_BASE:

POST /api/briefs/

Request:

{
  "keyword": "HVAC repair Brooklyn",
  "location": "United States",
  "language": "en"
}

Response: Full POP content brief with keyword analysis, LSI terms, recommended structure.

POST /api/dataforseo/keywords/

Request:

{
  "keyword": "roofing contractor Tampa",
  "location": "United States",
  "language": "en"
}

Response: Search volume, CPC, competition, related keywords.

POST /api/dataforseo/serp/

Request:

{
  "keyword": "dentist near me",
  "location": "United States",
  "language": "en"
}

Response: Top 10 organic results with titles, URLs, descriptions, and domain metrics.

POST /api/dataforseo/backlinks/

Request:

{
  "domain": "seodesignlab.com"
}

Response: Referring domains, backlinks count, domain rating, anchor distribution.

POST /api/dataforseo/audit/

Request:

{
  "url": "https://drbrattrvc.com/services/teeth-whitening/"
}

Response: Meta title/description analysis, heading structure, image alt coverage, link counts, page speed, content quality, technical issues.


Development

# Install dependencies
npm install

# Build
npm run build

# Run locally (stdio transport)
npm run dev

# Type check
npx tsc --noEmit

Testing with MCP Inspector

npx @modelcontextprotocol/inspector node dist/index.js

Publishing

⚠️ Don't publish yet! Wait until the Cloudflare Worker paywall is deployed and live.

When ready:

npm run build
npm publish --access public

License

MIT © SEODesignLab

Reviews

No reviews yet

Be the first to review this server!