mcpField
G
Geo Audit MCP

Geo Audit MCP

Local
gptmelo.comProductivity1Updated 17w ago

About Geo Audit MCP

Geo Audit MCP audits a website page for Generative Engine Optimization readiness. It is for site owners and editors, and reports check results across six pillars along with an overall score and a prompt for fixes.

Key features

  1. 01Evaluate 31 signals across six pillars
  2. 02Return an overall readiness score
  3. 03Show pillar-level checks and results
  4. 04Generate an actionable fix prompt
  5. 05Run static HTML analysis without an API key

Use cases

  1. 01Check a page's readiness for AI citations
  2. 02Review technical, content, and schema issues
  3. 03Use the fix prompt to guide page edits

MCP support

It exposes the `geo_site_audit` tool to MCP clients. The tool accepts a URL and optional brand and page-type hints, then returns the audit results.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

geo-audit-mcp

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

Output format

{
  "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"
}
What each part means
FieldDescription
scoreOverall GEO readiness score (0–100), weighted across 6 pillars
pillarsPer-pillar pass/fail/warn counts and percentage
checksAll 31 individual check results with status, message, and evidence
fixPromptActionable fix prompt — paste into Claude, Cursor, or your site editor
summaryHuman-readable summary (LLM-generated if OPENAI_API_KEY is set, else auto-generated)
statsPage-level statistics: word count, headings, external links, JSON-LD blocks
auditedUrlThe normalized URL that was audited

BYOK

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.

Required environment variables

VariableRequiredDescription
OPENAI_API_KEYOptionalOpenAI API key for LLM-generated audit summary. Without it, the summary is auto-generated from check results.
OPENAI_BASE_URLOptionalCustom OpenAI-compatible endpoint (default: https://api.openai.com/v1).
OPENAI_HTTPS_PROXYOptionalHTTPS proxy URL for OpenAI API calls (e.g. http://127.0.0.1:7890).
WEBSITE_HTTPS_PROXYOptionalHTTPS proxy URL for fetching the target website.

Quick Start

npm install
npm run build

MCP Config Example

Claude Desktop (claude_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>"
      }
    }
  }
}
Cursor / Windsurf / Other MCP clients
{
  "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"
      }
    }
  }
}

Tool Input

{
  "url": "https://example.com/pricing",
  "brand_name": "Example",
  "page_type": "product"
}
ParameterRequiredDescription
urlYesFull URL to audit. Must start with https:// or http://.
brand_nameNoBrand name — improves the accuracy of the opening-content check (B1).
page_typeNoHint: homepage, product, or article. Auto-detected from URL path if omitted.

What gets checked (31 signals, 6 pillars)

Technical Crawlability (5 checks)

T1–T5: HTTPS reachability, AI crawler robots.txt rules, llms.txt presence, readable text without JavaScript, canonical URL.

Content Structure (4 checks)

B1–B4: Answer-first brand mention, heading hierarchy, paragraph chunking, quotable blocks (lists/FAQ).

Schema & Metadata (4 checks)

C1–C4: Title + meta description, Organization/WebSite JSON-LD, page-type structured data, FAQPage schema.

E-E-A-T (7 checks)

E1–E7: Author/entity signals, visible byline, About/Contact links, Organization JSON-LD with sameAs, Privacy/Terms links, authority review links, publication date.

Citation Readiness (10 checks)

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.

Governance (1 check)

G1: Sitemap reachability.

Notes

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.