Skip to main content
Glama

SafeStreets

Server Details

Walkability and pedestrian safety for any US address: scores, neighborhoods, deadly roads.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Poseidon-t/safestreets-plugin
GitHub Stars
0

TDQS

Score is being calculated.

Available Tools

8 tools
compare_locations
Read-onlyIdempotent
Inspect

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 per-component gap is usually the answer: two places can reach the same composite for opposite reasons, one with errands close by and dangerous streets, the other the reverse.

A location that cannot be resolved is reported in errors and the rest are still scored. Each location counts as one call against your allowance.

ParametersJSON Schema
NameRequiredDescriptionDefault
locationsYesThe places to compare.
find_walkable_neighborhoods
Read-onlyIdempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
cityYesCity name or slug, e.g. "Chicago".
limitNoHow many to return, default 25.
get_city_walkability
Read-onlyIdempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
cityYesCity name or slug, e.g. "Houston", "fort worth", "chicago".
get_dangerous_corridors
Read-onlyIdempotent
Inspect

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 dangerous, where crashes happen, or wants evidence for a specific street. These are recorded deaths, not a model or a prediction: a road absent from the list had no recorded pedestrian fatality in the period, which is not the same as being safe.

ParametersJSON Schema
NameRequiredDescriptionDefault
latNoLatitude, to search around a point.
lonNoLongitude, to search around a point.
cityNoCity name or slug. Give this or lat/lon.
limitNoHow many to return, default 25.
radiusKmNoSearch radius in km around lat/lon, default 10.
get_walkability_score
Read-onlyIdempotent
Inspect

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.

Pass "address" when you have an address. Do not convert an address to coordinates yourself: coordinates recalled from memory land somewhere else, and this tool will score that other place and return a confident number for it. When an address is used, the reply carries resolvedFrom with the address that was actually matched, so check it before quoting the score.

Returns a JSON object: overallScore 0-100 composite displayScore the same score as 0-10, which is how SafeStreets presents it grade A to F tier plain label, e.g. "Very walkable", "Car-dependent" confidence 0-100, how much underlying data was available for this point dataSources the sources that fed this specific result components four scored sub-dimensions, each with a 0-100 score and the individual metrics behind it: dailyReach errands reachable on foot streetSafety street design and pedestrian crash risk transitReach usable transit access walkingComfort shade, heat, air quality, surface

              plus networkDesign, which carries its metrics (network
              density, intersection density, block length, dead-end ratio)
              but reports score 0 at weight 0, so it does not contribute to
              the composite. Read its metrics, not its score.

              The keys safety, environmentalComfort and densityContext are
              backward-compatibility aliases of streetSafety,
              walkingComfort and dailyReach. They duplicate those objects
              rather than adding signal.

The per-component metrics are the point: you can re-weight or rebuild the composite yourself instead of trusting one number.

Coverage and limits: United States only. Pedestrian crash inputs are county-level, so two nearby points can share crash figures. Where the underlying crash record is missing, the safety component is reported as unavailable rather than guessed, and confidence drops accordingly. This does not return driving directions, transit timetables, crime statistics, or property listings.

ParametersJSON Schema
NameRequiredDescriptionDefault
latNoLatitude in decimal degrees, WGS84. US locations only. Required unless address is given.
lonNoLongitude in decimal degrees, WGS84. Negative for the US. Required unless address is given.
addressNoA US street address, intersection or place name, e.g. "1200 W Foster Ave, Chicago". Give this OR lat/lon. Preferred when you have not been given exact coordinates: do not guess coordinates from memory, they will score a different place and the answer will look correct.
score_many
Read-onlyIdempotent
Inspect

Score up to 10 US locations in one request.

Use this for a list: properties, branches, listings, sites. For two to a handful of places where the question is which is better, compare_locations answers it directly instead.

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
locationsYesThe places to score.
search_insights
Read-onlyIdempotent
Inspect

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 question about walkability that is not about one specific location.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoHow many articles, default 5.
queryYesWhat to look for, e.g. "car free cities", "arterial roads", "kids walking to school".
search_neighborhoods
Read-onlyIdempotent
Inspect

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 ratio, commute mode shares, zero-car household share, and where available year-over-year home value growth and property tax rate — so walkability can be read alongside what living there costs.

Counties are addressed by 5-digit state+county FIPS codes because county names repeat across states (there are Delaware Counties in PA, OH, NY and IN). Example: Chester PA 42029, Delaware PA 42045, Montgomery PA 42091, New Castle DE 10003.

walkabilityIndex is the EPA National Walkability Index on its 1-20 scale, with a national percentile beside it, and sort_by "walk" ranks on it. It is not the 0-100 SafeStreets score; for that, follow up with get_walkability_score on a specific address.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return, default 25, max 100.
metroNoMetro name substring, e.g. "Philadelphia". Give any of county, metro or state.
stateNoTwo-letter state code, e.g. "PA".
countyNoComma-separated 5-digit state+county FIPS codes, e.g. "42029,42045,42091,10003". The precise way to scope a county set.
offsetNoPagination offset.
sort_byNoRanking field, default "demand".
sort_dirNoDefault "desc".
walk_minNoMinimum EPA walkability index (1-20 scale).
budget_maxNoMaximum median home value in USD; neighborhoods above it are dropped.
transit_minNoMinimum transit percentile (0-100).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 8 tool updates
    • First observedcompare_locations
    • First observedfind_walkable_neighborhoods
    • First observedget_city_walkability
    • First observedget_dangerous_corridors
    • First observedget_walkability_score
    • First observedscore_many
    • First observedsearch_insights
    • First observedsearch_neighborhoods

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.