Bridges — FHWA National Bridge Inventory: Condition, Posting & Clearance
link.morningbrief/bridgesmorningbrief.linkstreamable-httpv1.0.0Scanned
FHWA bridge inventory: 624,193 bridges, condition, posting, clearance. 8 tools, free, no key.
8 tools: 8 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Only reads 8Show 8 read-only tools
find_low_clearance_bridgesBridges in a state whose vertical clearance is at or below max_height_m.No findings
Why it is in this group
- The name "find_low_clearance_bridges" says "find": a word for reading.
Description, as the server wrote it Bridges in a state whose vertical clearance is at or below max_height_m. Default clearance is over the roadway on the bridge (NBI Item 10); set under=true for the clearance under the bridge (Item 54B), which is what matters for routes passing beneath. Sentinel 'no restriction' values are excluded.
get_bridgeGet one bridge by its FHWA structure number (Item 8).No findings
Why it is in this group
- The name "get_bridge" says "get": a word for reading.
Description, as the server wrote it Get one bridge by its FHWA structure number (Item 8). Structure numbers are unique within a state; pass state to be exact. Returns the full decoded record.
get_county_summariesPer-county bridge counts for a state, with Poor-condition and posted/closed counts per county.No findings
Why it is in this group
- The name "get_county_summaries" says "get": a word for reading.
Description, as the server wrote it Per-county bridge counts for a state, with Poor-condition and posted/closed counts per county.
get_state_summaryBridge summary for one state: total bridges, counts by condition (Good/Fair/Poor), posted and closed counts, scour-critical count, average year built, total deck area.No findings
Why it is in this group
- The name "get_state_summary" says "get": a word for reading.
Description, as the server wrote it Bridge summary for one state: total bridges, counts by condition (Good/Fair/Poor), posted and closed counts, scour-critical count, average year built, total deck area. Without a state, returns per-state totals with condition counts for all states.
get_worst_bridgesThe worst-rated bridges in a state (condition = Poor), ordered by lowest component rating then age.No findings
Why it is in this group
- The name "get_worst_bridges" says "get": a word for reading.
Description, as the server wrote it The worst-rated bridges in a state (condition = Poor), ordered by lowest component rating then age. State is required. Use for 'worst bridges in X' questions.
list_bridges_in_countyList bridges in one county (state + 3-digit FIPS county code), paged.No findings
Why it is in this group
- The name "list_bridges_in_county" says "list": a word for reading.
Description, as the server wrote it List bridges in one county (state + 3-digit FIPS county code), paged.
list_posted_or_closed_bridgesBridges in a state that are load-posted or closed to traffic (NBI Item 41 status P/R/K), worst condition first.No findings
Why it is in this group
- The name "list_posted_or_closed_bridges" says "list": a word for reading.
Description, as the server wrote it Bridges in a state that are load-posted or closed to traffic (NBI Item 41 status P/R/K), worst condition first. Relevant for routing and heavy-haul feasibility — but per FHWA, NBI data must not be used as the sole source for route clearance; inspections can be up to ~24 months old.
search_bridgesSearch US bridges in the FHWA National Bridge Inventory.No findings
Why it is in this group
- The name "search_bridges" says "search": a word for reading.
Description, as the server wrote it Search US bridges in the FHWA National Bridge Inventory. Scope with state, county (3-digit FIPS code), and/or condition (Good/Fair/Poor); optional filters: posting_status (open/posted/closed/not_yet_open), owner_code, scour_critical, year_min/year_max, min_adt, route, and q (text match on facility carried, feature crossed, location). Returns decoded records with condition rollup, posting status, clearances, and labels.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http bridges https://bridges.morningbrief.link/mcpclaude mcp add --transport http bridges https://bridges.morningbrief.link/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bridges__search_bridges",
"mcp__bridges__get_bridge",
"mcp__bridges__list_bridges_in_county",
"mcp__bridges__get_worst_bridges",
"mcp__bridges__list_posted_or_closed_bridges",
"mcp__bridges__find_low_clearance_bridges",
"mcp__bridges__get_state_summary",
"mcp__bridges__get_county_summaries"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bridges. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/link.morningbrief/bridges/verify?hash=f8460ad184f6514e48aa59c571bec872ae77068525843e2b49484f727463fbb0" | jq -e '.changed == false'Pinned hash f8460ad184f6, from Oct 25, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/link.morningbrief/bridges/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/link.morningbrief/bridges)Source: MCP Registry. Synced Oct 25, 2026, 21:18 UTC.