Creator SEO MCP
PYPI · CREATOR-SEO-MCP · SCANNED SEP 20
SEO MCP server for creators. Ranks Google Search Console opportunities by ad revenue, not clicks.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 94 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 601 tokens (~75/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Creator SEO MCP server?
Creator SEO MCP runs locally as a PyPI package, launched with uvx creator-seo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · creator-seo-mcp
claude mcp add yoshyaes-creator-seo-mcp -- uvx creator-seo-mcp
{
"mcpServers": {
"yoshyaes-creator-seo-mcp": {
"command": "uvx",
"args": [
"creator-seo-mcp"
]
}
}
} {
"servers": {
"yoshyaes-creator-seo-mcp": {
"command": "uvx",
"args": [
"creator-seo-mcp"
]
}
}
} codex mcp add yoshyaes-creator-seo-mcp -- uvx creator-seo-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yoshyaes-creator-seo-mcp": {
"type": "local",
"command": [
"uvx",
"creator-seo-mcp"
],
"enabled": true
}
}
} openclaw mcp add yoshyaes-creator-seo-mcp --command uvx --arg creator-seo-mcp
mcp_servers:
yoshyaes-creator-seo-mcp:
command: "uvx"
args: ["creator-seo-mcp"] {
"McpServers": {
"yoshyaes-creator-seo-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"creator-seo-mcp"
]
}
}
} assistant mcp add yoshyaes-creator-seo-mcp -t stdio -c uvx -a creator-seo-mcp
{
"mcpServers": {
"yoshyaes-creator-seo-mcp": {
"command": "uvx",
"args": [
"creator-seo-mcp"
]
}
}
} 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 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.
- 19 Sept 26 −4
- Stability: pass → 0.77 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 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.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed pypi/creator-seo-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 46 packages
| Packages resolved | 46 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
analyze_content_decay Analyze Content Decay ~95
Compare recent vs prior period for every page and flag declining traffic. Results are sorted worst decliners first (most negative percent change at top).
| Name | Type | Req | Description |
|---|---|---|---|
| compare_days | integer | – | Length of the comparison period in days |
| min_clicks | integer | – | Minimum clicks in recent period to include |
| recent_days | integer | – | Length of the recent period in days |
| site_url | string | yes | GSC property URL |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
audit_page_onpage Audit Page Onpage ~66
Fetch a page, parse its title/meta/headings/body, and return concrete edit suggestions for the target query.
| Name | Type | Req | Description |
|---|---|---|---|
| page_url | string | yes | Full URL of the page to audit |
| target_query | string | yes | The search query you want this page to rank for |
| Name | Type | Req | Description |
|---|---|---|---|
| h1 | string | yes | – |
| headings | array | yes | – |
| meta_description | string | yes | – |
| suggestions | array | yes | – |
| target_density | number | yes | – |
| target_in_h1 | boolean | yes | – |
| target_in_title | boolean | yes | – |
| title | string | yes | – |
| url | string | yes | – |
| word_count | integer | yes | – |
No examples provided.
find_cannibalization Find Cannibalization ~72
Find queries where multiple pages are competing, splitting authority and confusing Google. Results are sorted by total impression volume.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days |
| min_impressions | integer | – | Minimum total impressions across competing pages |
| site_url | string | yes | GSC property URL |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_page_performance Get Page Performance ~69
Full GSC picture for one URL: clicks, impressions, CTR, position, and top queries.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days |
| page_url | string | yes | Full URL of the page to analyze |
| site_url | string | yes | GSC property URL |
| Name | Type | Req | Description |
|---|---|---|---|
| clicks | integer | yes | – |
| ctr | number | yes | – |
| impressions | integer | yes | – |
| page | string | yes | – |
| position | number | yes | – |
| top_queries | array | yes | – |
No examples provided.
get_striking_distance_keywords Get Striking Distance Keywords ~123
Find queries ranking in striking distance of page 1 (positions 4-15 by default). Results are sorted by impression volume so the highest-potential opportunities come first.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days |
| limit | integer | – | Max results to return |
| min_impressions | integer | – | Minimum impressions to include |
| position_max | number | – | Maximum average position |
| position_min | number | – | Minimum average position |
| site_url | string | yes | GSC property URL, e.g. https://example.com/ |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_top_opportunities Get Top Opportunities ~105
The headline call. Combines striking-distance keywords, content decay, and cannibalization, weights each by estimated revenue, and returns a single ranked action list. Revenue estimates use your configured RPM and affiliate multipliers.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days |
| limit | integer | – | Max opportunities to return |
| site_rpm | – | – | Override display ad RPM in USD (default from env) |
| site_url | string | yes | GSC property URL |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
health_check Health Check ~22
Check that the server is running and list your verified GSC properties.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | – |
| verified_sites | array | – | – |
| version | string | yes | – |
No examples provided.
list_sites List Sites ~19
List all Google Search Console properties you have access to.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
What is the Creator SEO MCP server?
Creator SEO MCP is listed in the public MCP registry as io.github.Yoshyaes/creator-seo-mcp. SEO MCP server for creators. Ranks Google Search Console opportunities by ad revenue, not clicks. This page covers its PyPI package (creator-seo-mcp).
Is the Creator SEO MCP server safe to use?
Creator SEO MCP scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 Creator SEO MCP server expose?
Creator SEO MCP exposes 8 tools: health_check, list_sites, get_striking_distance_keywords, get_page_performance, analyze_content_decay, and 3 more. Their descriptions and schemas cost roughly 571 tokens of context every time the server is loaded.
Is the Creator SEO MCP server still maintained?
Creator SEO MCP is still listed as active in the MCP registry. We last reached this channel on 20 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 Creator SEO MCP server under?
Creator SEO MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.