Skip to content

ApexSEO GEO & AI-Crawler Audit MCP server

io.github.kwizzlesurp10-ctrl/apexseo-geo-mcpkwizzlesurp10-ctrlstreamable-httpv0.1.1Scanned

Keyless Base USDC x402 MCP for live AI-crawler, GEO/AEO & JSON-LD citation audits.

6 tools: 6 change things.

Tools: 0 delete, 0 irreversible, 6 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 4
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ApexSEO GEO & AI-Crawler Audit MCP server can do

The ApexSEO GEO & AI-Crawler Audit MCP server is published by the GitHub account kwizzlesurp10-ctrl. It has 6 tools. It can create or change data (6 tools: geo_health, geo_pricing, ai_crawler_audit, geo_page_audit and 2 more), but cannot delete data. None of its tools only reads.

4 tools bring in text other people can write (ai_crawler_audit, geo_page_audit, schema_citation_check and 1 more); 4 tools can send data out of your system (ai_crawler_audit, geo_page_audit, schema_citation_check and 1 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 6Claude Code: ask
  • ai_crawler_auditLive-fetches a domain's /robots.txt, /llms.txt, /llms-full.txt, /sitemap.xml, and /.well-known/{x402,mcp,agent-card.json} files, returning a per-bot permission matrix (GPTBot, OAI-…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Live-fetches a domain's /robots.txt, /llms.txt, /llms-full.txt, /sitemap.xml, and /.well-known/{x402,mcp,agent-card.json} files, returning a per-bot permission matrix (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, Bingbot, Applebot-Extended, CCBot), AI-crawler readiness score (0-100), and ICE fixes. Use geo_page_audit for HTML/TTFB signals or schema_citation_check for JSON-LD validation.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • geo_competitor_compareRuns parallel live page GEO audits and AI-crawler (robots.txt / llms.txt) checks across your targetUrl and 1-3 competitorUrls, computing exact win/loss deltas across geoScore, AI-c…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "geo_competitor_compare" says "compare": a word for reading.
    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "run" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.targetUrl), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.targetUrl): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "geo_competitor_compare" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "geo_competitor_compare" says "compare": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Runs parallel live page GEO audits and AI-crawler (robots.txt / llms.txt) checks across your targetUrl and 1-3 competitorUrls, computing exact win/loss deltas across geoScore, AI-crawler readiness, TTFB speed, schema depth, question headings, and llms.txt coverage, plus a ranked ICE counter-strategy roadmap.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • geo_healthFree diagnostic check returning live service uptime, supported AI crawler matrix, x402 payment configuration (Base USDC payTo and CDP facilitator readiness), and SSRF protection st…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free diagnostic check returning live service uptime, supported AI crawler matrix, x402 payment configuration (Base USDC payTo and CDP facilitator readiness), and SSRF protection status. Call this or geo_pricing first before running paid live-site audits.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • geo_page_auditPerforms a comprehensive live technical + Generative Engine Optimization (GEO/AEO) audit of any URL: measures TTFB, redirect chain, X-Robots-Tag, meta robots, canonical/hreflang, c…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Performs a comprehensive live technical + Generative Engine Optimization (GEO/AEO) audit of any URL: measures TTFB, redirect chain, X-Robots-Tag, meta robots, canonical/hreflang, compression & security headers, title/meta/OpenGraph, H1-H3 question-heading density, structured lists/tables, empty CSR-shell detection, image alt coverage, E-E-A-T trust signals, composite geoScore (0-100), and ApexSEO Elite ICE action plan. Pair with ai_crawler_audit for site-wide robots.txt/llms.txt or geo_competitor_compare for rival benchmarking.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • geo_pricingFree pricing manifest listing all ApexSEO GEO audit endpoints, Base Mainnet (eip155:8453) USDC prices ($0.01-$0.05), endpoint paths, and MCP Streamable HTTP connection details.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free pricing manifest listing all ApexSEO GEO audit endpoints, Base Mainnet (eip155:8453) USDC prices ($0.01-$0.05), endpoint paths, and MCP Streamable HTTP connection details. Ideal sibling to geo_health before dispatching paid calls.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • schema_citation_checkExtracts and validates all embedded application/ld+json blocks (including @graph trees) on a live page, flags syntax errors and missing AI-citation properties for Organization, Web…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Extracts and validates all embedded application/ld+json blocks (including @graph trees) on a live page, flags syntax errors and missing AI-citation properties for Organization, WebSite, SoftwareApplication, Product, Article, FAQPage, and WebPage entities, scores schema completeness (0-100), and outputs a ready-to-paste JSON-LD @graph patch customized from detected metadata.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out4
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:20 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://apexseo-geo-mcp.vercel.app/mcp: tools/list returned 6 tools to an anonymous client, including geo_health (write), geo_pricing (write), ai_crawler_audit (write), geo_page_audit (write), schema_citation_check (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "geo_competitor_compare" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "geo_competitor_compare" says "compare": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http apexseo-geo https://apexseo-geo-mcp.vercel.app/mcp
claude mcp add --transport http apexseo-geo https://apexseo-geo-mcp.vercel.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__apexseo-geo__geo_health",
      "mcp__apexseo-geo__geo_pricing",
      "mcp__apexseo-geo__ai_crawler_audit",
      "mcp__apexseo-geo__geo_page_audit",
      "mcp__apexseo-geo__schema_citation_check",
      "mcp__apexseo-geo__geo_competitor_compare"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as apexseo-geo. Review it before you use it.

Capability tags behind 4 rules
  • mcp__apexseo-geo__ai_crawler_audit untrusted-input, outbound
  • mcp__apexseo-geo__geo_page_audit untrusted-input, outbound
  • mcp__apexseo-geo__schema_citation_check untrusted-input, outbound
  • mcp__apexseo-geo__geo_competitor_compare untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.kwizzlesurp10-ctrl/apexseo-geo-mcp/verify?hash=b7f3dfd81eeff46baac8bd28772ea22c35c42856cc54138701036c0e51119c73" | jq -e '.changed == false'

Pinned hash b7f3dfd81eef, from Nov 20, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.kwizzlesurp10-ctrl/apexseo-geo-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.kwizzlesurp10-ctrl/apexseo-geo-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.kwizzlesurp10-ctrl/apexseo-geo-mcp.svg)](https://radar.anlyon.com/servers/io.github.kwizzlesurp10-ctrl/apexseo-geo-mcp)

Source: MCP Registry · repository. Synced Nov 20, 2026, 12:17 UTC.

ApexSEO GEO & AI-Crawler Audit MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ApexSEO GEO & AI-Crawler Audit MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ApexSEO GEO & AI-Crawler Audit MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ApexSEO GEO & AI-Crawler Audit MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ApexSEO GEO & AI-Crawler Audit MCP server have?

6 tools: 6 write. geo_health, geo_pricing, ai_crawler_audit, geo_page_audit, schema_citation_check and geo_competitor_compare.

Does the ApexSEO GEO & AI-Crawler Audit MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ApexSEO GEO & AI-Crawler Audit MCP server send data to outside services?

4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): ai_crawler_audit, geo_page_audit, schema_citation_check and geo_competitor_compare.

Has the ApexSEO GEO & AI-Crawler Audit MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.