SEO GEO Intelligence
PYPI · SEO-GEO-INTELLIGENCE-MCP · 2 COMPONENTS
SEO and AI-answer visibility intelligence for search, content gaps, and GEO actions.
Last scanned (16 hours ago)
Scores higher than 66% of PyPI servers
Category Marketing and SEO
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 Security94
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 175 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 301 tokens (~25/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 92% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 0% of tool parameters carry a description.Fail
- 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 29 Oct 26 +14
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 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 4 Nov 2026 · Analysed pypi/seo-geo-intelligence-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 |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_hook | unreviewed | legacy backend root module |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| 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 →
get_competitor_geo_score Get Competitor Geo Score ~36
Compare AI answer visibility for competitors in a category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| competitors | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_content_gaps Get Content Gaps ~25
Return missing topics and citation opportunities.
| Name | Type | Req | Description |
|---|---|---|---|
| target_keyword | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_geo_recommendations Get Geo Recommendations ~21
Return prioritized content actions to improve AI answer visibility.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_geo_visibility_score Get Geo Visibility Score ~38
Measure brand inclusion across AI answer engines.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_models | – | – | – |
| brand | string | yes | – |
| keywords | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_license_status Get License Status ~27
Return payment/license readiness for AtulHritik-Mcp-Suite without exposing secrets.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_live_connector_status Get Live Connector Status ~20
Return SEO/GEO connector readiness without exposing secrets.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_seo_performance Get Seo Performance ~35
Blend GSC and backlink/rank data.
| Name | Type | Req | Description |
|---|---|---|---|
| date_range | string | – | – |
| domain | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
health Health ~4
No description provided.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
monitor_brand_mentions_in_ai Monitor Brand Mentions In Ai ~32
Stage a scheduled AI mention monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | – |
| frequency | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
test_ai_visibility_connection Test Ai Visibility Connection ~21
Report AI visibility provider readiness without making paid model calls.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
test_google_search_console_connection Test Google Search Console Connection ~21
Run a read-only Google Search Console smoke check.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
test_seo_data_connection Test Seo Data Connection ~21
Run a read-only SEO data provider smoke check.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the SEO GEO Intelligence MCP server?
SEO GEO Intelligence runs locally as a PyPI package, launched with uvx seo-geo-intelligence-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 · seo-geo-intelligence-mcp
claude mcp add atul0016-seo-geo-intelligence -- uvx seo-geo-intelligence-mcp
What is the SEO GEO Intelligence MCP server?
SEO GEO Intelligence is an MCP server listed in the public MCP registry as io.github.atul0016/seo-geo-intelligence. SEO and AI-answer visibility intelligence for search, content gaps, and GEO actions. This page covers its PyPI package (seo-geo-intelligence-mcp).
Is the SEO GEO Intelligence MCP server safe to use?
SEO GEO Intelligence scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 SEO GEO Intelligence MCP server expose?
SEO GEO Intelligence exposes 12 tools: health, get_license_status, get_live_connector_status, test_google_search_console_connection, test_seo_data_connection, and 7 more. Their descriptions and schemas cost roughly 301 tokens of context every time the server is loaded.
Is the SEO GEO Intelligence MCP server still maintained?
SEO GEO Intelligence is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.