# Causabi GEO Optimizer (npm · geo-optimizer-mcp)

Audit a site for AI readiness: AI-crawler access, schema, FAQ, content structure. Generates fixes.

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

## Components

- npm · `geo-optimizer-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-causabi-geo-optimizer-mcp/geo-optimizer-mcp.md), [page](https://verifymcp.io/servers/com-causabi-geo-optimizer-mcp/geo-optimizer-mcp)

## Channel facts

- Registry: `npm`
- Package: `geo-optimizer-mcp`
- Version: `0.5.1`
- Transport: `stdio`

## Trust breakdown

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. 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-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 968 tokens (~161/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 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 6 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 Causabi GEO Optimizer MCP server?

Causabi GEO Optimizer runs locally as an npm package, launched with npx -y geo-optimizer-mcp. 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 com-causabi-geo-optimizer-mcp -- npx -y geo-optimizer-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-causabi-geo-optimizer-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "geo-optimizer-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-causabi-geo-optimizer-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "geo-optimizer-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-causabi-geo-optimizer-mcp -- npx -y geo-optimizer-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-causabi-geo-optimizer-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "geo-optimizer-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-causabi-geo-optimizer-mcp --command npx --arg -y --arg geo-optimizer-mcp
```

### Hermes

```yaml
mcp_servers:
  com-causabi-geo-optimizer-mcp:
    command: "npx"
    args: ["-y", "geo-optimizer-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-causabi-geo-optimizer-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "geo-optimizer-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-causabi-geo-optimizer-mcp -t stdio -c npx -a -y geo-optimizer-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-causabi-geo-optimizer-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "geo-optimizer-mcp"
      ]
    }
  }
}
```

## 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-04 (score 79, +1)

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

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

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

### 2026-10-30 (score 77, +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-10-28 (score 76, +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-10-26 (score 75, +1)

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

### 2026-10-24 (score 74, +1)

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

### 2026-10-22 (score 73, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-21 (score 57, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.5.0 → 0.5.1

## MCP tools (6)

### `get_product_guide` (~147 tokens)

Get the complete guide for making a website visible in AI search engines (ChatGPT, Gemini, Grok, Claude). Call this FIRST when the user asks about AI search visibility, GEO optimization, why their site isn't cited by AI, or how to get mentioned in ChatGPT. Returns a step-by-step workflow explaining which tools to call and in what order.

Input parameters:

- `scenario` (string): User scenario: 'new_site' — building a site and want AI visibility from day one; 'existing_site' — site exists, want to improve AI citation rate; 'check_only' — just want to check the current GEO sco…

### `analyze_geo_score` (~126 tokens)

Check the GEO (Generative Engine Optimization) score for any existing website. Returns an AI readiness score 0-100, grade A-F, and a breakdown of specific issues that reduce visibility in ChatGPT, Gemini, Grok, Claude, and other AI search engines. Use this for existing sites. For new or rebuilding sites, use make_site_geo_ready instead. After getting the score, call get_geo_fixes to get specific copy-paste fix instructions.

Input parameters:

- `domain` (string, required): Domain to analyze (e.g. 'example.com' or 'https://example.com')

### `get_geo_fixes` (~94 tokens)

Get specific copy-paste fix instructions for a website's GEO (AI search) issues. Returns ready-to-use code for robots.txt, Organization Schema JSON-LD, FAQ Schema, and llms.txt — tailored to that site's current score and issues. Call this AFTER analyze_geo_score to get actionable fixes for an existing site.

Input parameters:

- `domain` (string, required): Domain to get fixes for (e.g. 'example.com')

### `make_site_geo_ready` (~218 tokens)

Generate all GEO (AI search optimization) assets for a website in one shot. Returns ready-to-use Organization Schema JSON-LD, FAQ Schema JSON-LD, llms.txt, and robots.txt snippet — so AI search engines like ChatGPT, Gemini, Grok, and Claude can find, understand, and cite the site. Use this when building or updating a website and the user wants AI search visibility. No API key required.

Input parameters:

- `description` (string, required): What the business does — 1-3 sentences
- `email` (string): Contact email (optional)
- `faq` (array): FAQ pairs (optional — 3-7 Q&A recommended)
- `name` (string, required): Business or site name (e.g. 'Acme Corp')
- `phone` (string): Contact phone (optional)
- `services` (array): List of services or products (e.g. ['Web design', 'SEO', 'Hosting'])
- `url` (string, required): Site URL (e.g. 'https://acme.com')

### `suggest_monitoring_config` (~189 tokens)

Generate a complete AI monitoring configuration for a business: target audience descriptions, monitoring location, and query suggestions. Use this when the user describes their business and wants to set up monitoring for the right audience and location. Returns ready-to-use configuration JSON and API instructions to apply it. AI agents can use this to auto-fill monitoring settings without the user having to manually describe their audience.

Input parameters:

- `business_description` (string, required): What the business does — the more detail, the better the config. Include: who the customers are, what problems you solve, where you operate.
- `business_name` (string, required): Business name
- `location` (string): Primary location or service area (city, region, or country). Used to localize AI search monitoring.
- `target_queries` (array): Optional: existing target queries. If provided, audience suggestions will be tuned to match how these queries are typically asked.

### `get_site_report` (~194 tokens)

Get a client-ready report for a site: GEO score breakdown, and — if a Visibility Report share link (slug) is available — AI mention-rate results across engines (ChatGPT, Claude, Gemini, Grok). Use this when the user asks for 'a report on this site', 'how is this client doing', or wants something to hand to a client. Pass `report_slug` if you have a causabi.com/report/<slug> link (full report, no API key needed). Pass only `domain` for a score-only summary (no monitoring history available without a Causabi login).

Input parameters:

- `domain` (string): Domain to report on (e.g. 'example.com'). Required if report_slug is not given.
- `report_slug` (string): Visibility Report slug from a causabi.com/report/<slug> share link. When given, returns the full mention-rate report instead of just the score.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-causabi-geo-optimizer-mcp/geo-optimizer-mcp#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 73
- 2026-10-22: 73
- 2026-10-21: 57
- 2026-10-20: 72
- 2026-10-19: 71
- 2026-10-18: 71
- 2026-10-17: 71
- 2026-10-16: 70

## Common questions

### What is the Causabi GEO Optimizer MCP server?

Causabi GEO Optimizer is an MCP server listed in the public MCP registry as com.causabi/geo-optimizer-mcp. Audit a site for AI readiness: AI-crawler access, schema, FAQ, content structure. Generates fixes. This page covers its npm package (geo-optimizer-mcp).

### Is the Causabi GEO Optimizer MCP server safe to use?

Causabi GEO Optimizer scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Causabi GEO Optimizer MCP server expose?

Causabi GEO Optimizer exposes 6 tools: get_product_guide, analyze_geo_score, get_geo_fixes, make_site_geo_ready, suggest_monitoring_config, get_site_report. Their descriptions and schemas cost roughly 968 tokens of context every time the server is loaded.

### Is the Causabi GEO Optimizer MCP server still maintained?

Causabi GEO Optimizer is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Causabi GEO Optimizer MCP server under?

Causabi GEO Optimizer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Causabi GEO Optimizer MCP server?

VerifyMCP ran 16 checks on Causabi GEO Optimizer, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/geo-optimizer-mcp
- Socket report: https://socket.dev/npm/package/geo-optimizer-mcp
- Repository: https://github.com/SHADRINMMM/geo-optimizer-mcp
- Website: https://causabi.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-causabi-geo-optimizer-mcp/geo-optimizer-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-causabi-geo-optimizer-mcp/geo-optimizer-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-causabi-geo-optimizer-mcp/geo-optimizer-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-causabi-geo-optimizer-mcp/geo-optimizer-mcp