mcpbeat Sign in

Seegeo MCP Server

answering

Seegeo is answering right now. Last checked 13 min ago. 92 installs a week from npm. It exposes 3 tools.

Audit any website for AI visibility: graded report, findings with fixes, AI crawler access check.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 274 · avg 16 · +33% w/w
a month agotoday
Uptime history 55 days of history · worst day 7%
55 days agonow
11.5%
Uptime 24h
21 of 182 checks
3
Tools
read from the server
793 ms
Response time
average over 24h
92
Installs / week
npm and PyPI

Seegeo does not always answer

Over the last week it answered 13.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add seegeo --transport http https://see-geo.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://see-geo.com/mcp
~/.codex/config.toml
[mcp_servers.seegeo]
url = "https://see-geo.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "seegeo": {
      "url": "https://see-geo.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "seegeo": {
      "type": "http",
      "url": "https://see-geo.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

audit
audit_site
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.
get_audit
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.
crawler
crawler_check
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.

Endpoints

URLTransportStateLatencyChecked
https://see-geo.com/mcp streamable-http sign-in 887 ms 13 min ago
https://see-geo.com/mcp/anonymous streamable-http answering 259 ms 13 min ago

Alternatives to Seegeo

same job, measured the same way
Vibeking
by vibekingdevelopment

Website monitoring for SEO, AI visibility and ads: issues, fix tasks, rankings, reports and fixes.

answering
SyteCheck
by sytecheck

Scan a website for SEO, accessibility, performance and security issues, and read the report.

256 installs/wk local only
Evolize
by evolize

Accessibility scans with evidence, public reports, and fresh checks after fixes.

3 tools answering
Proofie Coach
by tryproofie

Read your Proofie report on AI visibility and AI agents, and fix each finding on your site.

answering
AI Visibility
by lastminutedealshq

AI-search-visibility tools: check crawler access, generate llms.txt, lint robots.txt, census data.

4 tools answering
Geolint
by iliasabk

ESLint for AI search: audits AI-crawler access, llms.txt, schema and citability.

87 installs/wk local only
Answer Checkup
by answercheckup

Free AI readiness scan for any website. Paid reports for agents are coming soon.

3 tools answering
EaseWeb accessibility
by easeweb

Accessibility guides for coding agents: fixes with working code, test steps, contrast checks. EN/JA

answering

Seegeo — questions

Answers built from our own checks of this server.

What can Seegeo do?
It exposes 3 tools, read directly from the server on our last check. Among them: audit_site, crawler_check, get_audit. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Seegeo working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 21 of 182 checks got a reply (11.5%), average response time 793 ms. The bar chart above shows every period we have measured.
Is Seegeo still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Seegeo?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Seegeo?
No API key is involved. Seegeo answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Seegeo?
It answers our handshake in 793 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Seegeo?
The npm package seegeo-mcp was installed 92 times in the last week. Week over week that is +33%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.