Alerts, API and MCP

Alerts, API and MCP: your AI visibility data where you work

GeoRush checks your data every morning and alerts you when your mention rate drops, a competitor overtakes you, negative mentions rise or data collection fails. Alerts reach the app, Slack or a signed webhook. On the Growth and Agency plans you also get a REST API and an MCP server to query your data from scripts or from Claude, ChatGPT and Cursor.

Updated on

The problem: nobody checks a dashboard every day

AI answers change from week to week: a new model, a source that stops citing you, a competitor publishing a comparison page. If you only find out when you open the dashboard, you are already late.

And if you work with data (a Looker Studio dashboard, an internal report, an AI agent), copying numbers by hand does not scale. GeoRush handles both: it alerts you only when something really changes, and it lets you read your GEO (generative engine optimization) data through an API or MCP (Model Context Protocol, the standard AI assistants use to connect to external tools).

Which alerts you get

Visibility alerts compare the last 7 days with the 7 before using 95% confidence ranges, so you are not alerted about noise.

AlertWhen it fires
Mention rate droppedWith at least 20 answers in each week, this week's range sits entirely below last week's: a real drop, not normal variation.
A competitor overtook youA rival that was behind you now clearly appears more often than you (its range sits above yours).
More negative mentionsThe share of negative mentions rises by 15 points or more versus the previous week.
Answers are failingIn the last 24 hours at least 5 answers failed, and they make up at least 20% of the total.
Page got slowerA page speed monitor sees the grade drop, LCP rise more than 20% or TBT rise more than 50%.

Each alert is sent only once per period, so you do not get repeats.

How to connect

  1. 1

    Slack

    Paste a Slack incoming webhook URL and choose alerts, the Monday weekly digest, or both. A button sends a test message.

  2. 2

    Signed webhook

    GeoRush posts JSON over HTTPS to your URL. If you set a secret, every delivery is signed with HMAC SHA-256 in the X-GeoRush-Signature header so you can verify it came from GeoRush.

  3. 3

    REST API

    In your workspace API settings, create a read-only or read-write key. It is shown once (GeoRush only keeps a hash of it) and you can revoke it at any time.

  4. 4

    MCP server

    Add https://georush.si/mcp with your key to your MCP client. For clients that only support local servers, such as Claude Desktop, use the mcp-remote bridge.

What you can read through the API and MCP

The REST API lives at https://georush.si/api/v1: JSON over HTTPS, with your key as a Bearer token and a limit of 120 requests per minute per key. The MCP server exposes the same reads as tools.

  • Brands (list_brands): your brands with mention rate, share of voice and citation rate.
  • Brand overview (brand_overview): mention rate with a 95% range, share of voice, citation rate, position, sentiment, themes and per-engine rates.
  • Questions (prompt_performance): how often you are named for each tracked question, per engine.
  • Competitors (competitor_comparison): your brand versus the rivals you track, per engine.
  • Sources (top_sources): the sites and pages AI answers cite, labeled own, competitor or third party.
  • Next steps (next_steps): prioritized actions with the numbers behind each.
  • Answers (search_answers): search stored answers by text, engine or question.
  • Add questions (API only): with a write key, POST /v1/brands/{id}/prompts adds questions to tracking.

What you do with it

Connect Slack on day one: it is the simplest way for the team to hear about a drop or a rising rival. When an alert fires, open competitor analysis or brand perception to see why, and check your action plan.

Use the API to pull your metrics into Looker Studio, a spreadsheet or your own dashboard, and MCP to ask questions about your data from Claude, ChatGPT or Cursor. Alerts and the Slack and webhook integrations are on every plan; the API and MCP are on Growth and Agency (see pricing). If an integration fails 10 times in a row, GeoRush pauses it and you can switch it back on.

Hear about it before you lose ground

Create a free account, connect Slack and get your first alert when something really changes.

Frequently asked questions

Visibility alerts compare two weeks using 95% confidence ranges and require at least 20 answers. They only fire when the ranges stop overlapping, meaning the change is real and not normal AI variation.

Growth and Agency. Alerts, Slack and webhooks are available on every plan.

Any client that supports MCP over HTTP, such as Claude, ChatGPT or Cursor. For clients that only support local servers, such as Claude Desktop, use the mcp-remote bridge.

Only if you create a read-write key, and only to add questions to tracking. Read-only keys cannot change anything.

120 requests per minute per key. Above that, the API returns a 429 error telling you how long to wait.

If you set a secret when creating the webhook, each delivery carries an X-GeoRush-Signature header with an HMAC SHA-256 signature of the body computed with that secret.

Keep reading