boston.mcp.agentstatus.dev
https://boston.mcp.agentstatus.dev/rpc
active Production-safe Score 84/100 http no auth
At a glance
| Endpoint | https://boston.mcp.agentstatus.dev/rpc |
|---|---|
| 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:43 |
Observed reliability
| 7-day uptime | 99% |
|---|---|
| 24-hour uptime | 99% |
| Handshake success | 99% |
| Latency p50 / p95 | 1407 / 2885 ms |
| Last successful check | 2026-11-17 21:46:43 |
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:43 | ✓ | ✓ | 1407 ms | 85 | active |
| 2026-11-17 21:31:42 | ✓ | ✓ | 1495 ms | 85 | active |
| 2026-11-17 21:16:41 | ✓ | ✓ | 1638 ms | 85 | active |
| 2026-11-17 21:01:40 | ✓ | ✓ | 1196 ms | 85 | active |
| 2026-11-17 20:46:39 | ✓ | ✓ | 1231 ms | 85 | active |
| 2026-11-17 20:31:38 | ✓ | ✓ | 1282 ms | 85 | active |
| 2026-11-17 20:16:37 | ✓ | ✓ | 1404 ms | 85 | active |
| 2026-11-17 20:01:36 | ✓ | ✓ | 1382 ms | 85 | active |
| 2026-11-17 19:46:35 | ✓ | ✓ | 1357 ms | 85 | active |
| 2026-11-17 19:31:33 | ✓ | ✓ | 1278 ms | 85 | active |
| 2026-11-17 19:16:32 | ✓ | ✓ | 1370 ms | 85 | active |
| 2026-11-17 19:01:31 | ✓ | ✓ | 1445 ms | 85 | active |
| 2026-11-17 18:46:29 | ✓ | ✓ | 1393 ms | 85 | active |
| 2026-11-17 18:31:28 | ✓ | ✓ | 1081 ms | 85 | active |
| 2026-11-17 18:16:27 | ✓ | ✓ | 1346 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/rpc") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/boston-mcp-agentstatus-dev-rpc # JSON