boston.mcp.agentstatus.dev
https://boston.mcp.agentstatus.dev/tools
active Production-safe Score 83/100 http no auth
At a glance
| Endpoint | https://boston.mcp.agentstatus.dev/tools |
|---|---|
| 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:46:32 |
Observed reliability
| 7-day uptime | 99% |
|---|---|
| 24-hour uptime | 99% |
| Handshake success | 99% |
| Latency p50 / p95 | 1553 / 2940 ms |
| Last successful check | 2026-11-17 21:46:32 |
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:46:32 | ✓ | ✓ | 1263 ms | 85 | active |
| 2026-11-17 21:31:31 | ✓ | ✓ | 1352 ms | 85 | active |
| 2026-11-17 21:16:30 | ✓ | ✓ | 1205 ms | 85 | active |
| 2026-11-17 21:01:29 | ✓ | ✓ | 1401 ms | 85 | active |
| 2026-11-17 20:46:27 | ✓ | ✓ | 1562 ms | 85 | active |
| 2026-11-17 20:31:24 | ✓ | ✓ | 1372 ms | 85 | active |
| 2026-11-17 20:16:22 | ✓ | ✓ | 1621 ms | 85 | active |
| 2026-11-17 20:01:20 | ✓ | ✓ | 1611 ms | 85 | active |
| 2026-11-17 19:46:18 | ✓ | ✓ | 1524 ms | 85 | active |
| 2026-11-17 19:31:17 | ✓ | ✓ | 1762 ms | 85 | active |
| 2026-11-17 19:16:15 | ✓ | ✓ | 1630 ms | 85 | active |
| 2026-11-17 19:01:13 | ✓ | ✓ | 1626 ms | 85 | active |
| 2026-11-17 18:46:12 | ✓ | ✓ | 1960 ms | 85 | active |
| 2026-11-17 18:31:10 | ✓ | ✓ | 2126 ms | 85 | active |
| 2026-11-17 18:16:08 | ✓ | ✓ | 1284 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/tools") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/boston-mcp-agentstatus-dev-tools # JSON