Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
supercarto is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Token-budgeted map context: OSM graph, terrain, weather, air, transit
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user supercarto-mcp '--' npx -y supercarto
# 2 — ask your agent for something these tools do
# get_maplet, localize, route and 9 more
supercarto costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts supercarto as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user supercarto-mcp '--' npx -y supercartoReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take SUPERCARTO_OWM_KEY (OpenWeatherMap key; enables the traffic tool), SUPERCARTO_GTFS_URL (GTFS static feed zip URL; enables the transit tools), SUPERCARTO_GTFS_RT (GTFS realtime TripUpdates URL; joins predictions into schedule rows) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Fetch real map data around a coordinate and return a token-budgeted
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | number | yes | Latitude in WGS84 degrees. |
| lon | number | yes | Longitude in WGS84 degrees. |
| radiusM | number | no | Radius in metres. Default 300. Larger costs more tokens. |
| layers | array | no | Semantic layers to include, e.g. ["road", "poi"]. Default all. |
| budget | number | no | Token budget for the response. Default 1024, hard cap …. |
| returnScr | boolean | no | Also return the wire SCR in a second content block. Keep it: it is the session state a later localize() call moves within, and the agent stores it in its own RAM rather than the chat context. |
Move within a map session you already hold. Pass the session SCR
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scr | string | yes | Session state: the SCR string from the previous get_maplet or localize. |
| lat | number | yes | Latitude in WGS84 degrees. |
| lon | number | yes | Longitude in WGS84 degrees. |
| radiusM | number | no | Radius in metres. Default 300. |
| layers | array | no | Semantic layers to include, e.g. ["road", "poi"]. Default all. |
| budget | number | no | Token budget for the re-fit view. Default 1024, hard cap …. |
Feasibility between two coordinates: straight-line distance, the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fromLat | number | yes | — |
| fromLon | number | yes | — |
| toLat | number | yes | — |
| toLon | number | yes | — |
| mode | string | no | — |
Find named places (cafes, stations, shops) near a coordinate. Cheaper
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | number | yes | — |
| lon | number | yes | — |
| radiusM | number | no | — |
| query | string | no | Substring match on place name or type. |
| limit | number | no | — |
Fetch the exact geometry of features by id, as WKT. Use only when
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scr | string | yes | SCR document from a previous get_maplet. |
| ids | array | yes | — |
Sample ground elevation around a coordinate, in metres. Returns the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | number | yes | — |
| lon | number | yes | — |
| radiusM | number | no | — |
| samples | number | no | — |
Sun position, sunrise, sunset, and twilight state for a coordinate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | number | yes | — |
| lon | number | yes | — |
| at | string | no | ISO 8601 instant. Defaults to now. Times are UTC. |
Current weather conditions and a short forecast at a coordinate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | number | yes | — |
| lon | number | yes | — |
| hours | number | no | Forecast horizon in hours. Default 12, max 48. |
Air quality at a coordinate: European and US AQI bands, particulate
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | number | yes | — |
| lon | number | yes | — |
| hours | number | no | Forecast horizon in hours. Default 12, max 48. |
Live traffic congestion and a realistic arrival time between two
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fromLat | number | yes | — |
| fromLon | number | yes | — |
| toLat | number | yes | — |
| toLon | number | yes | — |
| mode | string | no | — |
Transit stops, lines, and service times around a coordinate, read from
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | number | yes | — |
| lon | number | yes | — |
| radiusM | number | no | — |
| budget | number | no | Token budget for the response. Default 1024, hard cap …. |
| now | string | no | ISO 8601 instant to judge the service day against. Defaults to now. Interpreted in the feed timezone. |
A certified ride plan between two coordinates from the operator’s configured GTFS feed: walk to a stop, ride one line that serves both catchments, then walk to the destination. Plans are certified against the service day in the feed timezone; walk legs are straight-line with a compass word, not…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fromLat | number | yes | — |
| fromLon | number | yes | — |
| toLat | number | yes | — |
| toLon | number | yes | — |
| maxWalkM | number | no | Catchment radius around each end for finding stops. Default 500. |
| budget | number | no | Token budget for the response. Default 1024, hard cap …. |
| now | string | no | ISO 8601 instant to judge the service day against. Defaults to now. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install supercarto or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (12 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
1 of the 12 recovered tools are registered only when carto.hasElevation holds (dist/server/mcp.js:286) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 6.
1 of the 12 recovered tools are registered only when carto.hasWeather holds (dist/server/mcp.js:288) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 6.
1 of the 12 recovered tools are registered only when carto.hasAir holds (dist/server/mcp.js:290) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 6.
1 of the 12 recovered tools are registered only when carto.hasTraffic holds (dist/server/mcp.js:292) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 6.
2 of the 12 recovered tools are registered only when carto.hasTransit holds (dist/server/mcp.js:297) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 6.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
6 tools are registered unconditionally · (1) 1 more only when carto.hasElevation holds (dist/server/mcp.js:286) · (2) 1 more only when carto.hasWeather holds (dist/server/mcp.js:288) · (3) 1 more only when carto.hasAir holds (dist/server/mcp.js:290) · (4) 1 more only when carto.hasTraffic holds (dist/server/mcp.js:292) · (5) 2 more only when carto.hasTransit holds (dist/server/mcp.js:297) — typically when a key or option is configured. All 12 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_maplet | untrusted-input | untrusted-input: keyword "fetch" |
| localize | no tags | |
| route | no tags | |
| search_places | no tags | |
| expand_feature | untrusted-input | untrusted-input: keyword "fetch" |
| get_terrain conditional (1) | no tags | |
| get_daylight | no tags | |
| get_weather conditional (2) | no tags | |
| get_air conditional (3) | no tags | |
| get_traffic conditional (4) | no tags | |
| get_transit conditional (5) | no tags | |
| get_transit_route conditional (5) | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.7.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish supercarto can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.