boston.mcp.agentstatus.dev
https://boston.mcp.agentstatus.dev/mcp.json
active Production-safe Score 84/100 http no auth
At a glance
| Endpoint | https://boston.mcp.agentstatus.dev/mcp.json |
|---|---|
| Source | https://boston.mcp.agentstatus.dev/ |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-11-11 12:58:38 |
| Last checked | 2026-11-17 21:57:08 |
Observed reliability
| 7-day uptime | 99% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 99% |
| Latency p50 / p95 | 1511 / 2273 ms |
| Last successful check | 2026-11-17 21:57:08 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
search_stops— Search Boston transit stops and stations by name or stop id.search_routes— Search Boston transit routes by short name, long name, or route id.upcoming_departures— Next departures from one Boston transit stop. Uses the live arrivals list when this feed has one, and reuses that list for about a minute.start_work— Start work that finishes later. This call returns immediately with a job id. Subscribers hear work.finished when finish_work runs.finish_work— Mark a started job finished or failed and post work.finished to subscribers. Call this when the work is actually done.send_feedback— Tell the developer this result was wrong or confusing. Call this after a tool, not instead of the tool.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:57:08 | ✓ | ✓ | 1220 ms | 85 | active |
| 2026-11-17 21:26:31 | ✓ | ✓ | 1606 ms | 85 | active |
| 2026-11-17 20:42:20 | ✓ | ✓ | 1103 ms | 85 | active |
| 2026-11-17 19:57:32 | ✓ | ✓ | 1648 ms | 85 | active |
| 2026-11-17 19:28:24 | ✓ | ✓ | 1145 ms | 85 | active |
| 2026-11-17 18:56:39 | ✓ | ✓ | 1387 ms | 85 | active |
| 2026-11-17 18:26:52 | ✓ | ✓ | 1196 ms | 85 | active |
| 2026-11-17 17:42:29 | ✓ | ✓ | 1258 ms | 85 | active |
| 2026-11-17 16:57:22 | ✓ | ✓ | 2171 ms | 85 | active |
| 2026-11-17 16:27:07 | ✓ | ✓ | 1287 ms | 85 | active |
| 2026-11-17 15:40:48 | ✓ | ✓ | 1210 ms | 85 | active |
| 2026-11-17 14:55:21 | ✓ | ✓ | 1349 ms | 85 | active |
| 2026-11-17 14:25:11 | ✓ | ✓ | 1323 ms | 85 | active |
| 2026-11-17 13:40:06 | ✓ | ✓ | 1238 ms | 85 | active |
| 2026-11-17 12:56:00 | ✓ | ✓ | 1203 ms | 85 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://boston.mcp.agentstatus.dev/mcp.json") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/boston-mcp-agentstatus-dev-mcp-json # JSON