Geo MCP Server

by thinair Your server? Claim it

answering

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

Geocoding, routing, isochrones, traffic, weather, and place search for AI agents. 19 MCP tools.

Uptime history 47 days of history · worst day 92%

47 days agonow

96.7%

Uptime 24h

88 of 91 checks

—

Tools

hidden behind auth

68 ms

Response time

average over 24h

authentication required

Access

streamable-http

Geo does not always answer

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

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.

Claude Code Claude Desktop Codex Cursor VS Code

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 it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://geo.thinair.co/mcp	streamable-http	needs auth	68 ms	12 min ago

Alternatives to Geo

same job, measured the same way

Google Maps MCP Server

by cablate

18 Google Maps tools for AI agents — geocode, search, directions, weather, and more.

3 246 installs/wk local only

MapMap

by mapmap

Maps built for agents: routing incl. truck/ADR, geocoding, matrices, isochrones — 34 tools.

43 tools answering

Here

by pipeworx-io

HERE MCP — premium geocoding, places, and TRAFFIC-AWARE routing from HERE

35 tools answering

LatLng

by latlng-mcp

Geocoding, reverse geocoding, and places search for LatLng.

5 tools answering

Inavi MCP

by inavi-systems

MCP Server for iNavi Maps API - Geocoding, POI Search, Route Planning for Claude AI

71 installs/wk local only

Metalift

by metalift-ai

Metalift MCP for AI agents: web search (2 credits), scrape, crawl, and map tools

62 installs/wk local only

Weather & Geo Intel MCP

by datakoot

US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys.

6 tools answering

Mapsi MCP

by algolayertechnologies

Geocoding, routing, isochrone, H3, elevation and 13 more geospatial tools via OpenStreetMap.

21 installs/wk local only

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: 96.7% 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 88 of 91 checks got a reply (96.7%), average response time 68 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 credentials: 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 68 ms on average, which is faster than 86% 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.