GEO Audit (AI Search Visibility) MCP server
io.github.theharrisontruong-web/geo-audittheharrisontruong-webstreamable-httpv1.0.1Scanned
Scores any URL's AI-search visibility with concrete fixes. $1.50/call via x402.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 2
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 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.
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 GEO Audit (AI Search Visibility) MCP server can do
The GEO Audit (AI Search Visibility) MCP server is published by the GitHub account theharrisontruong-web. It has 2 tools. It can create or change data (2 tools: audit_geo and audit_geo_lite), but cannot delete data. None of its tools only reads.
2 tools bring in text other people can write (audit_geo and audit_geo_lite); 2 tools can send data out of your system (audit_geo and audit_geo_lite).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 1.0.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.
2 tools
Changes things 2Claude Code: ask
audit_geoFull GEO (AI-search visibility) readiness audit of a brand/storefront URL.Reads text others writeCan send data out1 finding
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.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...tent dates), and authority (about page, credentials, canonical/HTTPS). Returns machine-read..."
Description, as the server wrote it Full GEO (AI-search visibility) readiness audit of a brand/storefront URL. Fetches the site server-side and runs 20 weighted checks across schema.org depth (Organization, Product, Review, FAQPage, aggregateRating), business identity (sameAs, NAP consistency, contact), AI-crawler policy (robots.txt treatment of GPTBot/ClaudeBot/PerplexityBot/CCBot, llms.txt), content extractability (clean text, headings, JS walls, meta description), freshness (sitemap, lastmod, content dates), and authority (about page, credentials, canonical/HTTPS). Returns machine-readable JSON: 0-100 score, A-F grade, per-check pass/partial/fail/unknown with evidence, and the top 3 prioritized fixes. No LLM is queried per call — deterministic checks only. Cost: $1.50 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this to audit a client's site for AI-search visibility, or to generate the audit behind a GEO report for a brand owner.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
audit_geo_liteFREE lite GEO readiness audit of a brand/storefront URL.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 FREE lite GEO readiness audit of a brand/storefront URL. Runs the same 20 checks as audit_geo but returns top-line results only: 0-100 score, A-F grade, check counts, and the titles of the top gaps — no per-check evidence, no detailed recommendations. Use this to triage whether a site needs the full audit_geo report, or call audit_geo directly for the complete evidence-backed audit.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: 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 write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- 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.
Looked at Nov 20, 2026, 19:11 UTC, unchanged since Oct 22, 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
- 2
- Protocol version
- 2025-06-18
- 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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://geo-al6bxcngia-ue.a.run.app/mcp: tools/list returned 2 tools to an anonymous client, including audit_geo (write), audit_geo_lite (write)
Findings
Matches of fixed checks, with the text they matched.
- Infoaudit_geo
The description mentions "credentials".
What this check looks forMatched text
description: "...tent dates), and authority (about page, credentials, canonical/HTTPS). Returns machine-read..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:audit_geoChanges thingsannotations
- Changed:audit_geo_liteChanges thingsannotations
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http geo-audit https://geo-al6bxcngia-ue.a.run.app/mcpclaude mcp add --transport http geo-audit https://geo-al6bxcngia-ue.a.run.app/mcpRun 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.
{
"permissions": {
"allow": [],
"ask": [
"mcp__geo-audit__audit_geo",
"mcp__geo-audit__audit_geo_lite"
],
"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 geo-audit. Review it before you use it.
Capability tags behind 2 rules
- mcp__geo-audit__audit_geo untrusted-input, outbound
- mcp__geo-audit__audit_geo_lite 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.theharrisontruong-web/geo-audit/verify?hash=8e3fb2f95f8b9cec3df776685a247a32e115af5632e31d593c50e7eaeedfb43b" | jq -e '.changed == false'Pinned hash 8e3fb2f95f8b, from Nov 17, 2026, 02: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.theharrisontruong-web/geo-audit/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theharrisontruong-web/geo-audit)Source: MCP Registry · repository. Synced Nov 17, 2026, 02:18 UTC.
GEO Audit (AI Search Visibility) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the GEO Audit (AI Search Visibility) MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 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 GEO Audit (AI Search Visibility) MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the GEO Audit (AI Search Visibility) 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 GEO Audit (AI Search Visibility) MCP server have?
- 2 tools: 2 write. audit_geo and audit_geo_lite.
Does the GEO Audit (AI Search Visibility) MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the GEO Audit (AI Search Visibility) MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): audit_geo and audit_geo_lite.
Has the GEO Audit (AI Search Visibility) MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.