HasData Google Maps
MCP server com.hasdata/google-maps
Sourced
Google Maps places, reviews, contributor history, photos and posts as JSON. No Google Cloud.
The name and description are the publisher's own words, as the registry holds them.
- For
- Google Maps
- Version
- 1.0.7
- Registry record changed
- Listed here since
Who publishes it
Sourced. By another publisher, naming a public repository or a package. Anyone can publish one; we have not read its code.
Repository: https://github.com/HasData/google-maps-mcp
How to reach it
- Remote, Streamable HTTP:
https://mcp.hasdata.com/mcp?apis=google_mapsIts record asks for a header:x-api-key. - npm:
@hasdata/google-maps-mcpversion 1.0.7, runs over stdio - PyPI:
hasdata-google-maps-mcpversion 1.0.7, runs over stdio
{
"mcpServers": {
"google-maps": {
"type": "http",
"url": "https://mcp.hasdata.com/mcp?apis=google_maps",
"headers": {
"x-api-key": "<your value>"
}
}
}
}Built from the registry record: the address and the header names are the publisher's. Put your own value where it says so, and check the address is the one you expect before you do.
What is known about it
- Downloads
- About 71 a week for
@hasdata/google-maps-mcp(from npm on , rounded) - About 34 a week for
hasdata-google-maps-mcp(from pypistats on , rounded)
- About 71 a week for
- Vulnerabilities
- No known vulnerability in the listed npm and PyPI versions, from OSV on . That is what OSV lists, not a review of the code.
- Tools
- Not read yet. This directory does not connect to servers, so it cannot say which tools this one offers or how much room their definitions take in a context window.
Built from agent catalog version 2026-11-13.3 of , from the MCP Registry as read on . A listing here is not an endorsement: anyone can publish a server, and we have not read its code. Names, descriptions and addresses are the publisher's own. See how this directory is made, and tell us about a wrong entry through the contact page.