maine-parks.mcp.agentstatus.dev
https://maine-parks.mcp.agentstatus.dev/.well-known/mcp
active Production-safe Score 94/100 http no auth
At a glance
| Endpoint | https://maine-parks.mcp.agentstatus.dev/.well-known/mcp |
|---|---|
| Source | https://maine-parks.mcp.agentstatus.dev/ |
| Transport | http |
| Tools | 4 |
| Auth | none |
| First seen | 2026-11-11 12:58:38 |
| Last checked | 2026-11-17 21:54:55 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 420 / 616 ms |
| Last successful check | 2026-11-17 21:54:55 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (4)
search_parks— Search Maine State Parks by park name or city. Hours and fees are included only when the state publishes them.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:54:55 | ✓ | ✓ | 311 ms | 91 | active |
| 2026-11-17 21:39:42 | ✓ | ✓ | 478 ms | 91 | active |
| 2026-11-17 21:24:27 | ✓ | ✓ | 455 ms | 91 | active |
| 2026-11-17 21:09:16 | ✓ | ✓ | 416 ms | 91 | active |
| 2026-11-17 20:54:07 | ✓ | ✓ | 256 ms | 94 | active |
| 2026-11-17 20:39:05 | ✓ | ✓ | 494 ms | 91 | active |
| 2026-11-17 20:24:03 | ✓ | ✓ | 263 ms | 94 | active |
| 2026-11-17 20:08:52 | ✓ | ✓ | 405 ms | 91 | active |
| 2026-11-17 19:53:04 | ✓ | ✓ | 254 ms | 94 | active |
| 2026-11-17 19:38:01 | ✓ | ✓ | 229 ms | 94 | active |
| 2026-11-17 19:22:44 | ✓ | ✓ | 591 ms | 90 | active |
| 2026-11-17 19:07:30 | ✓ | ✓ | 240 ms | 94 | active |
| 2026-11-17 18:52:11 | ✓ | ✓ | 303 ms | 91 | active |
| 2026-11-17 18:37:06 | ✓ | ✓ | 434 ms | 91 | active |
| 2026-11-17 18:22:02 | ✓ | ✓ | 409 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://maine-parks.mcp.agentstatus.dev/.well-known/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/maine-parks-mcp-agentstatus-dev-well-known-mcp # JSON