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.

SEOPro AI

REMOTE · API.SEOPROAI.CO · SCANNED SEP 28

Turn Search Console data into SEO actions, content, publishing, indexing, and AI insights.

Available components

+3 this week 89 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1640 tokens (~71/item across 23 items; 18 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 20 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 SEOPro AI MCP server?

SEOPro AI is a hosted endpoint at https://api.seoproai.co/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.seoproai.co

# add to Claude Code
claude mcp add --transport http alpha-ai-labs-seo-agent 'https://api.seoproai.co/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "alpha-ai-labs-seo-agent": {
      "url": "https://api.seoproai.co/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "alpha-ai-labs-seo-agent": {
      "type": "http",
      "url": "https://api.seoproai.co/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.alpha-ai-labs-seo-agent]
url = "https://api.seoproai.co/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alpha-ai-labs-seo-agent": {
      "type": "remote",
      "url": "https://api.seoproai.co/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add alpha-ai-labs-seo-agent --url 'https://api.seoproai.co/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  alpha-ai-labs-seo-agent:
    url: "https://api.seoproai.co/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "alpha-ai-labs-seo-agent": {
      "Transport": "http",
      "Url": "https://api.seoproai.co/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add alpha-ai-labs-seo-agent -t streamable-http -u 'https://api.seoproai.co/api/mcp'
// mcp.json
{
  "mcpServers": {
    "alpha-ai-labs-seo-agent": {
      "type": "http",
      "url": "https://api.seoproai.co/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

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

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

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 28 Sept 2026 · Probed https://api.seoproai.co/api/mcp

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.seoproai.co CN=Amazon RSA 2048 M01,O=Amazon,C=US 14 Sept 2026 30 Mar 2027 RSA 2048 SHA256-RSA a1095c88f0284ccc1fb074c977f4104
SANs: api.seoproai.co, 2a57j77ubhgu6usx8dkhw6zu4n39wq9.api.seoproai.co
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.seoproai.co. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
seoproai.co. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://api.seoproai.co/.well-known/oauth-protected-resource/api/mcp"

Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://api.seoproai.co/.well-known/oauth-protected-resource/api/mcp"

Protected resource metadata

Document https://api.seoproai.co/.well-known/oauth-protected-resource/api/mcp
Retrieved Yes
Resource https://api.seoproai.co/api/mcp
Authorisation server https://dajosjnaalanhqksxrpe.supabase.co/auth/v1

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.seoproai.co/api/mcp Verified 200
http (plaintext) http://api.seoproai.co/api/mcp HTTPS enforced 301 https://api.seoproai.co:443/api/mcp
MCP tools · 18 exposed · ~1,285 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_ai_citations ~62

Check whether AI assistants (ChatGPT, Claude, Gemini, Perplexity) mention or cite a website when answering questions in its niche. Takes 1-3 minutes; results are cached for 7 days.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

generate_article ~126

Start generating an SEO article for a target keyword. Returns immediately; generation takes 5-10 minutes in the background — poll get_article_status for the scheduled_date until it shows a blog. scheduled_date is YYYY-MM-DD and defaults to today (UTC). One article is generated per website per date; if that date already has an article the existing blog_id is returned. Counts toward the plan's monthly limit.

NameTypeReqDescription
keywordstringyes–
scheduled_date–––
topic–––
website_idintegeryes–

No output schema declared.

No examples provided.

generate_keyword_plan ~120

Generate an AI keyword/content plan for the website. Optionally guide it with topic instructions and comma-separated primary/secondary keywords. Can take a minute or two. Set replace_existing=true only after the user explicitly approves discarding the current plan's pending topics; that path also requires confirm_replace_existing=true.

NameTypeReqDescription
confirm_replace_existingboolean––
primary_keywords–––
replace_existingboolean––
secondary_keywords–––
topic_instructions–––
website_idintegeryes–

No output schema declared.

No examples provided.

get_ai_search_traffic ~91

Show traffic the website receives from AI assistants and AI search (ChatGPT, Perplexity, Claude, Gemini, etc.): sessions, engaged pages and per-source breakdowns. Dates are YYYY-MM-DD; defaults to the last 30 days.

NameTypeReqDescription
end_date–––
limitinteger––
start_date–––
website_idintegeryes–

No output schema declared.

No examples provided.

get_article ~53

Read a single article by blog_id. By default returns metadata and a short excerpt; set include_content=true for the full HTML content.

NameTypeReqDescription
blog_idintegeryes–
include_contentboolean––

No output schema declared.

No examples provided.

get_article_status ~75

Check article generation/publication status per date. Dates are YYYY-MM-DD and default to the current month. A date with has_blog=true and a blog_id means the article is ready to read via get_article.

NameTypeReqDescription
end_date–––
start_date–––
website_idintegeryes–

No output schema declared.

No examples provided.

get_backlink_profile ~50

Get the website's backlink profile from the SEOPro AI backlink network: totals, unique sources, available credits and the most recent earned backlinks.

NameTypeReqDescription
website_idintegeryes–

No output schema declared.

No examples provided.

get_indexing_status ~38

Get auto-indexing stats for the website: how many URLs are indexed, pending or failed.

NameTypeReqDescription
website_idintegeryes–

No output schema declared.

No examples provided.

get_keyword_plan ~39

Get the website's scheduled keyword/content plan: which keywords are planned, their scheduled dates and statuses.

NameTypeReqDescription
website_idintegeryes–

No output schema declared.

No examples provided.

get_search_performance ~84

Get the Google Search Console performance summary for a website: clicks, impressions, CTR, average position, top keywords, AI-assistant traffic sources and device/country breakdowns. Dates are YYYY-MM-DD; defaults to the last 30 days.

NameTypeReqDescription
end_date–––
start_date–––
website_idintegeryes–

No output schema declared.

No examples provided.

get_search_trends ~55

Get monthly search-performance trends (clicks, impressions, CTR, average position) for the last N months. Use to spot growth or decay.

NameTypeReqDescription
monthsinteger––
website_idintegeryes–

No output schema declared.

No examples provided.

get_top_search_keywords ~87

List the website's top search keywords with clicks, impressions, CTR and average position. Great for finding quick wins (positions 5-15 with high impressions). Dates are YYYY-MM-DD; defaults to the last 30 days.

NameTypeReqDescription
end_date–––
limitinteger––
start_date–––
website_idintegeryes–

No output schema declared.

No examples provided.

get_website_stats ~42

Get content stats for a website: total articles, keywords tracked, published posts and whether SEO autopilot is enabled.

NameTypeReqDescription
website_idintegeryes–

No output schema declared.

No examples provided.

list_articles ~58

List the website's articles (drafts and published), newest first. Optionally filter by status (e.g. 'draft', 'published').

NameTypeReqDescription
limitinteger––
status–––
website_idintegeryes–

No output schema declared.

No examples provided.

list_websites ~49

List the websites in the user's SEOPro AI account. Returns each website's numeric website_id (needed by most other tools), URL, platform and autopilot status. Call this first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

publish_article ~104

Publish an article to the website's connected platform (WordPress, Shopify, Webflow, etc.). Set publish_as_draft=true to push it as an unpublished draft in the CMS instead of going live. Before calling, show the user the article and destination and obtain explicit approval. Every call requires confirm_publish=true.

NameTypeReqDescription
blog_idintegeryes–
confirm_publishboolean––
publish_as_draftboolean––

No output schema declared.

No examples provided.

request_indexing ~91

Submit up to 50 URLs for search-engine indexing (Google/Bing) via SEOPro AI auto-indexing. Requires the auto-indexing feature on the account. Show the exact URL list and obtain explicit user approval first; every call requires confirm_indexing=true.

NameTypeReqDescription
confirm_indexingboolean––
urlsarrayyes–
website_idintegeryes–

No output schema declared.

No examples provided.

run_seo_audit ~61

Run a technical SEO audit on any URL: meta tags, headings, images, links, performance, content quality, security and social metadata, with a scored result. Rate-limited for free accounts.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

Common questions

What is the SEOPro AI MCP server?

SEOPro AI is an MCP server listed in the public MCP registry as io.github.alpha-ai-labs/seo-agent. Turn Search Console data into SEO actions, content, publishing, indexing, and AI insights. This page covers its hosted endpoint (https://api.seoproai.co/api/mcp).

Is the SEOPro AI MCP server safe to use?

SEOPro AI scores 89 out of 100 on VerifyMCP. 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 SEOPro AI MCP server expose?

SEOPro AI exposes 18 tools: list_websites, get_website_stats, get_search_performance, get_top_search_keywords, get_search_trends, and 13 more. Their descriptions and schemas cost roughly 1,285 tokens of context every time the server is loaded.

Does the SEOPro AI MCP server require authentication?

Yes. SEOPro AI asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the SEOPro AI MCP server still maintained?

SEOPro AI is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.