Causabi GEO Optimizer
NPM · GEO-OPTIMIZER-MCP
Audit a site for AI readiness: AI-crawler access, schema, FAQ, content structure. Generates fixes.
Available components
Last scanned (8 hours ago)
Scores higher than 62% of npm servers
Category Marketing and SEO
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.5.0 → 0.5.1 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/geo-optimizer-mcp@0.5.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_geo_score ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to analyze (e.g. 'example.com' or 'https://example.com') |
No output schema declared.
No examples provided.
get_geo_fixes ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to get fixes for (e.g. 'example.com') |
No output schema declared.
No examples provided.
get_product_guide ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
get_site_report ~194
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
make_site_geo_ready ~218
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What the business does — 1-3 sentences |
| string | – | Contact email (optional) | |
| faq | array | – | FAQ pairs (optional — 3-7 Q&A recommended) |
| name | string | yes | 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 | yes | Site URL (e.g. 'https://acme.com') |
No output schema declared.
No examples provided.
suggest_monitoring_config ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_description | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · geo-optimizer-mcp
claude mcp add com-causabi-geo-optimizer-mcp -- npx -y geo-optimizer-mcp
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.