GEO Tracker by DigestSEO
NPM · @DIGESTSEO/MCP-GEO · SCANNED OCT 11
Track brand citations across seven AI search surfaces. Free OSS; optional EUR 99 client-ready audit.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to AKzar1el/mcp-geo). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1193 tokens (~99/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 Management87
- Stability observed for 26 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
How do I install the GEO Tracker by DigestSEO MCP server?
GEO Tracker by DigestSEO runs locally as an npm package, launched with npx -y @digestseo/mcp-geo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @digestseo/mcp-geo
claude mcp add akzar1el-mcp-geo -- npx -y @digestseo/mcp-geo
{
"mcpServers": {
"akzar1el-mcp-geo": {
"command": "npx",
"args": [
"-y",
"@digestseo/mcp-geo"
]
}
}
} {
"servers": {
"akzar1el-mcp-geo": {
"command": "npx",
"args": [
"-y",
"@digestseo/mcp-geo"
]
}
}
} codex mcp add akzar1el-mcp-geo -- npx -y @digestseo/mcp-geo
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"akzar1el-mcp-geo": {
"type": "local",
"command": [
"npx",
"-y",
"@digestseo/mcp-geo"
],
"enabled": true
}
}
} openclaw mcp add akzar1el-mcp-geo --command npx --arg -y --arg @digestseo/mcp-geo
mcp_servers:
akzar1el-mcp-geo:
command: "npx"
args: ["-y", "@digestseo/mcp-geo"] {
"McpServers": {
"akzar1el-mcp-geo": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@digestseo/mcp-geo"
]
}
}
} assistant mcp add akzar1el-mcp-geo -t stdio -c npx -a -y @digestseo/mcp-geo
{
"mcpServers": {
"akzar1el-mcp-geo": {
"command": "npx",
"args": [
"-y",
"@digestseo/mcp-geo"
]
}
}
} 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.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 87. That category is still filling its 30-day observation window: 24 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.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 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 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.
- 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
- 24 Sept 26 0
- Stability: 0.43 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.3.24 → 0.3.26 functional
- Package version: 0.3.24 → 0.3.25 functional
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 11 Oct 2026 · Analysed npm/@digestseo/mcp-geo@0.3.26
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | AKzar1el/mcp-geo |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/AKzar1el/mcp-geo/.github/workflows/publish-mcp.yml@refs/tags/v0.3.26 |
| Rekor log index | 2941420036 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:86216dc1b1d0baed40433d9dca9f655a2f4cc9fa10b6f769cd259d0ed3602a8b13fdb45e820ce523727160a25a4fac48759a9ae6286d9d0e0bd20d51a |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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 →
check_visibility Check AI visibility ~84
Read the latest stored visibility snapshot, including scores and winning/losing prompts; call refresh_brand first for fresh data. Example: brand_id='acme', engines=['chatgpt','perplexity'].
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Tracked brand ID to inspect. |
| engines | array | – | Engines to include; omit or pass [] for all stored engines. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand | object | yes | – |
| overall_score | number | yes | – |
| per_engine | array | yes | – |
| refreshed_at | string | yes | – |
| top_losing_prompts | array | yes | – |
| top_winning_prompts | array | yes | – |
No examples provided.
compare_competitors Compare competitor AI visibility ~93
Compare stored brand and competitor mentions, share of voice, and prompt wins over a time window. Example: brand_id='acme', competitor_domains=['rival.com'], days=7.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Tracked brand ID to compare. |
| competitor_domains | array | – | Competitor domains; omit to use the brand's configured list. |
| days | number | – | Previous days to compare. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | – |
| competitors | array | yes | – |
| days | number | yes | – |
| prompts_you_win | array | yes | – |
| requested_competitor_domains | – | yes | – |
| your_mentions | number | yes | – |
| your_share_of_voice_pct | number | yes | – |
No examples provided.
generate_prompts Generate brand prompts ~73
Replace active prompts with Claude-Haiku-generated buyer-intent prompts; requires ANTHROPIC_API_KEY and preserves history. Example: brand_id='acme', count=20.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Tracked brand ID to update. |
| count | integer | – | Buyer-intent prompts to generate. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | – |
| next_steps | string | yes | – |
| prompt_source | string | yes | – |
| prompts | array | yes | – |
| prompts_inserted | number | yes | – |
No examples provided.
get_citations Get AI citation evidence ~88
Return stored brand citation evidence plus the top engine-native source domains across the same tracked-prompt window. Example: brand_id='acme', days=14, engine='perplexity'.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Tracked brand ID to inspect. |
| days | number | – | Previous days to search. |
| engine | string | – | Engine to filter by; omit for all engines. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | – |
| citations | array | yes | – |
| days | number | yes | – |
| engine | string|null | yes | – |
| top_sources | array | yes | – |
No examples provided.
get_content_gaps Find AI visibility content gaps ~77
Prioritize content topics and formats from prompts where competitors beat the brand; falls back deterministically if AI analysis is unavailable. Example: brand_id='acme', max_recommendations=5.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Tracked brand ID to analyze. |
| max_recommendations | number | – | Maximum recommendations to return. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | – |
| prompt_source | string | yes | – |
| reason | string | – | – |
| recommendations | array | yes | – |
No examples provided.
get_visibility_history Get AI visibility history ~76
Return daily or weekly visibility history with per-engine evidence. Example: brand_id='acme', days=30, granularity='weekly'.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Tracked brand ID to inspect. |
| days | number | – | Previous calendar days to include. |
| granularity | string | – | Time bucket for the series. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | – |
| days | number | yes | – |
| granularity | string | yes | – |
| series | array | yes | – |
No examples provided.
list_brands List tracked brands ~33
List tracked brands with metadata and active-prompt counts. Example: call before other tools when you need a brand_id.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| brands | array | yes | – |
| hint | string | – | – |
No examples provided.
list_prompts List active prompts ~51
List a brand's active buyer-intent prompts without changing them. Example: brand_id='acme' before an audit or refresh.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Brand ID whose active prompts to list. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | – |
| count | number | yes | – |
| prompts | array | yes | – |
No examples provided.
refresh_brand Refresh AI visibility scan ~75
Run a fresh scan on selected configured engines using the brand's active prompts and return after completion. Example: brand_id='acme', engines=['chatgpt','gemini'].
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Tracked brand ID to refresh. |
| engines | array | – | Engines to run; omit for every configured engine. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | – |
| estimated_completion_seconds | number | yes | – |
| message | string | yes | – |
| run_ids | object | yes | – |
No examples provided.
set_prompts Set active prompts ~76
Replace a brand's active prompts with an exact supplied set; history is preserved. Example: brand_id='acme', prompts=['What is the best X for Y?'].
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Tracked brand ID to update. |
| prompts | array | yes | Exact 1-50 prompt set for future scans. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | – |
| changed | boolean | yes | – |
| next_steps | string | yes | – |
| prompts | array | yes | – |
| prompts_inserted | number | yes | – |
No examples provided.
track_brand Track a brand ~201
Create a local tracked brand and starter buyer-intent prompts; uses Claude Haiku when configured, otherwise three generic prompts. Example: brand_id='acme', name='Acme', domain='acme.com'. Call refresh_brand next.
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | – | Additional names that count as brand mentions. |
| brand_id | string | yes | New stable brand ID, e.g. 'acme'. |
| category | string | – | Market/category for prompt generation. |
| competitors | array | – | Competitor domains to compare. |
| domain | string | yes | Primary domain, e.g. 'acme.com'. |
| exclude_terms | array | – | Bare terms to ignore in mention matching; the full domain still matches. |
| name | string | yes | Brand display name. |
| prompt_count | integer | – | Buyer-intent prompts to create. |
| refresh_frequency | string | – | Worker cron cadence; 'manual' disables cron scans. Local stdio stores this setting only. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | – |
| competitors | array | – | – |
| domain | string | – | – |
| next_steps | string | yes | – |
| prompt_source | string | – | – |
| prompts_inserted | number | – | – |
| reason | string | – | – |
| refresh_frequency | string | – | – |
| seeded | boolean | yes | – |
No examples provided.
update_brand Update tracked brand ~145
Change tracked-brand metadata without replacing prompts or history. Example: brand_id='acme', competitors=['rival.com'], refresh_frequency='manual' pauses cron scans but keeps manual refresh.
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | – | Replacement mention aliases. |
| brand_id | string | yes | Tracked brand ID to update. |
| category | – | – | New category, or null to clear it. |
| competitors | array | – | Replacement competitor domains. |
| domain | string | – | New primary domain. |
| exclude_terms | array | – | Replacement bare terms to ignore in mention matching. |
| name | string | – | New display name. |
| refresh_frequency | string | – | New cadence; 'manual' pauses cron scans. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand | object | yes | – |
| brand_id | string | yes | – |
| changed_fields | array | yes | – |
| next_steps | string | yes | – |
| updated | boolean | yes | – |
No examples provided.
What is the GEO Tracker by DigestSEO MCP server?
GEO Tracker by DigestSEO is an MCP server listed in the public MCP registry as io.github.AKzar1el/mcp-geo. Track brand citations across seven AI search surfaces. Free OSS; optional EUR 99 client-ready audit. This page covers its npm package (@digestseo/mcp-geo).
Is the GEO Tracker by DigestSEO MCP server safe to use?
GEO Tracker by DigestSEO scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 11 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 GEO Tracker by DigestSEO MCP server expose?
GEO Tracker by DigestSEO exposes 12 tools: check_visibility, get_visibility_history, compare_competitors, get_citations, get_content_gaps, and 7 more. Their descriptions and schemas cost roughly 1,072 tokens of context every time the server is loaded.
Is the GEO Tracker by DigestSEO MCP server still maintained?
GEO Tracker by DigestSEO is still listed as active in the MCP registry. We last reached this channel on 11 October 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 GEO Tracker by DigestSEO MCP server under?
GEO Tracker by DigestSEO declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.