rail-crossing-atlas
https://railcrossingatlas.tansolutions.org
Registry code: 01d52d3757da538b
Look up US railroad crossings from the FRA Crossing Inventory: crossings near a point, one crossing by its ID, and county or state totals. Each answer links to its page on railcrossingatlas.tansolutions.org.
- endpoint
- https://railcrossingatlas.tansolutions.org/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is rail-crossing-atlas live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is rail-crossing-atlas free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does rail-crossing-atlas have?
- 4 tools: county_summary, find_crossings_near, get_crossing, state_summary.
- Is rail-crossing-atlas safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
county_summary unknown 1h ago
Get the totals for one US county. Returns the number of public railroad crossings, how many have gates, lights or signs, the most trains a day and the other facts shown on the county page, with a link to that page.
{ "type": "object", "required": [ "state", "county" ], "properties": { "state": { "type": "string", "description": "A US state name or its two-letter code, like Illinois or IL." }, "county": { "type": "string", "description": "The county name, like Cook." } }, "additionalProperties": false }arguments 18 linesfind_crossings_near unknown 1h ago
Find US railroad crossings near a point. Give a latitude and longitude, and a distance of up to 2 miles (1 mile if left out). Returns up to the 25 closest crossings, each with its crossing ID, road, city, equipment, daily trains, distance in miles and a link to its page.
{ "type": "object", "required": [ "latitude", "longitude" ], "properties": { "latitude": { "type": "number", "maximum": 85, "minimum": -85, "description": "Latitude in decimal degrees, like 41.8781." }, "longitude": { "type": "number", "maximum": 180, "minimum": -180, "description": "Longitude in decimal degrees, like -87.6298." }, "radius_miles": { "type": "number", "maximum": 2, "description": "How far to look, in miles. Up to 2; 1 if left out.", "exclusiveMinimum": 0 } }, "additionalProperties": false }arguments 28 linesget_crossing unknown 1h ago
Look up one US railroad crossing by its 7-character FRA crossing ID. Returns its road, place, equipment, daily trains, road traffic, a link to its page, a link to this version of the record and a link to the FRA record.
{ "type": "object", "required": [ "crossing_id" ], "properties": { "crossing_id": { "type": "string", "description": "The 7-character FRA crossing ID: six digits and a letter, like 123456A." } }, "additionalProperties": false }arguments 13 linesstate_summary unknown never probed
Get the totals for one US state: the number of public railroad crossings and how many are equipped with gates, with flashing lights only, with signs only, or with other or unreported equipment. Returns a link to the state page.
{ "type": "object", "required": [ "state" ], "properties": { "state": { "type": "string", "description": "A US state name or its two-letter code, like Illinois or IL." } }, "additionalProperties": false }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id01d52d3757da538b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/01d52d3757da538b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/01d52d3757da538b?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.