Maps & transport · Remote MCP server
Geo
Geocoding, routing, isochrones, traffic, weather, and place search for AI agents. 19 MCP tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
co.thinair/geo- Version
- 2.2.2
- Status
- Active
- Category
- maps & transport
- Transport
- Streamable HTTP
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- co.thinair · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain thinair.co · how
- Listed under
- Weather MCP servers, Maps MCP servers
- Website
- geo.thinair.co
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://geo.thinair.co/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Geo
Geo is a remote MCP server: there is nothing to install. Its endpoint is https://geo.thinair.co/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, geo.thinair.co, was checked for the files that tell AI systems about a site.
More from co.thinair
| Server | Runs |
|---|---|
| DataPostgreSQL, MySQL, and SQL Server in one session. 26 read-only MCP tools for AI agents. | Remote · HTTPLive check: sign-in required |
More maps & transport servers
| Server | Runs |
|---|---|
| FreightUtils MCP ServerNeutral freight reference + validation layer for AI agents: ADR, HS, UN/LOCODE, freight math. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| fromtocargo.comEuropean road freight and moving prices: quotes, dated price index, glossary, order submission. | Remote · HTTPLive check: ✓ handshake |
| Fuel Economy MCPVehicle fuel economy ratings from the EPA. No key required. | Local · stdio |
| Futuristic Risk IntelligenceGeopolitical conflict risk, political events, and maritime traffic data for AI agents. | Local · stdio |
| GeoapifyGeocode, reverse-geocode, autocomplete, route and search places. | Remote · HTTPLive check: ✓ handshake |
| GeocodingForward and reverse geocoding, place search, and distance via OpenStreetMap Nominatim. No key. | Local · stdio |
| GeoEDGE MCPGeospatial analysis: vector and raster GIS operations, cartographic maps, spatial data access. | Local · stdio |
| GeojpMCP server for Japan geodata: cadastral lot numbers (chiban) and reverse geocoding, for AI agents. | Remote & Local · HTTP, stdioLive check: sign-in required |