arclan-ai-mcp
Validated registry of MCP servers, OpenAPI tools, and AI plugins — continuously tested via live handshake, scored on rolling reliability, and monitored for uptime.
active Production-safe Score 97/100 http no auth
At a glance
| Endpoint | https://arclan.ai/mcp |
|---|---|
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-03-17 11:04:46 |
| Last checked | 2026-11-17 21:53:57 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 42 / 262 ms |
| Last successful check | 2026-11-17 21:53:57 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
query_registry— Search the Arclan registry for MCP servers. By default returns only connectable servers (active, mcp_partial, auth_gated). Use status=stdioget_server— Get full details for a specific MCP server. Pass the server name (e.g. "GitHub", "Brave Search"), registry ID slug, or endpoint URL. Returnsrecommend_server— Get ranked MCP server recommendations for a task. Returns servers scored by production safety, keyword relevance, registry score, latency, areport_server— Submit an agent usage report for an MCP server. Reports are aggregated and influence registry trust scores. Call this after using an MCP sersign_in— Start GitHub sign-in to get an Arclan API key, without leaving MCP (OAuth device flow). Returns a verification URL and a short user_code — scomplete_sign_in— Finish the GitHub sign-in started by sign_in and return a new Arclan API key. Pass the device_code from sign_in. If the user has not authori
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:53:57 | ✓ | ✓ | 255 ms | 96 | active |
| 2026-11-17 21:38:48 | ✓ | ✓ | 182 ms | 96 | active |
| 2026-11-17 21:23:34 | ✓ | ✓ | 13 ms | 99 | active |
| 2026-11-17 21:08:19 | ✓ | ✓ | 12 ms | 99 | active |
| 2026-11-17 20:53:18 | ✓ | ✓ | 171 ms | 96 | active |
| 2026-11-17 20:38:16 | ✓ | ✓ | 44 ms | 99 | active |
| 2026-11-17 20:23:12 | ✓ | ✓ | 203 ms | 96 | active |
| 2026-11-17 20:08:04 | ✓ | ✓ | 177 ms | 96 | active |
| 2026-11-17 19:52:13 | ✓ | ✓ | 46 ms | 99 | active |
| 2026-11-17 19:37:08 | ✓ | ✓ | 12 ms | 99 | active |
| 2026-11-17 19:21:55 | ✓ | ✓ | 26 ms | 99 | active |
| 2026-11-17 19:06:43 | ✓ | ✓ | 13 ms | 99 | active |
| 2026-11-17 18:51:31 | ✓ | ✓ | 16 ms | 99 | active |
| 2026-11-17 18:36:25 | ✓ | ✓ | 185 ms | 96 | active |
| 2026-11-17 18:21:21 | ✓ | ✓ | 12 ms | 99 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://arclan.ai/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/arclan-ai-mcp # JSON