SafeStreets
Walkability and pedestrian safety for any US address: scores, neighborhoods, deadly roads.
| Endpoint | https://safestreets.streetsandcommons.com/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 8 tools · grade C (72) · pin ts_82974ffc85fd55f1f4df271593835fbc · protocol 2025-06-18 |
| First / last listed | 2026-10-28 05:42 UTC / 2026-10-28 05:42 UTC |
| Grade over time | 2026-10-28: C (72), 8 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: get_walkability_score compare_locations score_many get_city_walkability find_walkable_neighborhoods search_neighborhoods get_dangerous_corridors search_insights
get_walkability_score | Score a US location on how good and how safe it is to walk, from a street address or from latitude/longitude.
Call this when someone asks whether a place is walkable, how safe it is to walk, whether they could live somewhere without a car, how a neighborhood compares to another on foot, or when evaluating a specific address or property for walkability or pedestrian risk.
The server geocodes an a params: address, lat, lon |
compare_locations | Score 2 to 10 US locations and say how they differ.
Use this for "which of these is the most walkable", choosing between addresses, or any question that puts places side by side. Give addresses or coordinates, and a label for each if you want the results matched back to your own names.
Returns every location ranked, the best and worst, the spread between them, and the gap on each component. The params: locations* |
score_many | Score up to 10 US locations in one request.
Use this for a list: properties, branches, listings, sites.
Each location counts as one call against your allowance, so a list of ten costs ten. A location that cannot be resolved is reported in errors rather than failing the request. params: locations* |
get_city_walkability | Walkability score for a whole US city, precomputed. Instant, no analysis.
Use this for "how walkable is Houston" rather than scoring a point inside it. Returns the 0-100 composite, the same score as 0-10, the tier, and the four components. Covers 203 cities; a city not in the set returns null, which means not covered rather than not walkable. params: city* |
find_walkable_neighborhoods | Neighborhoods inside a US city, ranked most walkable first, precomputed.
Use this for "which part of Chicago should I live in without a car". Returns up to 25 neighborhoods, each with its 0-10 score, tier and components. Covers 749 neighborhoods across the cities analysed so far, so an empty list means that city has not been broken down yet, not that it has no walkable areas. params: city*, limit |
search_neighborhoods | Ranked neighborhood search across every US neighborhood (202,000+), for "where should I move" questions.
Use this when someone is relocating and has not picked a town yet: filter to a county set, a metro, a state, a home-price ceiling or a walkability floor, then rank by walkability, transit, zero-car share, demand or home value. Each row carries median home value, median income, price-to-income params: county, metro, state, budget_max, walk_min, transit_min, sort_by, sort_dir, limit, offset |
get_dangerous_corridors | Road corridors where pedestrians were actually killed, from federal crash records.
Source: NHTSA FARS 2022-2024 (PER_TYP=5, INJ_SEV in 4,6). Each corridor carries the road name, the city, the total pedestrian deaths and a per-year breakdown, so a claim can be checked rather than taken on trust.
Give either a city, or a lat/lon with an optional radius. Use this when someone asks which roads are d params: city, lat, lon, radiusKm, limit |
search_insights | Search SafeStreets' published research on walkability, street design and pedestrian safety.
Returns the article title, summary, URL and its published questions and answers, so a finding can be quoted and linked rather than paraphrased from memory. 32 articles, each built on named public sources.
Use this when someone asks what the evidence says, wants a figure they can cite, or asks a general qu params: query*, limit |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.