[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_136":137},"routes/modules.$creator.$moduleId",{"_14":15,"_16":17,"_18":19,"_20":21},"routes/modules.$creator.$moduleId.endpoints",{"_11":12,"_13":-5},"error","Module not found","tools","module",{"_20":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":26,"_36":37,"_38":-5,"_39":-5,"_40":41,"_42":43,"_44":45,"_46":47,"_48":49,"_50":51,"_52":53,"_54":55,"_56":-5,"_57":49,"_58":59,"_60":61,"_62":63,"_64":65,"_66":67,"_68":69,"_70":71,"_72":73,"_74":75,"_76":77,"_78":79,"_80":-5,"_81":-5,"_82":-5,"_83":49,"_84":-5,"_85":86,"_87":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98},"apiUrl","https://odel.app/api","creator","akzar1el","moduleId","mcp-geo","@akzar1el/mcp-geo","displayName","GEO Tracker by DigestSEO","tagline","DigestSEO GEO Tracker: track brand citations across five AI search engines.","iconKey","https://digestseo.com/products/mcp-geo-mark.svg","category","remote","status","published","visibility","public","metaDescription","deploymentType","external","workerName","bindingName","mcpConfig","{\"url\":\"https://geo-mcp.digestseo.com/mcp\",\"transport\":\"streamable-http\",\"authType\":\"none\"}","pricingModel","free","creatorUserId","system:external-import","createdAt",1783916470000,"updatedAt",1788772644000,"sourceRegistry","official-mcp-registry","sourceUrl","https://registry.modelcontextprotocol.io/v0/servers?search=io.github.AKzar1el%2Fmcp-geo","sourceVerified",true,"sourceMissingSince","importedAt","upstreamStars",44,"upstreamUpdatedAt",1788206558000,"detectedTransport","streamable-http","detectedAuthType","oauth","probeStatus","ok","lastProbedAt",1788151887000,"githubRepoUrl","https://github.com/AKzar1el/mcp-geo","githubRepoFullName","AKzar1el/mcp-geo","releaseId","ext-akzar1el-mcp-geo","version","0.3.2","descriptionMarkdown","# DigestSEO — AI Visibility MCP for SEO & GEO\n\n[![CI](https://github.com/AKzar1el/mcp-geo/actions/workflows/ci.yml/badge.svg)](https://github.com/AKzar1el/mcp-geo/actions/workflows/ci.yml)\n[![npm version](https://img.shields.io/npm/v/%40digestseo%2Fmcp-geo)](https://www.npmjs.com/package/@digestseo/mcp-geo)\n[![MCP Registry](https://img.shields.io/badge/MCP_Registry-io.github.AKzar1el%2Fmcp--geo-0098FF)](https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.AKzar1el/mcp-geo)\n[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE)\n[![TypeScript](https://img.shields.io/badge/TypeScript-007ACC?logo=typescript&logoColor=white)](https://www.typescriptlang.org/)\n[![Cloudflare Workers](https://img.shields.io/badge/Cloudflare-Workers-F38020?logo=cloudflare&logoColor=white)](https://workers.cloudflare.com/)\n[![MCP](https://img.shields.io/badge/MCP-Server-blueviolet)](https://modelcontextprotocol.io/)\n[![mcp-geo MCP server](https://glama.ai/mcp/servers/AKzar1el/mcp-geo/badges/score.svg)](https://glama.ai/mcp/servers/AKzar1el/mcp-geo)\n[![GitHub stars](https://img.shields.io/github/stars/AKzar1el/mcp-geo?style=social)](https://github.com/AKzar1el/mcp-geo/stargazers)\n\n\n## Quick Install\n\nRuns locally over stdio with your own API keys — all data stays on your machine (see [Privacy Policy](#privacy-policy)). Set at least one engine key (`OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, `GEMINI_API_KEY`, `PERPLEXITY_API_KEY`, `SERPAPI_API_KEY`); engines without a key skip gracefully.\n\n**Runtime:** Node.js 22+ (CI exercises Node 22 and 24).\n\n**Claude Desktop / any MCP client (npx):**\n\n```json\n{\n \"mcpServers\": {\n \"digestseo\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@digestseo/mcp-geo\"],\n \"env\": {\n \"OPENAI_API_KEY\": \"sk-...\",\n \"GEMINI_API_KEY\": \"your_key_here\"\n }\n }\n }\n}\n```\n\n**Claude Code:**\n\n```bash\nclaude mcp add --transport stdio digestseo -s user --env GEMINI_API_KEY=your_key_here -- npx -y @digestseo/mcp-geo\n```\n\n**Cursor:**\n\n[![Add to Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=digestseo&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBkaWdlc3RzZW8vbWNwLWdlbyJdLCJlbnYiOnsiT1BFTkFJX0FQSV9LRVkiOiIiLCJBTlRIUk9QSUNfQVBJX0tFWSI6IiIsIkdFTUlOSV9BUElfS0VZIjoiIiwiUEVSUExFWElUWV9BUElfS0VZIjoiIiwiU0VSUEFQSV9BUElfS0VZIjoiIn19)\n\n**Kiro (hosted endpoint):**\n\n[![Add to Kiro](https://kiro.dev/images/add-to-kiro.svg)](https://kiro.dev/launch/mcp/add?name=mcp-geo&config=%7B%22url%22%3A%22https%3A%2F%2Fgeo-mcp.digestseo.com%2Fmcp%22%2C%22disabled%22%3Afalse%2C%22autoApprove%22%3A%5B%5D%7D)\n\nUses the hosted OAuth endpoint, so no engine API keys are placed in the Kiro install link.\n\n**Claude Desktop extension (one-click):** download the `.mcpb` bundle from the [latest release](https://github.com/AKzar1el/mcp-geo/releases/latest) and double-click it — Claude Desktop prompts for the API keys.\n\n**First run:** ask your client to *\"track acme.com as brand `acme`, then refresh it\"* — `track_brand` creates the brand with generated prompts, `refresh_brand` runs the first scan, `check_visibility` shows the scores.\n\nAI agents installing this server: follow [llms-install.md](https://github.com/AKzar1el/mcp-geo/blob/main/llms-install.md). Prefer a remote server with cron auto-refresh? Self-host on Cloudflare Workers below.\n\n---\n\n**mcp-geo** is an open-source **AI visibility tracker** that measures how often your brand is cited by ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews. It's the **GEO** (Generative Engine Optimization) and **AEO** (Answer Engine Optimization) equivalent of Google Search Console — built as an MCP server so you can query your AI visibility data directly inside Claude.ai, Claude Desktop, Claude Code, Cursor, Codex CLI, or any MCP-compatible client.\n\nCanonical product page: [DigestSEO mcp-geo — AI Visibility MCP Server](https://digestseo.com/geo-mcp/)\n\nEngineering case study: [DigestSEO MCP Suite — AI visibility, Search Console, web validation, and trend intelligence](https://tomiseregi.si/projects/digestseo-mcp-suite)\n\n> **Prefer zero setup?** Try the hosted version at [digestseo.com](https://digestseo.com) — managed Cloudflare infra, no API keys to manage, multi-brand, scheduled refresh, web UI. Waitlist now open. [Join waitlist →](https://digestseo.com/#waitlist)\n\n---\n\n## What it produces\n\nConnect via MCP, ask Claude *\"Run an AI visibility analysis on [my brand]\"*, and within 90 seconds you get a strategist-quality memo grounded in real per-engine data:\n\n[![Example AI visibility report](https://raw.githubusercontent.com/AKzar1el/mcp-geo/main/docs/demo-report-hero.png)](docs/demo-report-full.png)\n\n*[View the full report including content gaps, engine recommendations, and synthesis →](https://github.com/AKzar1el/mcp-geo/blob/main/docs/demo-report-full.png)*\n\nThe report above was generated by Claude through the digestseo-mcp MCP server. The conversation chained five hosted tools — `visibility.check`, `visibility.compare`, `visibility.citations` (Perplexity + Claude), and `visibility.content_gaps` — to produce a 4-engine analysis with citation excerpts and a 3-recommendation strategy memo.\n\n---\n\n## What's New\n\n### [0.3.2] — July 27, 2026\n\n- **Published scoped package:** `@digestseo/mcp-geo` with synchronized Worker, MCP Registry, and MCPB metadata.\n- **Hosted tool metadata:** `visibility.*` namespaces with typed input/output schemas; local stdio tool names remain flat.\n- **Distribution and deployment:** dedicated `mcp-geo-db` D1 configuration, Cursor and Claude Code plugin metadata, and patched production dependency pins.\n\n### [0.3.0] — July 2026\n\n- **Local stdio CLI on npm** (`npx -y @digestseo/mcp-geo`): the same MCP tools backed by a local SQLite database (`~/.digestseo/digestseo.sqlite`) — no Cloudflare account needed. Engines run inline with your own API keys.\n- **Local brand-management tools** (CLI only): `track_brand`, `list_brands`, `generate_prompts`. Workers deployments keep these behind the `X-Seed-Secret`-gated `/admin/*` routes.\n- **Runtime-agnostic core** (`src/core/`) shared by the Worker and the CLI, with a `Db` contract implemented by D1 and better-sqlite3 adapters. All 0.2.1 accuracy and security fixes carry over to both runtimes.\n- **Distribution metadata**: official MCP Registry `server.json`, MCPB desktop extension (`.mcpb` bundle), Dockerfile, `llms-install.md` for AI agents, release-publish workflow.\n\n### [0.2.1] — June 2026\n\n- **Optional `CONNECT_SECRET` gate on the OAuth flow.** By default the OSS build auto-completes `/authorize` for any MCP client that knows your worker URL — anyone who finds the URL can connect and call `visibility.refresh`, spending your engine API credits. Set `CONNECT_SECRET` and the browser step of the connect flow now asks for it before issuing a token. See [SECURITY.md](https://github.com/AKzar1el/mcp-geo/blob/main/SECURITY.md).\n- **Accurate citation matching.** Brand/competitor mentions now require word boundaries (`acme` no longer matches \"acmeshop\"), and linked-citation checks require the exact domain or a subdomain (`notacme.com` no longer counts as a link to `acme.com`).\n- **Per-brand `aliases` and `exclude_terms`.** Aliases always count as a mention; exclude terms suppress the bare-word match on the brand name and domain root — so \"Monday\" the brand stops matching \"monday\" the weekday, while `monday.com` still counts. Apply `migrations/0005_brand_alias_exclude.sql`; existing brands behave exactly as before.\n- **`visibility.history` consistency.** Partially-finished runs now count toward history (matching `visibility.check`'s 0.2.0 behavior), and fully-failed runs no longer show up as fake zero scores.\n- **CI + unit tests.** GitHub Actions runs `tsc --noEmit` plus a pure-function unit suite (`npm run test:unit`) covering mention matching, citation extraction, and score aggregation on every push.\n- **Docs now recommend OpenAI + Anthropic as the starting engine pair** — the Gemini free tier rate-limits brands with more than ~5 prompts and produced misleading first-run data as the documented cheapest path.\n- Constant-time comparison for `SEED_SECRET` / `CONNECT_SECRET`.\n\n### [0.2.0] — May 2026\n\n- **Per-engine HTTP fan-out.** `/admin/run-live` now creates one runs row per engine and self-fetches `/admin/run-engine` once per engine. Each engine runs in its own worker invocation with its own free-plan 50-subrequest budget — a single-invocation fan-out used to burst past the cap mid-run and lose half the rows.\n- **Service binding (`env.SELF`)** dispatches the per-engine fan-out through Cloudflare's internal fabric instead of a public-URL fetch, dodging the \"Worker called itself\" guard (error 1042) that silently blocks the latter.\n- **Status column** on `prompt_responses` (`ok` / `failed` / `skipped`) plus `error_message`. Failed engine calls used to write `raw_response='ERROR: ...'` rows that downstream scoring treated as real zero-mention hits; now they're explicitly excluded.\n- **FK-resistant inserts.** `/admin/run-engine` `INSERT OR IGNORE`s its runs row before persisting — D1 is eventually consistent across edge regions, and the upstream `INSERT INTO runs` from `/admin/run-live` doesn't always replicate before the downstream engine call lands. The IGNORE makes the FK happy either way.\n- **Bulk D1 batch.** Each engine collects its 20 prompt results in memory then flushes inserts + cache writes + the final `UPDATE runs SET status='completed'` in a single `D1.batch()` call. Drops the per-invocation subrequest count from ~89 to ~26.\n- **Relaxed visibility queries.** `getLatestCompletedRun` anchors on `EXISTS(ok rows)` instead of `status='completed'`, so partially-finished runs still surface their data in MCP tool output instead of silently disappearing.\n- **New admin route `POST /admin/cleanup-failed-runs`** for one-shot deletion of legacy polluted rows after migrating to 0004.\n\n### [0.1.1] — May 2026\n\n- Manual install is now the canonical path. The unreliable bash setup script was removed; SETUP.md is self-contained and copy-pasteable, with every interactive wrangler prompt documented inline.\n\n### [0.1.0] — May 2026\n\n- Initial public release.\n- 5-engine support: ChatGPT (`gpt-4o-mini`), Claude (`claude-haiku-4-5`), Perplexity (`sonar`), Gemini (`gemini-2.5-flash-lite`), and Google AI Overviews (via SerpAPI).\n- 6 hosted MCP tools: `visibility.check`, `visibility.history`, `visibility.compare`, `visibility.citations`, `visibility.content_gaps`, `visibility.refresh`.\n- Engines are opt-in based on which API keys you provide — set only the credentials you have, the rest skip gracefully.\n- Cloudflare Cron Trigger that auto-refreshes tracked brands every 6h, respecting per-brand `refresh_frequency` (daily/weekly).\n- D1-backed storage for brands, prompts, runs, citations, and a shared prompt cache.\n\n---\n\n## What Can This Do?\n\n- **See which AI tools cite your brand and which don't** — get a per-engine breakdown of who's citing you for buyer-intent queries.\n- **Track AI visibility weekly, automatically** — the built-in Cron Trigger re-runs scans on the cadence you configure per brand.\n- **Compare your AI visibility to competitors** — share-of-voice percentages, prompts you win, prompts they win.\n- **Find content gaps** — Claude-Haiku-synthesized recommendations grounded in your actual losing prompts.\n- **Use it inside Claude.ai conversations** — add the deployed Worker URL as a custom MCP connector and ask in natural language.\n- **Self-hosted on your own Cloudflare account** — your API keys, your data, your cost ceiling. The free Workers + D1 tiers cover a single brand with daily refreshes.\n\n*See [the example report above](#what-it-produces) for what this looks like in practice.*\n\n---\n\n## Available Tools\n\n| Tool | What it does | What you provide |\n|---|---|---|\n| `visibility.check` | Latest AI visibility snapshot across all configured engines for a tracked brand, with per-engine scores, winning prompts, and losing prompts. | `brand_id`, optional `engines[]` filter |\n| `visibility.history` | Time-series history of overall and per-engine visibility, bucketed daily or weekly. | `brand_id`, optional `days` (default 30), optional `granularity` (`daily`/`weekly`) |\n| `visibility.compare` | Share-of-voice comparison against competitor domains, with prompts you win and prompts they win. | `brand_id`, optional `competitor_domains[]`, optional `days` |\n| `visibility.citations` | The actual citation events — prompt, engine, response excerpt, citation type, brand URL when present. | `brand_id`, optional `days`, optional `engine` filter |\n| `visibility.content_gaps` | Prioritized Claude-Haiku-generated content recommendations targeting your losing prompts. | `brand_id`, optional `max_recommendations` (1-10) |\n| `visibility.refresh` | Manually trigger a fresh scan across every engine whose API key is set. | `brand_id`, optional `engines[]` filter |\n\nThe local stdio CLI (npx, desktop extension, Docker) additionally provides brand management — on a Workers deployment the same operations live behind the `X-Seed-Secret`-gated `/admin/*` routes instead:\n\n| Tool (local CLI only) | What it does | What you provide |\n|---|---|---|\n| `track_brand` | Start tracking a brand: creates it locally and generates its buyer-intent prompt set (Claude Haiku when `ANTHROPIC_API_KEY` is set, three starter prompts otherwise). | `brand_id`, `name`, `domain`, optional `category`, `competitors[]`, `aliases[]`, `exclude_terms[]`, `prompt_count` |\n| `list_brands` | List tracked brands with domains, competitors, and active prompt counts. | — |\n| `generate_prompts` | Regenerate a brand's prompt set via Claude Haiku (replaces active prompts, keeps history). | `brand_id`, optional `count` (default 20) |\n\n---\n\n## Getting Started\n\n### Step 1 — Get API keys\n\nEngines are opt-in. Pick the ones you want; the rest skip silently.\n\n- **OpenAI** — ChatGPT engine. ~€0.0004 per prompt with `gpt-4o-mini`. Batch path roughly halves that. [platform.openai.com](https://platform.openai.com/api-keys)\n- **Anthropic** — Claude engine, plus prompt generation and content-gap analysis (both call Claude Haiku). ~€0.0002 per prompt. Free trial credits are usually enough to evaluate. [console.anthropic.com](https://console.anthropic.com/)\n- **Google AI Studio (Gemini)** — Gemini engine. ~€0.0001 per prompt. The free tier has a low per-minute cap, so brands with more than ~5 prompts hit HTTP 429 and drop out of scoring (see [Troubleshooting](#troubleshooting)) — treat it as an opt-in add-on, not a starting engine. [aistudio.google.com](https://aistudio.google.com/app/apikey)\n- **Perplexity** — Perplexity Sonar engine. ~€0.005-0.008 per prompt. Paid only. [perplexity.ai/settings/api](https://www.perplexity.ai/settings/api)\n- **SerpAPI** — Google AI Overviews engine. ~€0.005 (free tier) / ~€0.0015 (volume) per prompt. Free tier covers 250 searches/month — enough for development. [serpapi.com/dashboard](https://serpapi.com/dashboard)\n\n**Recommended starting pair: OpenAI + Anthropic (Claude).** Both bill per token with no rate-limit surprises, so your first scan returns clean, scorable data across the ChatGPT and Claude engines — and the Anthropic key also powers prompt generation and content-gap analysis. Solo evaluation runs comfortably under €1/month on the two together. Add Gemini, Perplexity, or SerpAPI deliberately once you want more coverage; Gemini's free tier rate-limits and Google AI Overviews often returns no result (scored as a zero), so leading with the cheapest path can skew your first run.\n\n### Step 2 — Deploy to your Cloudflare account\n\nThe deploy is 6 commands and takes about 5 minutes. See [SETUP.md](https://github.com/AKzar1el/mcp-geo/blob/main/SETUP.md) for the full walkthrough with explanations and troubleshooting, or follow the quick version below.\n\n```bash\n# 1. Install deps\nnpm install\n\n# 2. Log in to Cloudflare\nnpx wrangler login\n\n# 3. Copy the config template\ncp wrangler.example.jsonc wrangler.jsonc\n\n# 4. Create KV namespace + D1 database, paste each printed id into wrangler.jsonc\nnpx wrangler kv namespace create OAUTH_KV\nnpx wrangler d1 create mcp-geo-db\n\n# 5. Set the required secret + at least one engine API key\n# Recommended starting pair — both bill per token, clean first-run data:\nnpx wrangler secret put SEED_SECRET\nnpx wrangler secret put CONNECT_SECRET # recommended — gates who can connect (see SECURITY.md)\nnpx wrangler secret put OPENAI_API_KEY # ChatGPT engine\nnpx wrangler secret put ANTHROPIC_API_KEY # Claude engine + prompt generation\n\n# 6. Apply migrations and deploy\nnpx wrangler d1 migrations apply mcp-geo-db --remote\nnpx wrangler deploy\n```\n\nThe production MCP endpoint is the product-based custom domain:\n\n```\nhttps://geo-mcp.digestseo.com/mcp\n```\n\nUse that exact URL when publishing `digestseo/mcp-geo` on Smithery.ai.\nThe endpoint is OAuth-protected, so Smithery will complete its normal MCP\nauthorization flow during inspection.\n\n### Step 3 — Connect to your MCP client\n\nAfter `wrangler deploy` finishes, you get a URL like\n`https://digestseo-mcp.YOUR-SUBDOMAIN.workers.dev`.\n\n#### Claude.ai (web)\n\nSettings → Connectors → Add custom connector. Paste:\n\n```\nhttps://YOUR-WORKER-NAME.YOUR-SUBDOMAIN.workers.dev/mcp\n```\n\nComplete the OAuth handshake. The connector turns green when ready.\n\n#### Claude Code\n\n```bash\nclaude mcp add --transport http digestseo https://YOUR-WORKER-NAME.YOUR-SUBDOMAIN.workers.dev/mcp\n```\n\nThen run `/mcp` inside Claude Code to complete the OAuth handshake in your browser.\n\n#### Claude Desktop\n\nEdit your Claude Desktop config:\n\n- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`\n- Windows: `%APPDATA%\\Claude\\claude_desktop_config.json`\n\n```jsonc\n{\n \"mcpServers\": {\n \"digestseo\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"mcp-remote\",\n \"https://YOUR-WORKER-NAME.YOUR-SUBDOMAIN.workers.dev/mcp\"\n ]\n }\n }\n}\n```\n\nRestart Claude Desktop after editing.\n\n#### Cursor\n\nEdit `~/.cursor/mcp.json`:\n\n```jsonc\n{\n \"mcpServers\": {\n \"digestseo\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"mcp-remote\",\n \"https://YOUR-WORKER-NAME.YOUR-SUBDOMAIN.workers.dev/mcp\"\n ]\n }\n }\n}\n```\n\nRestart Cursor.\n\n#### Codex CLI\n\nAdd to `~/.codex/config.toml`:\n\n```toml\n[mcp_servers.digestseo]\ncommand = \"npx\"\nargs = [\n \"-y\",\n \"mcp-remote\",\n \"https://YOUR-WORKER-NAME.YOUR-SUBDOMAIN.workers.dev/mcp\",\n]\n```\n\n---\n\n## Environment Variables Reference\n\n| Variable | Required | Default | Description |\n|---|---|---|---|\n| `OPENAI_API_KEY` | opt-in | unset | Enables the ChatGPT engine. Without it, ChatGPT is skipped. |\n| `ANTHROPIC_API_KEY` | opt-in | unset | Enables the Claude engine *and* the Claude-Haiku-powered prompt generator + content-gap analyzer. |\n| `GEMINI_API_KEY` | opt-in | unset | Enables the Gemini engine. Free tier is rate-limited for brands with more than ~5 prompts (see Troubleshooting); opt-in add-on. |\n| `PERPLEXITY_API_KEY` | opt-in | unset | Enables the Perplexity Sonar engine. Paid only. |\n| `SERPAPI_API_KEY` | opt-in | unset | Enables the Google AI Overviews engine (via SerpAPI). |\n| `SEED_SECRET` | **yes** | unset | Shared secret that gates every `/admin/*` route. Pick a high-entropy string. |\n| `CONNECT_SECRET` | recommended | unset | When set, the OAuth connect flow asks for this secret in the browser before issuing a token. Without it, anyone who knows your worker URL can connect an MCP client. See [SECURITY.md](https://github.com/AKzar1el/mcp-geo/blob/main/SECURITY.md). |\n| `TURNSTILE_SITE_KEY` | no | unset | Reserved for forks that add a public `/check` form. Unused by the OSS build. |\n| `TURNSTILE_SECRET_KEY` | no | unset | Same — reserved for forks. |\n\nAll values are set via `wrangler secret put VAR` in production or `.dev.vars` locally. None are stored in `wrangler.jsonc`.\n\n---\n\n## Architecture\n\n```mermaid\nflowchart LR\n C[\"MCP client
(Claude.ai / Claude Code / Cursor / ...)\"] -- \"MCP over HTTP + OAuth\" --> W[\"Cloudflare Worker
digestseo-mcp\"]\n CRON[\"Cron Trigger
every 6h\"] --> W\n W --> DO[\"GeoMcpAgent
(Durable Object, 6 MCP tools)\"]\n W -- \"one self-fetch per engine
via SELF service binding\" --> RE[\"/admin/run-engine
(own invocation per engine)\"]\n RE --> E1[\"OpenAI\"]\n RE --> E2[\"Anthropic\"]\n RE --> E3[\"Gemini\"]\n RE --> E4[\"Perplexity\"]\n RE --> E5[\"SerpAPI
(AI Overviews)\"]\n RE --> DB[(\"D1
brands / prompts / runs /
responses / cache\")]\n DO --> DB\n```\n\nEach engine runs in its own Worker invocation with its own free-plan 50-subrequest budget; results are flushed in a single `D1.batch()` per engine. The whole system fits the Cloudflare free tier for a single brand on a daily cadence.\n\n---\n\n## Security\n\n- `/admin/*` is gated by `SEED_SECRET` (constant-time compared).\n- `/mcp` requires OAuth; set `CONNECT_SECRET` so only people with the secret can complete the connect flow — strongly recommended whenever your worker URL is shared anywhere, since connected clients can call `visibility.refresh` and spend your engine API credits.\n- All engine keys live in Cloudflare's encrypted secret store; all data stays in your own D1 database.\n\nFull details and vulnerability reporting: [SECURITY.md](https://github.com/AKzar1el/mcp-geo/blob/main/SECURITY.md).\n\n---\n\n## Sample Prompts\n\n*The [example report above](#what-it-produces) was generated by the first prompt below.*\n\nOnce the connector is live in Claude.ai (or any MCP client), try:\n\n| Tool | Example prompt |\n|---|---|\n| `visibility.check` | \"How visible is brand_id `acme` on AI right now?\" |\n| `visibility.history` | \"Show me the visibility trend for `acme` over the last 60 days, daily.\" |\n| `visibility.compare` | \"Compare `acme` against asana.com and monday.com over the last 14 days.\" |\n| `visibility.citations` | \"Show me real Perplexity citations for `acme` from the last week.\" |\n| `visibility.content_gaps` | \"What content should `acme` publish to close its visibility gap? Give me the top 5.\" |\n| `visibility.refresh` | \"Refresh `acme` across every available engine right now.\" |\n| `visibility.refresh` | \"Refresh `acme` but only for Gemini and Claude.\" |\n\n---\n\n## Hosted Version\n\nIf you'd rather not run your own Cloudflare account, manage API keys, or pay individual engine bills, the hosted version of DigestSEO runs the same MCP server on managed infrastructure with multi-brand support, scheduled refresh, a web UI, and consolidated billing. Waitlist now open — [join at digestseo.com](https://digestseo.com/#waitlist).\n\n---\n\n## Troubleshooting\n\n- **Worker deploys but tools return empty data** — at least one engine API key is missing. Check `wrangler secret list` and add the keys you intend to use. Engines without keys are silently skipped, which can leave `visibility.check` with no data.\n- **`no engines available` error in logs** — no engine API keys are set at all. Set at least one of `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, `GEMINI_API_KEY`, `PERPLEXITY_API_KEY`, `SERPAPI_API_KEY`.\n- **D1 migration fails** — make sure you've run `npx wrangler d1 migrations apply mcp-geo-db --remote` (and also `--local` for `wrangler dev`). For ad-hoc fixes, `npx wrangler d1 execute mcp-geo-db --remote --file=migrations/0001_initial.sql`.\n- **Custom MCP connector in Claude.ai not connecting** — the URL must end in `/mcp`. The OAuth handshake auto-completes in the OSS build (single dev user); if you set `CONNECT_SECRET`, the browser step shows a one-field form — enter the secret you set during deploy. If it loops, clear the connector and re-add it. Double-check the Worker is publicly reachable (`curl https://YOUR-WORKER-NAME.YOUR-SUBDOMAIN.workers.dev/healthz` should return `ok`).\n- **Cron not firing** — check the Cloudflare dashboard at **Workers & Pages → digestseo-mcp → Settings → Triggers**. The \"Cron Triggers\" section should list `0 */6 * * *`. If it's missing, run `npx wrangler deploy` again — the trigger is registered on deploy. The handler also only dispatches engines for brands whose `refresh_frequency` cadence has elapsed, so a freshly-seeded brand might not fire on the next 6h boundary.\n- **`401 unauthorized` from `/admin/*`** — `X-Seed-Secret` header is missing or doesn't match the deployed `SEED_SECRET`. Re-run `npx wrangler secret put SEED_SECRET` and update your `.env.test`.\n- **Worker returns 404 on self-fetch / error code 1042** — the `services` binding in `wrangler.jsonc` is missing or the `service` name doesn't match the worker's `name` field. `/admin/run-live` self-fetches `/admin/run-engine` via `env.SELF` (a Cloudflare service binding) precisely because a public-URL fetch back to your own `workers.dev` hostname is blocked by Cloudflare's \"Worker called itself\" guard. Confirm the `wrangler.jsonc` you deployed contains `\"services\": [{ \"binding\": \"SELF\", \"service\": \"\" }]` with the same name you set in the top-level `\"name\"` field. After fixing, `npx wrangler deploy` and re-run.\n- **Gemini rate limit (HTTP 429) on every prompt** — the Gemini free tier caps `gemini-2.5-flash-lite` at single-digit requests per minute and a low daily total. For brands with more than ~5 prompts you'll see `status='failed'` rows with 429 error messages, which excludes Gemini from scoring. Workarounds: upgrade to paid Gemini, switch the `MODEL` constant in `src/core/gemini.ts` to a different model with a higher quota, or invoke `/admin/run-engine` for one engine at a time so the per-minute window has time to refill between batches.\n- **`FOREIGN KEY constraint failed` in wrangler tail during `/admin/run-engine`** — the handler defensively `INSERT OR IGNORE`s the runs row before persisting prompt responses. This is an idempotency/FK guard for independently dispatched engine work, so you should not see this on the 0.2.0+ build; if you do, confirm you've deployed the latest `src/index.ts` (`grep -n \"INSERT OR IGNORE INTO runs\" src/index.ts` should match).\n\n---\n\n## Contributing\n\nIssues and PRs welcome. See [CONTRIBUTING.md](https://github.com/AKzar1el/mcp-geo/blob/main/CONTRIBUTING.md) for the short version.\n\n---\n\n## Privacy Policy\n\nWhen you run `digestseo-mcp` locally (npx, the desktop extension, or Docker), all of your data — brands, prompts, runs, responses, and the response cache — stays on your machine in a local SQLite database at `~/.digestseo/digestseo.sqlite` (override with `DIGESTSEO_DB_PATH`). The scan prompts are sent to whichever AI providers you configured with your own API keys (OpenAI, Anthropic, Google, Perplexity, and/or SerpAPI), and only to those; their handling of that traffic is governed by their respective privacy policies. Nothing is ever sent to the author of this project: no telemetry, no analytics, no account.\n\n---\n\n## License\n\n[MIT](https://github.com/AKzar1el/mcp-geo/blob/main/LICENSE).\n\nBuilt and maintained by [Tomi Šeregi](https://tomiseregi.si).\n\n---\n\n## Changelog\n\nSee [CHANGELOG.md](https://github.com/AKzar1el/mcp-geo/blob/main/CHANGELOG.md) for the full version history.\n\n### [0.3.2] — July 27, 2026\n\n- Published `@digestseo/mcp-geo` with synchronized Worker, MCP Registry, and MCPB metadata.\n- Hosted `visibility.*` tool namespaces with typed input/output schemas; local stdio names remain flat.\n- Dedicated `mcp-geo-db` D1 configuration and Cursor/Claude Code plugin metadata.\n- Patched production dependency pins.\n\n### [0.3.0] — July 2026\n\n- Local stdio CLI on npm (`npx -y @digestseo/mcp-geo`) with SQLite storage and inline engine runs.\n- Local brand-management tools: `track_brand`, `list_brands`, `generate_prompts`.\n- Runtime-agnostic core shared by Worker and CLI; D1 + better-sqlite3 `Db` adapters.\n- MCP Registry `server.json`, MCPB desktop extension, Dockerfile, `llms-install.md`.\n\n### [0.2.1] — June 2026\n\n- Optional `CONNECT_SECRET` gate on the OAuth connect flow.\n- Word-boundary brand/competitor matching; exact-domain-or-subdomain linked-citation checks.\n- Per-brand `aliases` and `exclude_terms` (migration 0005) for homograph brands like Monday/Notion.\n- `visibility.history` includes partial runs and drops fully-failed runs.\n- CI workflow (typecheck + unit tests) and a pure-function unit test suite.\n- Docs recommend OpenAI + Anthropic as the starting engine pair.\n- Constant-time secret comparison.\n\n### [0.2.0] — May 2026\n\n- Per-engine HTTP fan-out via `env.SELF` service binding (one worker invocation per engine, dodges Cloudflare's 1042 self-call guard).\n- `status` + `error_message` columns on `prompt_responses` — failed engine calls are now explicit rows, no more `ERROR:` strings in `raw_response`.\n- `INSERT OR IGNORE` on the runs row inside `/admin/run-engine` (handles D1 cross-region replication lag without dropping prompt_responses to FK violations).\n- Bulk D1 batch in each engine's `runLive` (~26 subrequests/invocation instead of ~89; full 20-prompt runs now fit under the free-plan cap).\n- `getLatestCompletedRun` anchored on `EXISTS(ok rows)`; partially-finished runs still show their data.\n- New `POST /admin/cleanup-failed-runs` admin route.\n\n### [0.1.1] — May 2026\n\n- Removed the unreliable bash setup script. Manual install via SETUP.md is now the canonical path.\n\n### [0.1.0] — May 2026\n\n- Initial public release.\n- 5-engine support: ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews.\n- 6 MCP tools.\n- Engines opt-in based on which API keys you provide.\n- Cloudflare Cron Trigger for auto-refresh.\n","changelogMarkdown","videoKey","requiredSecretsJson","publishedAt","priceCents","trialDays",0,"iconType","svg","upstream",{"_116":117,"_118":119,"_120":121,"_122":123,"_124":125,"_126":127},"requiredSecrets",[],"tags",[101,102,103,104,105,106,107,108,109,110,111,112,113,114,115],"assets",[],"stats",{"_99":86,"_100":86},"ratingAvg","reviewCount","aeo","ai-visibility","answer-engine-optimization","brand-monitoring","chatgpt","claude","cloudflare-workers","gemini","generative-engine-optimization","geo","google-ai-overviews","llm","perplexity","seo","typescript","topics",[101,102,103,104,105,106,107,108,109,110,111,112,133,134,135,113,114,115],"license","MIT","language","TypeScript","registryName","io.github.AKzar1el/mcp-geo","homepage","https://digestseo.com/geo-mcp/","packages",[128],{"_129":130,"_131":132,"_76":77},"registryType","npm","identifier","@digestseo/mcp-geo","mcp","mcp-server","model-context-protocol","ENV",{"_138":139,"_140":141,"_142":143},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]