north-dakota.mcp.agentstatus.dev
https://north-dakota.mcp.agentstatus.dev/.well-known/mcp
active Production-safe Score 94/100 http no auth
At a glance
| Endpoint | https://north-dakota.mcp.agentstatus.dev/.well-known/mcp |
|---|---|
| Source | https://north-dakota.mcp.agentstatus.dev/ |
| Transport | http |
| Tools | 4 |
| Auth | none |
| First seen | 2026-11-11 12:58:38 |
| Last checked | 2026-11-17 21:54:51 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 429 / 722 ms |
| Last successful check | 2026-11-17 21:54:51 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (4)
search_offices— Search North Dakota DMV offices by city, ZIP code, or office name. Hours are included 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:51 | ✓ | ✓ | 632 ms | 90 | active |
| 2026-11-17 21:39:38 | ✓ | ✓ | 260 ms | 94 | active |
| 2026-11-17 21:24:21 | ✓ | ✓ | 299 ms | 94 | active |
| 2026-11-17 21:09:13 | ✓ | ✓ | 397 ms | 90 | active |
| 2026-11-17 20:54:04 | ✓ | ✓ | 463 ms | 90 | active |
| 2026-11-17 20:39:01 | ✓ | ✓ | 278 ms | 94 | active |
| 2026-11-17 20:23:58 | ✓ | ✓ | 442 ms | 90 | active |
| 2026-11-17 20:08:49 | ✓ | ✓ | 436 ms | 90 | active |
| 2026-11-17 19:53:01 | ✓ | ✓ | 638 ms | 90 | active |
| 2026-11-17 19:37:57 | ✓ | ✓ | 314 ms | 90 | active |
| 2026-11-17 19:22:37 | ✓ | ✓ | 355 ms | 90 | active |
| 2026-11-17 19:07:25 | ✓ | ✓ | 419 ms | 90 | active |
| 2026-11-17 18:52:07 | ✓ | ✓ | 427 ms | 90 | active |
| 2026-11-17 18:37:01 | ✓ | ✓ | 482 ms | 90 | active |
| 2026-11-17 18:21:57 | ✓ | ✓ | 242 ms | 94 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://north-dakota.mcp.agentstatus.dev/.well-known/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/north-dakota-mcp-agentstatus-dev-well-known-mcp # JSON