seegeo MCP server
com.see-geo/seegeosee-geo.comstreamable-httpv1.0.5Scanned
Audit any website for AI visibility: graded report, findings with fixes, AI crawler access check.
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- 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 seegeo MCP server can do
The seegeo MCP server is published by see-geo.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: audit_site), but cannot delete data. 2 tools only read.
2 tools bring in text other people can write (audit_site and crawler_check).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 11, 2026, version 1.0.5.
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.
3 tools
Changes things 1Claude Code: ask
audit_siteRuns SeeGeo's full audit of a domain — crawler access for 16 AI bots, technical basics, structured data, content extractability, off-site presence, entity clarity — and returns the…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Runs SeeGeo's full audit of a domain — crawler access for 16 AI bots, technical basics, structured data, content extractability, off-site presence, entity clarity — and returns the grade (A–F), category scores and the findings with fixes. Takes 20–40 seconds; waits by default. If the wait runs out the result says so — call get_audit with the id. Re-auditing the same domain within ten minutes returns the earlier result.
Annotations the server declares
- title: Audit a website for AI visibility
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 2Show 2 read-only tools
crawler_checkReads robots.txt for each AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended…) and fetches the homepage as GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot to see whet…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Reads robots.txt for each AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended…) and fetches the homepage as GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot to see whether a bot wall blocks them. A few seconds; does not count as an audit.
Annotations the server declares
- title: Which AI crawlers can read this domain?
- readOnlyHint: true
- openWorldHint: true
get_auditReturns an audit's status while it runs, or its grade, category scores and findings when done.No findings
Why it is in this group
- The name "get_audit" says "get": a word for reading.
Description, as the server wrote it Returns an audit's status while it runs, or its grade, category scores and findings when done. Set includeReport to get the full report object with evidence.
Annotations the server declares
- title: Read an audit by id
- readOnlyHint: true
- openWorldHint: false
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 or outbound.
- 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 out0
- 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, 18:46 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
- 402
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: initialize answered HTTP 402.
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 200 to 402
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://see-geo.com/.well-known/oauth-protected-resource to none
- Authorization servers: https://see-geo.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 402; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 5 more).View diff
- HTTP status of an anonymous initialize: 200 to 402
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://see-geo.com/.well-known/oauth-protected-resource to none
- Authorization servers: https://see-geo.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.0.5. Values in angle brackets are yours to fill in.
claude mcp add --transport http seegeo https://see-geo.com/mcp/anonymousclaude mcp add --transport http seegeo https://see-geo.com/mcp/anonymousRun 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": [
"mcp__seegeo__get_audit",
"mcp__seegeo__crawler_check"
],
"ask": [
"mcp__seegeo__audit_site"
],
"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 seegeo. Review it before you use it.
Capability tags behind 2 rules
- mcp__seegeo__audit_site untrusted-input
- mcp__seegeo__crawler_check untrusted-input
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/com.see-geo/seegeo/verify?hash=fafb4e69dc7f917463078c17da766ba7d1b30258bdb0067edb8945f7c316b43a" | jq -e '.changed == false'Pinned hash fafb4e69dc7f, from Nov 11, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.see-geo/seegeo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.see-geo/seegeo)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:04 UTC.
seegeo MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the seegeo MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the seegeo MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the seegeo 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 seegeo MCP server have?
- 3 tools: 1 write, 2 read. audit_site, get_audit and crawler_check.
Does the seegeo MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the seegeo MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the seegeo MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.