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.

GEO Tracker by DigestSEO

NPM · @DIGESTSEO/MCP-GEO · SCANNED SEP 20

Track brand citations across five AI search engines. Free OSS; optional EUR 99 client-ready audit.

Available components

−6 this week 75 Trust /100
Trust breakdown (7 categories)

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 Security63
  • No malware found by supply-chain analysis.Pass
  • Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
  • No install/post-install scripts declared.Pass
  • Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
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 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1353 tokens (~135/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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 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

# add to Claude Code
claude mcp add akzar1el-mcp-geo -- npx -y @digestseo/mcp-geo
// .cursor/mcp.json
{
  "mcpServers": {
    "akzar1el-mcp-geo": {
      "command": "npx",
      "args": [
        "-y",
        "@digestseo/mcp-geo"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "akzar1el-mcp-geo": {
      "command": "npx",
      "args": [
        "-y",
        "@digestseo/mcp-geo"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add akzar1el-mcp-geo -- npx -y @digestseo/mcp-geo
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "akzar1el-mcp-geo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@digestseo/mcp-geo"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add akzar1el-mcp-geo --command npx --arg -y --arg @digestseo/mcp-geo
# ~/.hermes/config.yaml
mcp_servers:
  akzar1el-mcp-geo:
    command: "npx"
    args: ["-y", "@digestseo/mcp-geo"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "akzar1el-mcp-geo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@digestseo/mcp-geo"
      ]
    }
  }
}
# add to Vellum
assistant mcp add akzar1el-mcp-geo -t stdio -c npx -a -y @digestseo/mcp-geo
// mcp.json
{
  "mcpServers": {
    "akzar1el-mcp-geo": {
      "command": "npx",
      "args": [
        "-y",
        "@digestseo/mcp-geo"
      ]
    }
  }
}
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.

  • 20 Sept 26 −10
    • Known CVEs: pass → unverified security
    • Tool safety: pass → unverified security
    • Stability: 0.30 → unverified security
    • Schema quality: 1193 → 1353 functional
    • Dependency health: 0.85 → unverified functional
    • 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.11 → 0.3.15 functional
    • Package version: 0.3.11 → 0.3.14 functional
    • Package version: 0.3.11 → 0.3.13 functional
    • Package version: 0.3.2 → 0.3.12 functional
    • Package version: 0.3.11 → 0.3.12 functional
  • 19 Sept 26 +15
    • Known CVEs: pass → unverified security
    • Stability: 0.27 → unverified security
    • Tool safety: pass → unverified security
    • Malware scan: unverified → pass security
    • Dependency health: 0.85 → unverified functional
    • 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.6 → 0.3.11 functional
    • Package version: 0.3.6 → 0.3.10 functional
    • Package version: 0.3.2 → 0.3.9 functional
    • Package version: 0.3.6 → 0.3.9 functional
    • Package version: 0.3.6 → 0.3.8 functional
    • Package version: 0.3.6 → 0.3.7 functional
  • 18 Sept 26 −14
    • Malware scan: pass → unverified security
    • Package version: 0.3.5 → 0.3.6 functional
  • 17 Sept 26 0
    • Tool safety: pass → unverified security
    • Stability: 0.20 → 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.4 → 0.3.5 functional
  • 16 Sept 26 +15
    • Malware scan: unverified → pass security
  • 15 Sept 26 −12
    • Malware scan: pass → unverified security
    • Stability: unverified → 0.17 functional
    • Package version: 0.3.3 → 0.3.4 functional
  • 12 Sept 26 +15
    • Malware scan: unverified → pass security
  • 11 Sept 26 0
    • Package version: 0.3.2 → 0.3.3 functional
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 20 Sept 2026 · Analysed npm/@digestseo/mcp-geo@0.3.15

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.15
Rekor log index 2896551654
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:29d730a7ad9eb3f7101676f7b8398a52d9dd64d464935fecc73ebd30157c9455b982c4e638803b99781cd0b221917f7aa693a522a7091d105b14ad333

Background: How many MCP packages publish verified provenance →

MCP tools · 10 exposed · ~1,265 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_visibility ~135

Get the latest AI visibility data for a tracked brand: which AI assistants (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) cite this brand, for which prompts, and how it compares to competitors. Use when the user asks 'how visible am I on AI?', 'who's citing my brand?', or 'show me my AI visibility score'. Returns stored data — for fresh data, call refresh_brand.

NameTypeReqDescription
brand_idstringyesStable identifier of the tracked brand to inspect.
enginesarrayOptional engine filter. If omitted or empty, return results for every engine with stored data.
NameTypeReqDescription
brandobjectyes
overall_scorenumberyes
per_enginearrayyes
refreshed_atstringyes
top_losing_promptsarrayyes
top_winning_promptsarrayyes

No examples provided.

compare_competitors ~127

Compare a brand's AI visibility against competitors for the same category. Returns share-of-voice percentages, prompts the user wins, and prompts where competitors win. Use when the user asks 'who beats me in AI search?', 'compare me to my competitors', or 'why does [competitor] get cited more?'.

NameTypeReqDescription
brand_idstringyesStable identifier of the tracked brand to compare.
competitor_domainsarrayOptional competitor domains to compare; otherwise use the brand's configured competitors.
daysnumberNumber of previous days to include in the comparison.
NameTypeReqDescription
brand_idstringyes
competitorsarrayyes
daysnumberyes
prompts_you_winarrayyes
requested_competitor_domainsyes
your_mentionsnumberyes
your_share_of_voice_pctnumberyes

No examples provided.

generate_prompts ~104

Regenerate the buyer-intent prompt set for a tracked brand using Claude Haiku (requires ANTHROPIC_API_KEY). Replaces the brand's active prompts; historical run data is preserved. Use when the user wants better or more prompts, or to upgrade from the generic starter prompts after adding an Anthropic key.

NameTypeReqDescription
brand_idstringyesStable identifier of the tracked brand to update.
countintegerNumber of buyer-intent prompts to generate.
NameTypeReqDescription
brand_idstringyes
next_stepsstringyes
prompt_sourcestringyes
promptsarrayyes
prompts_insertednumberyes

No examples provided.

get_citations ~143

Get citation events where AI assistants mention the brand. Each event includes the prompt that triggered it, the LLM's response excerpt, whether the brand was mentioned with or without a link, and the matched brand URL from engine-native citation data when available. Use when the user asks 'show me where I'm cited', 'what are ChatGPT/Claude/Perplexity actually saying about my brand?', or 'give me proof of AI citations'.

NameTypeReqDescription
brand_idstringyesStable identifier of the tracked brand to inspect.
daysnumberNumber of previous days from which to return citations.
enginestringOptional engine filter for the citation events.
NameTypeReqDescription
brand_idstringyes
citationsarrayyes
daysnumberyes
enginestring|nullyes

No examples provided.

get_content_gaps ~109

Get actionable content recommendations based on AI visibility gaps. Returns prioritized topics and content formats that would close the gap between this brand and competitors winning the same prompts. Use when the user asks 'what should I write to improve AI visibility?', 'what content gaps do I have?', or 'how do I get cited more by AI?'.

NameTypeReqDescription
brand_idstringyesStable identifier of the tracked brand to analyze.
max_recommendationsnumberMaximum number of content recommendations to return.
NameTypeReqDescription
brand_idstringyes
prompt_sourcestringyes
reasonstring
recommendationsarrayyes

No examples provided.

get_visibility_history ~106

Get the time-series history of a brand's AI visibility score, broken down per engine. Use when the user asks 'how has my AI visibility changed over time?', 'is my visibility growing or shrinking?', or 'show me the trend for the last month'.

NameTypeReqDescription
brand_idstringyesStable identifier of the tracked brand to inspect.
daysnumberNumber of previous calendar days to include.
granularitystringTime bucket for the returned visibility series.
NameTypeReqDescription
brand_idstringyes
daysnumberyes
granularitystringyes
seriesarrayyes

No examples provided.

list_brands ~59

List every brand tracked in the local database, with domain, category, competitors, refresh frequency, and how many prompts are active. Use when the user asks 'which brands am I tracking?' or to look up the brand_id the other tools need.

Input schema present but exposes no named parameters.

NameTypeReqDescription
brandsarrayyes
hintstring

No examples provided.

list_prompts ~72

List the exact active buyer-intent prompts for one tracked brand without changing them. Use before a scan or audit when the user wants to inspect the measurement set, verify prompt coverage, or review what generate_prompts produced.

NameTypeReqDescription
brand_idstringyesStable identifier of the tracked brand whose active prompts to inspect.
NameTypeReqDescription
brand_idstringyes
countnumberyes
promptsarrayyes

No examples provided.

refresh_brand ~121

Manually trigger a fresh AI visibility scan for a tracked brand. Runs every selected configured engine (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) against the brand's current prompt set sequentially. Use when the user asks 'refresh my data', 'rerun the scan', or 'I want fresh data right now'. Returns only after all selected engine scans finish.

NameTypeReqDescription
brand_idstringyesStable identifier of the tracked brand to refresh.
enginesarrayOptional engine filter. If omitted, refresh every configured engine.
NameTypeReqDescription
brand_idstringyes
estimated_completion_secondsnumberyes
messagestringyes
run_idsobjectyes

No examples provided.

track_brand ~289

Start tracking a brand's AI visibility. Creates the brand in the local database and generates buyer-intent prompts for it — via Claude Haiku when ANTHROPIC_API_KEY is configured, otherwise three generic starter prompts (upgrade later with generate_prompts). Use when the user says 'track my brand', 'add my site', 'start monitoring acme.com', or when another tool reported the brand doesn't exist. After tracking, call refresh_brand to run the first scan.

NameTypeReqDescription
aliasesarrayExtra terms that always count as a brand mention (product names, abbreviations).
brand_idstringyesStable identifier to assign to the new tracked brand.
categorystringOptional product or market category for prompt generation.
competitorsarrayOptional competitor domains to include in visibility analysis.
domainstringyesPrimary domain of the brand, such as acme.com.
exclude_termsarrayTerms suppressed from bare-word matching — for brand names that are everyday words ("Monday", "Notion"). The full domain still matches.
namestringyesDisplay name of the brand to track.
prompt_countintegerNumber of buyer-intent prompts to generate for the brand.
refresh_frequencystringRefresh cadence used by self-hosted Worker cron scheduling. Local stdio stores this setting but does not run a background scheduler.
NameTypeReqDescription
brand_idstringyes
competitorsarray
domainstring
next_stepsstringyes
prompt_sourcestring
prompts_insertednumber
reasonstring
refresh_frequencystring
seededbooleanyes

No examples provided.

Common questions

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 five AI search engines. 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 75 out of 100 on VerifyMCP. 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 10 tools: check_visibility, get_visibility_history, compare_competitors, get_citations, get_content_gaps, and 5 more. Their descriptions and schemas cost roughly 1,265 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 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 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.