mcpbeat

Geo MCP Server

co.thinair/geo
answering

Geo is answering right now. Last checked 12 min ago.

Geocoding, truck routing, traffic, weather, and place search via MCP — 11 hosted tools.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
60 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add geo --transport http https://geo.thinair.co/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "geo": {
      "url": "https://geo.thinair.co/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.geo]
url = "https://geo.thinair.co/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "geo": {
      "url": "https://geo.thinair.co/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "geo": {
      "url": "https://geo.thinair.co/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://geo.thinair.co/mcp streamable-http needs key 51 ms 12 min ago

Geo — questions

Answers built from our own checks of this server.

Why is there no tool list for Geo?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Geo working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 60 ms. The bar chart above shows every period we have measured.
How do I connect Geo?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Geo need an API key?
Yes. Every time we knock, Geo answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Geo?
It answers our handshake in 60 ms on average, which is faster than 96% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.