# aeogeo (remote · mcp.aeogeo.site)

Deterministic AEO/GEO checks and a source-cited rulebook for AI search, for your agent.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `mcp.aeogeo.site`: 78/100 (this document), [markdown](https://verifymcp.io/servers/site-aeogeo-aeogeo/mcp.md), [page](https://verifymcp.io/servers/site-aeogeo-aeogeo/mcp)
- remote · `mcp.aeogeo.site`: 37/100, [markdown](https://verifymcp.io/servers/site-aeogeo-aeogeo/mcp-2.md), [page](https://verifymcp.io/servers/site-aeogeo-aeogeo/mcp-2)

## Channel facts

- Endpoint: `https://mcp.aeogeo.site`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2048 tokens (~227/item across 9 items; 6 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the aeogeo MCP server?

aeogeo is a hosted endpoint at https://mcp.aeogeo.site/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http site-aeogeo-aeogeo 'https://mcp.aeogeo.site/'
```

### Cursor

```json
{
  "mcpServers": {
    "site-aeogeo-aeogeo": {
      "url": "https://mcp.aeogeo.site/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "site-aeogeo-aeogeo": {
      "type": "http",
      "url": "https://mcp.aeogeo.site/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.site-aeogeo-aeogeo]
url = "https://mcp.aeogeo.site/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "site-aeogeo-aeogeo": {
      "type": "remote",
      "url": "https://mcp.aeogeo.site/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add site-aeogeo-aeogeo --url 'https://mcp.aeogeo.site/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  site-aeogeo-aeogeo:
    url: "https://mcp.aeogeo.site/"
```

### Netclaw

```json
{
  "McpServers": {
    "site-aeogeo-aeogeo": {
      "Transport": "http",
      "Url": "https://mcp.aeogeo.site/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add site-aeogeo-aeogeo -t streamable-http -u 'https://mcp.aeogeo.site/'
```

### Other

```json
{
  "mcpServers": {
    "site-aeogeo-aeogeo": {
      "type": "http",
      "url": "https://mcp.aeogeo.site/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 76, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-17 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-16 (score 75, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-15 (score 75, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-14 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `plan_audit` (~395 tokens)

Plan an audit

Plan an audit or a research task. Give your goal, the target and your limits; get back an ordered list of aeogeo tool calls with the quota each costs, which steps are semantic (judge: agent), what was deferred to fit your budget, your tier's daily limits, and the semantic-review rubric for the page type. Deterministic: no inference, no fetch, same input gives the same plan. The semantic review and report steps are never dropped to fit a budget. Use when: You are about to audit a page, a draft or a site, or answer a research question, and want the right calls for your goal, effort and remaining quota. Avoid when: You already know the single tool you need, such as scan_url on one URL. Do not claim: A plan is not a finding. Nothing was scanned or evaluated. Verify: Run the steps in order; the semantic review step is yours to do.

Input parameters:

- `budget` (object): Optional limits. calls: tool calls you will spend. rules: rules you can still draw today. pages: site-scan pages left today.
- `content_type` (string): Content type used to select applicable checks.
- `effort` (string): quick (default): fewest calls. standard: two rule lookups. thorough: three, plus insights.
- `goal` (string, required): fix_errors: engine defects first, cheapest path. pre_publish: lint a draft, then scan after deploy. citation_readiness: adds evidence and changelog lookups. site_audit: whole site, sampled semantic r…
- `page_count` (integer): Pages on the site, when known; sizes the scan_site step.
- `target_kind` (string): What is being audited: a live url, a whole site, draft html, draft text, a json-ld block, or none (research).

### `scan_url` (~473 tokens)

Scan a page

Run the AI-search hygiene checks on a public URL. A grade is not a citation and does not measure AI mentions. Free callers get per-group grades plus every failed fundamental (readiness levels L0-L3) with how to fix it; Pro/Team callers also get rule IDs, severity and evidence for every check, plus a work list ordered by weight. propose is always true: each fix is a proposal for a person to apply. Free results may be cached for up to an hour; keyed scans always fetch the page fresh. Batched callers pass detail=failures to drop passing checks. A page whose robots.txt disallows it for aeogeo-scanner is not fetched (blocked_url). The checks cover technical readiness only; each result says what a full audit adds in semantic_review (guidance.semantic_review on keyed page scans). Use when: The page is already public and you want the bytes a crawler receives. Avoid when: The draft is only local. Use lint_html for HTML, lint_text for markdown, or audit_schema for JSON-LD. content_type is an argument on those tools and on scan_url, not a separate tool. Do not claim: A grade or a pass is not a citation. The check says the page matches the rulebook. Verify: Deploy the edit, then call scan_url again. A keyed scan fetches fresh. judge: engine — trust the pass/fail from the deterministic check (access, rendering, and mechanical structure). judge: agent — your agent re-reads the rule text and decides; the label comes from the deterministic judgeForCheck mapping, not an LLM on our side.

Input parameters:

- `content_type` (string): Optional. What the page is, for pages that declare no schema.org @type or og:type. Without it the scanner infers the type and, when it cannot, skips the type-specific checks with a reason.
- `detail` (string): Keyed callers only; a free scan already lists failures alone and ignores it. full (default): every check. failures: only failed and skipped checks plus the page and group grades, grade_basis and the…
- `url` (string, required): Absolute public http(s) URL to scan.

### `list_categories` (~90 tokens)

List rule categories

List the rulebook categories with the number of active rules in each. Use when: You need a category name before reading rules. Avoid when: You are grading a page. Use scan_url or a lint tool. Do not claim: A category count is not a coverage score for any site. Verify: Pass a name from this list to fetch_sample_rules, or to fetch_rules when you have a key.

### `fetch_sample_rules` (~124 tokens)

Fetch sample rules

Fetch a stable teaser sample of up to 20 public rules (no evidence or remediation). Optionally filter by category. Use when: You have no API key and need to see what a public rule looks like. Avoid when: You have a key and need the full rule. Use fetch_rules or search_rules. Do not claim: A teaser has no remediation. It is not enough to apply the rule. Verify: This is a read. Nothing on the page changes until you edit and scan or lint.

Input parameters:

- `category` (string): Optional category name from list_categories.

### `get_hook_snippet` (~125 tokens)

Get agent setup snippet

Return a ready-to-paste snippet that hooks this rulebook into your agent: AGENTS.md instructions, Cursor rules, or a Claude Code skill. Use when: You are onboarding a repo and need the install text for that client. Avoid when: The snippet is already installed and you are checking a page. Do not claim: Installing the snippet does not scan the site. Verify: Call tools/list. A free snippet names only free tools; a keyed snippet names the lint chain.

Input parameters:

- `client` (string, required): Target client: agents_md, cursor, or claude.

### `export_report` (~316 tokens)

Create a report link

Create a private, shareable static report link for 1-2 public URLs. The report is rendered from the same scan output as scan_url — free callers get the aggregate report, Pro/Team callers get the detailed one — and the link works in any browser without an API key. Compare mode puts two URLs side by side; keyed reports add a per-rule delta. Use when: You want a link to paste into Slack, docs, email, or a pull request so a person (or link-preview bot) can read the scan without the API key. Avoid when: You need the raw scan result right now. Use scan_url and keep the JSON in context. Do not claim: A report is a snapshot of one scan — not a citation and not a live measurement. Verify: Open the returned https://aeogeo.site/r/<id> URL, or append ?format=md or ?format=json for other export formats. expires_at says when the link stops working.

Input parameters:

- `expires_in_days` (integer): How long the link works, in days. Default: 30 for a Pro/Team report (it shows paid detail to anyone with the link), 90 for a free one. The owner can revoke a Pro/Team link earlier at https://mcp.aeog…
- `mode` (string): single (default for one URL) or compare (two URLs, side by side).
- `urls` (array, required): One URL for a single report, or two URLs for compare mode.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/site-aeogeo-aeogeo/mcp#diagnostics

## Score history

- 2026-11-22: 78
- 2026-11-21: 78
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 76
- 2026-11-17: 76
- 2026-11-16: 75
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 74
- 2026-11-12: 74
- 2026-11-11: 73
- 2026-11-10: 73
- 2026-11-09: 72
- 2026-11-08: 72
- 2026-11-07: 64

## Common questions

### What is the aeogeo MCP server?

aeogeo is an MCP server listed in the public MCP registry as site.aeogeo/aeogeo. Deterministic AEO/GEO checks and a source-cited rulebook for AI search, for your agent. This page covers its hosted endpoint (https://mcp.aeogeo.site).

### Is the aeogeo MCP server safe to use?

aeogeo scores 78 out of 100 on VerifyMCP. 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 aeogeo MCP server expose?

aeogeo exposes 6 tools: plan_audit, scan_url, list_categories, fetch_sample_rules, get_hook_snippet, export_report. Their descriptions and schemas cost roughly 1,523 tokens of context every time the server is loaded.

### Does the aeogeo MCP server require authentication?

No. We connected to aeogeo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the aeogeo MCP server still maintained?

aeogeo is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the aeogeo MCP server?

VerifyMCP ran 13 checks on aeogeo, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.aeogeo.site/
- Repository: https://github.com/aeogeosite/aeogeo
- Website: https://aeogeo.site/docs/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/site-aeogeo-aeogeo/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/site-aeogeo-aeogeo/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/site-aeogeo-aeogeo/mcp.json
- HTML version of this page: https://verifymcp.io/servers/site-aeogeo-aeogeo/mcp
