ROOTE
REMOTE · MCP.ROOTE.AI
Mobility, geocoding and nearby urban services for AI agents.
Available components
Last scanned (10 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 689 tokens (~86/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +2
- Tool “nearby” rewrote its description, which is the text the model reads security
- Schema quality: 71 → 86 ▼ functional
- First check of Tool coverage: 100 functional
- Tool “nearby” changed its title: Find everything nearby → Find nearby mobility, transit and urban services cosmetic
- 6 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 4 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://mcp.roote.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.roote.ai | CN=YR2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | RSA 2048 | SHA256-RSA | 5c747fbd92886fef1c06f6f5f03d522f245 |
| SANs: mcp.roote.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.roote.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| roote.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; style-src 'self'; img-src 'self'; script-src 'self' 'sha256-feLVRJAY9OBYXBr63Cs2oxuP1bgxTv8g5t5RsJivB5o='; frame-ancestors 'none'; base-uri 'none'; form-action 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.roote.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.roote.ai/mcp | HTTPS enforced | 301 | https://mcp.roote.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
geocode Geocode an address ~38
Resolve an address-like query into geographic candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| language | string | – | – |
| q | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contract_version | string | yes | – |
| meta | object | yes | – |
| results | array | yes | – |
No examples provided.
mobility_nearby Find nearby shared mobility ~89
Find nearby shared bicycles, stations, scooters, mopeds, cars or taxis.
| Name | Type | Req | Description |
|---|---|---|---|
| debug | boolean | – | – |
| format | string | – | – |
| include | array | – | – |
| lat | number | yes | – |
| limit | integer | – | – |
| lon | number | yes | – |
| modes | array | – | – |
| offset | integer | – | – |
| radius | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | – |
| attributions | array | yes | – |
| contract_version | string | yes | – |
| coverage | object | yes | – |
| meta | object | yes | – |
| query | object | yes | – |
| stations | array | yes | – |
| status | string | yes | – |
| vehicles | array | yes | – |
| warnings | array | yes | – |
No examples provided.
nearby Find nearby mobility, transit and urban services ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| debug | boolean | – | – |
| families | array | – | – |
| family_limit | integer | – | – |
| lat | number | yes | – |
| limit | integer | – | – |
| lon | number | yes | – |
| modes | array | – | – |
| radius | number | – | – |
| types | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| completed_families | array | yes | – |
| contract_version | string | yes | – |
| coverage | – | yes | – |
| failed_families | array | yes | – |
| families | object | yes | – |
| query | object | yes | – |
| requested_families | array | yes | – |
| returned_count | integer | yes | – |
| status | string | yes | – |
| warnings | array | yes | – |
No examples provided.
place_search Search places ~52
Search cities, points of interest and named places, optionally biased around a coordinate.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| lat | number | – | – |
| lon | number | – | – |
| q | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contract_version | string | yes | – |
| meta | object | yes | – |
| results | array | yes | – |
No examples provided.
reverse_geocode Reverse geocode coordinates ~36
Resolve coordinates into geographic candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| lat | number | yes | – |
| lon | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contract_version | string | yes | – |
| meta | object | yes | – |
| results | array | yes | – |
No examples provided.
services_nearby Find nearby urban services ~92
Find supported urban services within 1500 metres of a coordinate in one aggregated request. Types include toilets, fountains, Wi-Fi, AEDs, parking and charging.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| debug | boolean | – | – |
| lat | number | yes | – |
| limit | integer | – | – |
| lon | number | yes | – |
| radius | number | – | – |
| types | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | yes | – |
| contract_version | string | yes | – |
| coverage | object | yes | – |
| meta | object | yes | – |
| query | object | yes | – |
| services | array | yes | – |
| status | string | yes | – |
| warnings | array | yes | – |
No examples provided.
transit_disruptions Read current transit disruption observations ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| at | integer | – | – |
| lat | number | yes | – |
| limit | integer | – | – |
| line_ref | string | – | – |
| lon | number | yes | – |
| network_id | string | – | – |
| stop_ref | string | – | – |
| transit_mode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| alerts | array | yes | – |
| contract_version | string | yes | – |
| coverage | object | yes | – |
| evaluated_at | string | yes | – |
| fetched_at | – | – | – |
| freshness | object | – | – |
| normality_confirmed | boolean | yes | – |
| provider | string | yes | – |
| provider_calls | – | yes | – |
| provider_invocations | – | yes | – |
| query | object | yes | – |
| reason | string | – | – |
| scope | string | yes | – |
| source_updated_at | – | yes | – |
| status | string | yes | – |
| total | – | – | – |
| truncated | boolean | – | – |
| warnings | array | – | – |
No examples provided.
transit_nearby Find nearby public transit ~64
Find nearby transit stations using the canonical ROOTE transit taxonomy.
| Name | Type | Req | Description |
|---|---|---|---|
| debug | boolean | – | – |
| lat | number | yes | – |
| limit | integer | – | – |
| lon | number | yes | – |
| modes | array | – | – |
| radius | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | yes | – |
| contract_version | string | yes | – |
| coverage | object | yes | – |
| lines | array | yes | – |
| meta | object | yes | – |
| operators | array | yes | – |
| query | object | yes | – |
| stations | array | yes | – |
| status | string | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the ROOTE MCP server?
ROOTE is a hosted endpoint at https://mcp.roote.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.roote.ai
claude mcp add --transport http ai-roote-mcp 'https://mcp.roote.ai/mcp'
What is the ROOTE MCP server?
ROOTE is an MCP server listed in the public MCP registry as ai.roote/mcp. Mobility, geocoding and nearby urban services for AI agents. This page covers its hosted endpoint (https://mcp.roote.ai/mcp).
Is the ROOTE MCP server safe to use?
ROOTE scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ROOTE MCP server expose?
ROOTE exposes 8 tools: geocode, place_search, reverse_geocode, nearby, mobility_nearby, and 3 more. Their descriptions and schemas cost roughly 658 tokens of context every time the server is loaded.
Does the ROOTE MCP server require authentication?
No. We connected to ROOTE without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ROOTE MCP server still maintained?
ROOTE is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.