ROOTE MCP Server

by roote Your server? Claim it

answering

ROOTE is answering right now. Last checked 13 min ago. It exposes 8 tools.

Mobility, geocoding and nearby urban services for AI agents.

Uptime history 12 days of history · worst day 99%

12 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

238 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 6 October 2026. No other catalogue keeps this.

8 Oct a tool description was rewritten nearby

6 Oct a tool appeared transit_disruptions

6 Oct a tool changed the parameters it asks for mobility_nearby

Nothing serious here today

Today is the operative word: we check ROOTE every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.roote.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.roote.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.roote.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.roote.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.roote.ai/mcp"
    }
  }
}

Available tools 8

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

transit

transit_disruptions

Current provider alert observations for an explicit geographic network sample. Never infer normal circulation from empty alerts. Unresolved line, stop, mode or non-current time returns unavailable. Preserve partial coverage and unknown source freshness.

transit_nearby

Find nearby transit stations using the canonical ROOTE transit taxonomy.

geocode

geocode

Resolve an address-like query into geographic candidates.

mobility

mobility_nearby

Find nearby shared bicycles, stations, scooters, mopeds, cars or taxis.

nearby

nearby

Find shared mobility vehicles and stations, public transport stops, and urban services near a latitude and longitude. Use this tool when the user requests multiple categories of nearby options or a general overview of what is nearby. Filter by families (mobility, transit, services), transport modes, or service types. Explicit families take precedence; otherwise modes and service types determine the requested families. Results may be partial or empty depending on source coverage. Preserve freshness information and warnings. This tool does not book vehicles, purchase tickets, or calculate journeys.

place

place_search

Search cities, points of interest and named places, optionally biased around a coordinate.

reverse

reverse_geocode

Resolve coordinates into geographic candidates.

services

services_nearby

Find supported urban services within 1500 metres of a coordinate in one aggregated request. Types include toilets, fountains, Wi-Fi, AEDs, parking and charging.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.roote.ai/mcp	streamable-http	answering	238 ms	13 min ago

Alternatives to ROOTE

same job, measured the same way

Geojp

by 55tarkun

MCP server for Japan geodata: cadastral lot numbers (chiban) and reverse geocoding, for AI agents.

23 installs/wk answering

Location and Timezone MCP Server by RoxyAPI

by roxyapi

City geocoding and timezone resolution for birth data, for AI agents, one API key.

3 tools answering

Geo

by thinair

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

answering

Tokenguard MCP

by eltociear

Real-world data for agents: air quality, geocoding, quakes, holidays, web search

9 tools answering

LatLng

by latlng-mcp

Geocoding, reverse geocoding, and places search for LatLng.

5 tools answering

Opencage Geocoding MCP

by opencagedata

MCP server for OpenCage geocoding API

23 installs/wk local only

Google Jules MCP Server

by georgeracu

Model Context Protocol server for Google's Jules AI coding agent

89 installs/wk local only

Google Maps MCP Server

by cablate

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

953 installs/wk local only

ROOTE — questions

Answers built from our own checks of this server.

What can ROOTE do?

It exposes 8 tools, read directly from the server on our last check. Among them: geocode, mobility_nearby, nearby, place_search, reverse_geocode, services_nearby and 2 more. 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 ROOTE 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 238 ms. The bar chart above shows every period we have measured.

How do I connect ROOTE?

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.

Does ROOTE need an API key?

No. ROOTE completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is ROOTE?

It answers our handshake in 238 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.