GEOScore MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEOSCORE_API_KEY | No | Your GEOScore API key. Obtain from https://geoscoreai.com/api-keys. Required for pro features like deep scan, fix generation, and visibility checks. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geo_scanB | Scan a website for AI search (GEO) readiness. Returns a score (0-100), grade (A-F), and 11 technical checks covering robots.txt, llms.txt, structured data, meta tags, content structure, sitemap, HTTP headers, content quality, internal linking, AI crawl access, and citation value. Each check includes specific issues found and actionable fix suggestions. |
| geo_deep_scanA | Deep scan a domain with full pro-level analysis. Returns everything from geo_scan plus: complete implementation markdown, AI-generated llms.txt, Schema.org JSON-LD fixes, meta tag optimizations, GEO value model with business insights, human-readable report, and 14-day sprint plan. Requires an API key with Pro plan or higher. |
| geo_generate_fixB | Generate ready-to-use fix code for a specific GEO issue. Scans the domain and generates the fix file content that can be directly written to the project. Fix types: 'llms_txt' (generate llms.txt file), 'schema' (JSON-LD structured data), 'meta' (meta tag improvements), 'robots' (AI-friendly robots.txt), 'sitemap' (XML sitemap guide). |
| geo_get_profileA | Get a domain's GEO score history and profile. Returns the latest score, best score, total scan count, first/last scanned dates, and site metadata. Useful for tracking improvements over time. |
| geo_compareA | Compare two domains' GEO readiness scores side by side. Returns both domain profiles with scores, grades, and metadata for direct comparison. Useful for competitive analysis. |
| geo_check_visibilityA | Check if a domain is being cited by AI search engines (ChatGPT, Perplexity, Claude). Tests brand-related queries against multiple AI engines and reports citation status. Requires Pro API key. |
| geo_get_reportB | Retrieve a previously saved GEO scan report by its report ID. Returns the full report data including domain, score, grade, and all check details. |
| geo_create_api_keyA | Create a free GEOScore API key for programmatic access. Free keys allow 10 scans/day. Returns the API key that can be used with other geo_ tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| geo-optimize | Complete GEO optimization workflow: scan a domain, analyze issues, generate fixes, and apply them to the project. |
| geo-audit | Perform a comprehensive GEO audit and generate a report with prioritized recommendations. |
| geo-compare | Compare your site's GEO readiness against a competitor. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| What is GEO? | Introduction to Generative Engine Optimization |
| llms.txt Guide | How to create an effective llms.txt file |
| Schema.org for AI | Using structured data to improve AI discoverability |
| robots.txt for AI Crawlers | Configure robots.txt to allow AI search engine access |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose (scan, compare, fix, profile, visibility check, etc.), with no overlapping functionality. Descriptions clearly differentiate them.
All tools follow the verb_noun pattern with a consistent 'geo_' prefix and snake_case (e.g., geo_scan, geo_get_profile), making the naming predictable and easy to navigate.
8 tools is well within the optimal range for a focused server. Each tool serves a necessary function without redundancy or bloat.
The tool set covers the primary GEO lifecycle: scanning, profiling, reporting, fix generation, comparison, and API key management. Minor gaps like a 'list all domains' or 'delete scan' tool are non-essential.