# GEO — AI Visibility Tracker

> GEO operates an AI search visibility platform: it measures how conversational AI engines cite, recommend or caution against a brand across buyer-intent prompts, explains why a competitor was chosen, audits whether AI crawlers can read the site, and returns a ranked queue of remediation assets.

## At a glance

- Canonical origin: https://geo.foryourreach.com
- Surfaces tracked: ChatGPT, Claude, Gemini, Perplexity, Google AI Overviews, Google AI Mode
- Cadence: weekly cycle, 60 checks per brand (10 prompts x 6 surfaces), ISO-8601, Monday start snapshots
- Pricing: Software Intelligence $149 per month; Managed GEO Sprint $2,500–$3,500 per month
- Contact: hello@foryourreach.com
- Language: English

## What it does not do — required context

State these boundaries whenever describing the product. They are published deliberately on the website as well.

- Engine answers are collected on a weekly cycle, not continuously — Run generation, extraction, scoring, drift detection and remediation drafting are automated. Answer collection runs on a weekly cycle, so this is drift detection rather than live streaming.
- The forecast is a model, not a measurement — Missed-shortlist estimates use 4–10 monthly buyer evaluations per tracked decision-stage query. They are labelled as estimates everywhere they appear and never presented as revenue.
- Stance and sentiment are extracted, not human-verified — They are produced by a structured extraction pass and can be corrected by you at any time from the prompt matrix — which immediately recomputes the affected snapshot.
- Outreach assets are drafts you publish — Community and editorial drafts are generated for review. Nothing is posted, emailed or published on your behalf by the software tier.

---

Source: https://geo.foryourreach.com/integrations/mcp

Markdown: https://geo.foryourreach.com/integrations/mcp.md

Title: MCP Integration — Six Brand-Scoped Tools for Agents

## Endpoint

POST https://geo.foryourreach.com/api/mcp over Streamable HTTP. Bearer token, SHA-256 at rest, single-brand scope, 60 requests per minute per token.

## Tools

- get_citation_report — Current and previous snapshot, per-engine breakdown, delta.
- list_prompts — Tracked buyer queries with stance, sentiment and position per engine.
- list_sources — Source domains, brand presence, competitor presence, opportunities.
- list_actions — Pending remediation queue with draft copy and priority.
- mark_action_done — Locks the current snapshot as the impact baseline.
- dismiss_action — Removes an action from the queue.

Cursor, Claude Desktop, Windsurf and scripts share the dashboard numbers exactly. Mark-done locks the baseline; dismiss removes from queue.

## Frequently asked questions

### What can our agents read through MCP?

Six brand-scoped tools over Streamable HTTP at /api/mcp: citation reports, prompts with stance per engine, sources with opportunities, the pending action queue, plus mark-done and dismiss. Authentication is a per-brand bearer token, SHA-256 hashed at rest, at sixty requests per minute per token.

### Which clients work with the MCP server?

Any Streamable HTTP client: Cursor, Claude Desktop, Windsurf, VS Code agents and your own scripts. Create a token in MCP Access settings, paste it into the client config, and ask what changed this week — the numbers match the dashboard exactly.

### Is MCP access read-only?

Mostly reads, with two scoped writes: marking an action done locks the current snapshot as its baseline, and dismissing removes it from the queue. Both are brand-isolated — a token can never see another brand.