Arclan / Servers

maine-parks.mcp.agentstatus.dev

https://maine-parks.mcp.agentstatus.dev/mcp.json

active Production-safe Score 94/100 http no auth

At a glance

Endpointhttps://maine-parks.mcp.agentstatus.dev/mcp.json
Sourcehttps://maine-parks.mcp.agentstatus.dev/
Transporthttp
Tools4
Authnone
First seen2026-11-11 12:58:38
Last checked2026-11-17 21:54:58

Observed reliability

7-day uptime100%
24-hour uptime100%
Handshake success100%
Latency p50 / p95395 / 539 ms
Last successful check2026-11-17 21:54:58

Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →

Tools (4)

Validation history

CheckedReachableHandshakeLatencyScoreState
2026-11-17 21:54:58✓✓503 ms90active
2026-11-17 21:39:45✓✓532 ms90active
2026-11-17 21:24:31✓✓297 ms94active
2026-11-17 21:09:22✓✓452 ms90active
2026-11-17 20:54:11✓✓258 ms94active
2026-11-17 20:39:09✓✓287 ms94active
2026-11-17 20:24:06✓✓401 ms90active
2026-11-17 20:08:55✓✓400 ms90active
2026-11-17 19:53:08✓✓277 ms94active
2026-11-17 19:38:05✓✓341 ms90active
2026-11-17 19:22:49✓✓484 ms90active
2026-11-17 19:07:36✓✓562 ms91active
2026-11-17 18:52:15✓✓316 ms91active
2026-11-17 18:37:10✓✓409 ms91active
2026-11-17 18:22:05✓✓377 ms91active

Query this programmatically

Agents can pull this record live over the MCP protocol or REST:

get_server("https://maine-parks.mcp.agentstatus.dev/mcp.json")   # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/maine-parks-mcp-agentstatus-dev-mcp-json   # JSON