Arclan / Servers

alabama.mcp.agentstatus.dev

https://alabama.mcp.agentstatus.dev/.well-known/mcp

active Production-safe Score 94/100 http no auth

At a glance

Endpointhttps://alabama.mcp.agentstatus.dev/.well-known/mcp
Sourcehttps://alabama.mcp.agentstatus.dev/
Transporthttp
Tools4
Authnone
First seen2026-11-11 12:58:38
Last checked2026-11-17 21:54:43

Observed reliability

7-day uptime100%
24-hour uptime100%
Handshake success100%
Latency p50 / p95429 / 704 ms
Last successful check2026-11-17 21:54:43

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

Tools (4)

Validation history

CheckedReachableHandshakeLatencyScoreState
2026-11-17 21:54:43✓✓306 ms90active
2026-11-17 21:39:31✓✓423 ms90active
2026-11-17 21:24:13✓✓429 ms90active
2026-11-17 21:09:05✓✓518 ms90active
2026-11-17 20:53:56✓✓479 ms90active
2026-11-17 20:38:53✓✓349 ms90active
2026-11-17 20:23:49✓✓440 ms90active
2026-11-17 20:08:40✓✓425 ms90active
2026-11-17 19:52:53✓✓326 ms90active
2026-11-17 19:37:49✓✓431 ms90active
2026-11-17 19:22:27✓✓273 ms94active
2026-11-17 19:07:15✓✓427 ms90active
2026-11-17 18:51:59✓✓299 ms94active
2026-11-17 18:36:54✓✓251 ms94active
2026-11-17 18:21:50✓✓392 ms90active

Query this programmatically

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

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