Google Maps MCP server
5 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Google's own remote MCP server for Maps Grounding Lite gives an agent place search, weather, routes and place lookups from Google Maps. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 5 tools
| Tool | Counted as |
|---|---|
compute_routes | Said to only read |
lookup_weather | Said to only read |
resolve_maps_urls | Said to only read |
resolve_names | Said to only read |
search_places | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
13 of the last 13 checks passed
A check passes when the server lists its tools. Checked at https://mapstools.googleapis.com/mcp.
Recent changes
27 Oct 2026, 01:50 UTC, after a check on 26 Oct 2026, 10:13 UTC
Description rewritten on compute_routes. Inputs or outputs changed on compute_routes, lookup_weather.
23 Oct 2026, 09:53 UTC, after a check on 22 Oct 2026, 09:44 UTC
Inputs or outputs changed on search_places.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Google Maps's tools change.
One email when Google Maps's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Each request is a billing event for the Google Cloud project whose API key or OAuth client the agent uses. Google's Maps Grounding Lite documentation
- Its terms allow it only with models that do not use the input for training, and ask for the Google Maps sources to be shown with what the agent writes. Google's Maps Grounding Lite documentation
How to limit it
With Google Maps's own settings, as its documentation describes them. Stackduke has not tested them.
- Restrict the API key the agent uses, as Google advises when you create or configure one. Google's Maps Grounding Lite documentation
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.