Provides an optional integration with OpenAI's API to generate a human-readable summary of the audit results using GPT-4.1-mini (or custom model).
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@geo-audit-mcp Audit https://example.com for GEO signals"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Lightweight MCP server for GEO (Generative Engine Optimization) site audits. Checks 31 signals across 6 pillars — Technical Crawlability, Content Structure, Schema & Metadata, E-E-A-T, Citation Readiness, and Governance — and returns a score, pillar breakdowns, and an actionable fix prompt.
This server provides one tool only:
geo_site_audit
{
"score": 72,
"pillars": {
"technical": { "pass": 4, "fail": 1, "warn": 0, "na": 0, "total": 5, "pct": 80 },
"content": { "pass": 3, "fail": 0, "warn": 1, "na": 0, "total": 4, "pct": 88 },
"schema": { "pass": 2, "fail": 1, "warn": 1, "na": 0, "total": 4, "pct": 63 },
"eeat": { "pass": 4, "fail": 1, "warn": 2, "na": 0, "total": 7, "pct": 71 },
"citations": { "pass": 6, "fail": 1, "warn": 3, "na": 0, "total": 10, "pct": 75 },
"governance": { "pass": 1, "fail": 0, "warn": 0, "na": 0, "total": 1, "pct": 100 }
},
"checks": [
{ "id": "T1", "pillar": "technical", "title": "Page reachable over HTTPS", "status": "pass", "message": "Page returned HTTP 200." },
{ "id": "B1", "pillar": "content", "title": "Answer-first opening mentions brand", "status": "fail", "message": "Add a 2–3 sentence opening that names your brand...", "evidence": "Welcome to our platform..." }
],
"fixPrompt": "You are improving GEO readiness for MyBrand...",
"summary": "- [Content] Improve heading hierarchy...",
"stats": { "words": 1523, "headings": 14, "externalLinks": 8, "jsonLdBlocks": 2 },
"auditedUrl": "https://example.com/page"
}Field | Description |
| Overall GEO readiness score (0–100), weighted across 6 pillars |
| Per-pillar pass/fail/warn counts and percentage |
| All 31 individual check results with status, message, and evidence |
| Actionable fix prompt — paste into Claude, Cursor, or your site editor |
| Human-readable summary (LLM-generated if |
| Page-level statistics: word count, headings, external links, JSON-LD blocks |
| The normalized URL that was audited |
Related MCP server: seo-gaca-mcp
This server uses your own API keys. Usage and billing are tied to your provider accounts. No API key is strictly required — the audit runs fully offline using static HTML analysis. Optionally set OPENAI_API_KEY for LLM-powered summary.
Variable | Required | Description |
| Optional | OpenAI API key for LLM-generated audit summary. Without it, the summary is auto-generated from check results. |
| Optional | Custom OpenAI-compatible endpoint (default: |
| Optional | HTTPS proxy URL for OpenAI API calls (e.g. |
| Optional | HTTPS proxy URL for fetching the target website. |
npm install
npm run buildclaude_desktop_config.json){
"mcpServers": {
"geo-audit-mcp": {
"command": "node",
"args": ["<ABSOLUTE_PATH>/geo-audit-mcp/dist/index.js"],
"env": {
"OPENAI_API_KEY": "<YOUR_OPENAI_API_KEY>"
}
}
}
}{
"mcpServers": {
"geo-audit-mcp": {
"command": "node",
"args": ["<ABSOLUTE_PATH>/geo-audit-mcp/dist/index.js"],
"env": {
"OPENAI_API_KEY": "<YOUR_OPENAI_API_KEY>",
"OPENAI_HTTPS_PROXY": "http://127.0.0.1:7890"
}
}
}
}{
"url": "https://example.com/pricing",
"brand_name": "Example",
"page_type": "product"
}Parameter | Required | Description |
| Yes | Full URL to audit. Must start with |
| No | Brand name — improves the accuracy of the opening-content check (B1). |
| No | Hint: |
T1–T5: HTTPS reachability, AI crawler robots.txt rules, llms.txt presence, readable text without JavaScript, canonical URL.
B1–B4: Answer-first brand mention, heading hierarchy, paragraph chunking, quotable blocks (lists/FAQ).
C1–C4: Title + meta description, Organization/WebSite JSON-LD, page-type structured data, FAQPage schema.
E1–E7: Author/entity signals, visible byline, About/Contact links, Organization JSON-LD with sameAs, Privacy/Terms links, authority review links, publication date.
R1–R10: External reference links, authoritative review domains, link diversity, in-content links, citable blocks, quotable facts, source attribution, entity sameAs, page citability score, citation-ready passage ratio.
G1: Sitemap reachability.
The audit fetches the target page via direct HTTP request (with browser-like User-Agent). Some sites with aggressive bot protection may block the request.
The audit is stateless — no data is stored or logged.
SSRF protection is built in: internal IPs, localhost, and cloud metadata endpoints are blocked.
If OPENAI_API_KEY is set, the summary uses GPT-4.1-mini by default. Set OPENAI_MODEL to override.
Fix prompts are designed to be pasted directly into Claude, Cursor, or your site editor — they target HTML, meta tags, and JSON-LD only.
Never commit real credentials into git. Use env vars only.
Built by gptmelo.com — the GEO brand monitor for ChatGPT.
Run a comprehensive GEO (Generative Engine Optimization) audit on a single page URL. Checks 31 signals across 6 pillars — Technical Crawlability, Content Structure, Schema & Metadata, E-E-A-T, Citation Readiness, and Governance. Returns a score, pillar breakdowns, per-check pass/fail/warn results, a human-readable summary, and an actionable fix prompt ready to paste into Claude, Cursor, or your site editor.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The full URL to audit (homepage, product page, or article page). Must start with https:// or http://. | |
| page_type | No | Optional. Hint about the page type. Auto-detected from the URL path if omitted. | |
| brand_name | No | Optional. Your brand or company name — improves the accuracy of the opening-content check. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It explicitly states the tool reads a URL and returns audit results, implying no side effects. It does not disclose rate limits or authentication needs, but the context (audit) suggests a safe read operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is a single focused paragraph with a bullet-like list of outputs. It is efficient but could be more front-loaded with the core purpose before enumerating details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description thoroughly explains what the tool returns (score, pillar breakdowns, pass/fail/warn, summary, fix prompt). It covers the key aspects a user needs to know.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the description adds minimal parameter detail. It mentions 'single page URL' and 'brand name for accuracy', but the schema already documents these. Baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description specifies a concrete action (audit), a resource (single page URL), and a domain (GEO). It lists 31 signals across 6 pillars and the return types, clearly distinguishing it from any potential sibling (none provided).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description states when to use (for a GEO audit) but does not mention when not to use, prerequisites, or alternative tools. Slightly ambiguous for an agent needing to decide.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clearly delineated by its name and description.
The sole tool uses a clear, descriptive snake_case name that follows a consistent pattern (geo_site_audit). No inconsistency can exist with only one tool.
While one tool is on the low end, it is borderline acceptable for a specialized, single-purpose server. The server's entire functionality is encapsulated in this one comprehensive audit tool.
The single tool fully delivers on the server's purpose: running a complete GEO audit across 31 signals and 6 pillars. No additional tools are needed for the stated scope.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
SEO MCP server for keyword research, SERP analysis, audits, and Search Console workflows.
SEO MCP server: crawl your site, find AI-visibility gaps, and ship the fix from your coding agent.
GEO scores and content-rewrite suggestions for any web page, as MCP tools.
Local SEO: MCP for local business audits with tools and guidance.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/carter-wzq/geo-audit-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
