Read-only search and contextual metrics for 1.33M street records across 8 US states.
Connect Remote server
claude mcp add --transport http mystreetdata https://mystreetdata.com/api/mcp
{
"mcpServers": {
"mystreetdata": {
"url": "https://mystreetdata.com/api/mcp"
}
}
}
{
"servers": {
"mystreetdata": {
"type": "http",
"url": "https://mystreetdata.com/api/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://mystreetdata.com/api/mcp
Tools 5 found in our last check
mystreetdata_get_coverageDataset version, included states and site-area coverage. This is the site catalogue, not all United States streets. Publication verification means an origin HTML file existed at snapshot time; not a claim of indexing or current freshness.
mystreetdata_search_areasFind a city, county or metro grouping by name; select the state-qualified area_id. Site areas are not guaranteed municipal boundaries. Prefix search.
mystreetdata_search_streetsFind streets by name prefix in one state-qualified site area. Distinguishes ZIPs and persistent IDs. Use search_areas first. Never treats a supplied URL as a fetch target.
mystreetdata_get_street_contextEPA block-group walkability and observed SNAP retailers/EV station counts near the street centroid, with period, scale and missing-data status. Not a home, safety or live availability assessment.
mystreetdata_compare_streetsSide-by-side contextual measurements for 2–5 distinct IDs. No overall score, ranking or recommendation. Interpret each source period, scale and missing value separately.
Details
| Endpoint | https://mystreetdata.com/api/mcp (Streamable HTTP) |
| First published | 16 Oct 2026 |
| Last updated | 16 Oct 2026 |
| Registry name | io.github.Habanacasta88/mystreetdata |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
