geoready-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_website_geo_readinessA | Runs a live 8-point Generative Engine Optimization (GEO) & ChatGPT Shopping audit on any public website URL: checks AI crawler access, /llms.txt, Accept: text/markdown token bloat, Content-Signal headers, and JSON-LD schema, and returns ready-to-deploy remediation snippets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool in the set, there is no possibility of misselection or overlapping purpose. The tool's scope (a GEO/ChatGPT Shopping readiness audit on a URL) is explicit and self-contained.
The single name, audit_website_geo_readiness, follows a clear snake_case verb_noun_resource pattern and is descriptive. It cannot demonstrate consistency across a set, so it falls just short of a 5.
One tool is thin for a server, even a narrowly scoped one; the 8-point audit is bundled into a single call with no granular options. It is defensible for a single-purpose auditor but leaves no room for narrower operations.
The audit itself appears comprehensive (crawler access, llms.txt, markdown tokens, Content-Signal, JSON-LD) and returns remediation snippets, covering the core purpose. However, there is no way to re-audit after fixes, batch multiple URLs, or retrieve prior results, creating dead ends for follow-up workflows.