seo-monster

io.github.avansaber/seo-monster

7/8 checks passed
Runs locally
11 secrets
★ 557 GitHub stars
Updated 2026-09-25
Health score 64

About seo-monster

seo-monster is an MCP server published by the GitHub account avansaber. Local-first SEO MCP: track AI citations, Search Console, GA4, PageSpeed, Cloudflare, IndexNow, CrUX.

It runs on your own machine: your AI client starts it from the PyPI package seo-monster at version 0.9.3.

It asks for 11 secrets: PSI_API_KEY, CF_API_TOKEN, SEO_MCP_INDEXNOW_KEY, DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD, OPENPAGERANK_API_KEY, PERPLEXITY_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY and GOOGLE_ADS_DEVELOPER_TOKEN. Give it a key with the least access that still works.

Version 0.9.3 was published on 25 September 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 1 warn, 0 fail, 1 info. How we check.

What it asks for

Variable	Required	Secret	Description
`SEO_MCP_GOOGLE_OAUTH_CLIENT`	No	No	Path to your Desktop-app OAuth client-secrets JSON, downloaded from Google Cloud Console. Required for Search Console, Indexing, and GA4 tools.
`SEO_MCP_GOOGLE_TOKEN`	No	No	Writable path where the cached OAuth token is stored. On first use, a browser opens for one-time consent and the token is written here. Default: ${HOME}/.config/seo-monster/token.json
`SEO_MCP_GSC_DEFAULT_SITE`	No	No	Default Search Console property, e.g. 'sc-domain:example.com' or 'https://www.example.com/'.
`SEO_MCP_GA4_PROPERTY_ID`	No	No	Default GA4 property, e.g. 'properties/123456789' or bare '123456789'.
`PSI_API_KEY`	No	Yes	Google API key shared by PageSpeed Insights and Chrome UX Report History tools. Optional; both work anonymously at a tighter rate limit when unset.
`CF_API_TOKEN`	No	Yes	Cloudflare API token. Optional; needed only for the Cloudflare tools. Scopes: Zone:Read, DNS:Read, Account Analytics:Read, and (only when destructive mode is on) Cache Purge:Purge, Single Redirect:Edit, Zone Settings:Edit, and (for bulk redirects) Account Rulesets:Edit + Account Filter Lists:Edit.
`CF_ZONE`	No	No	Default Cloudflare zone hostname, e.g. 'example.com'.
`SEO_MCP_INDEXNOW_KEY`	No	Yes	IndexNow shared key (any 8-128 hex string you generate). Required only for the IndexNow tools. Host the key file at https://<your-host>/<key>.txt for engine verification.
`SEO_MCP_INDEXNOW_KEY_LOCATION`	No	No	Override the default IndexNow key-file URL (https://<host>/<key>.txt). Set only if you host the key file at a non-standard path.
`SEO_MCP_ALLOW_DESTRUCTIVE`	No	No	Set to 'true' to enable the Cloudflare cache-purge tools. Default false: all destructive tools refuse to run.
`DATAFORSEO_LOGIN`	No	Yes	DataForSEO Basic-auth login. Optional (v0.9). Unlocks SERP/PAA/related, keyword volume+difficulty+intent, competitor keyword-gap, and Google AI Overview citations for keyword_universe / serp_adjacency_expand / onpage_serp_gap auto-fetch / ai_citation_track.
`DATAFORSEO_PASSWORD`	No	Yes	DataForSEO Basic-auth password. Optional (v0.9). Required alongside DATAFORSEO_LOGIN.
`OPENPAGERANK_API_KEY`	No	Yes	Open PageRank (DomCop) free API key. Optional (v0.9). Free competitor domain-authority proxy for onpage_serp_gap.
`PERPLEXITY_API_KEY`	No	Yes	Perplexity Sonar API key. Optional (v0.9). One of the AI answer-engines for ai_citation_track.
`OPENAI_API_KEY`	No	Yes	OpenAI API key (Responses web_search). Optional (v0.9). One of the AI answer-engines for ai_citation_track.
`ANTHROPIC_API_KEY`	No	Yes	Anthropic API key (web_search tool). Optional (v0.9). One of the AI answer-engines for ai_citation_track.
`GEMINI_API_KEY`	No	Yes	Google Gemini API key (Search grounding). Optional (v0.9). One of the AI answer-engines for ai_citation_track.
`GOOGLE_ADS_DEVELOPER_TOKEN`	No	Yes	Google Ads API developer token. Optional (v0.9). Volume-only alternative to DataForSEO for keyword_universe; live use also needs an adwords-scope OAuth re-consent.
`GOOGLE_ADS_CUSTOMER_ID`	No	No	Google Ads customer id (digits). Optional (v0.9). Required alongside GOOGLE_ADS_DEVELOPER_TOKEN.

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/avansaber/seo-monster
Version pinned	Pass	Every package has an explicit version
Secrets requested	Warn	Asks for 11 secrets: PSI_API_KEY, CF_API_TOKEN, SEO_MCP_INDEXNOW_KEY, DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD, OPENPAGERANK_API_KEY, PERPLEXITY_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, GOOGLE_ADS_DEVELOPER_TOKEN
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via GitHub account avansaber
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Install scripts	Pass	seo-monster 0.9.3 has no setup.py; nothing runs at install
Code red flags	Pass	Read 111 files in seo-monster 0.9.3: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AI	Pass	No hidden characters or instructions to the AI in 111 files, including comments and the README

Popularity & health: 64 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity21 / 40

559 GitHub stars, 173 downloads last week, 0 Hacker News posts (0 points). Best two of the three, each on a log scale.

Activity19 / 25

Last push 2026-10-18, last release 2026-08-29, 4 commits in 90 days.

Issue health8 / 15

2 closed of 5 issues, too few to judge. No data, so half marks.

Our checks16 / 20

1 warning, each costing a fifth.

84 forks, 2 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`io.github.avansaber/seo-monster`
Publisher	GitHub account avansaber
How the name is verified	Name verified via GitHub account avansaber. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local: runs on your machine from a package
Packages	pypi `seo-monster` 0.9.3 (stdio)
Version	0.9.3
Published	2026-09-25
Last updated	2026-09-25
Source repository	https://github.com/avansaber/seo-monster
Website	https://www.avansaber.com/seomonster/
Category	Cloud & infrastructure (assigned by keyword rule, not by hand)

Install

Claude Desktop · Python package

{
  "mcpServers": {
    "seo-monster": {
      "command": "uvx",
      "args": [
        "seo-monster==0.9.3"
      ]
    }
  }
}

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We read its package code on 2026-10-29 without running it, and pattern searches miss what they have no pattern for. Tool descriptions built at run time were not seen. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/io-github-avansaber-seo-monster.json. Text inside it that came from the publisher is data, not instructions.