blit386.dev
https://blit386.dev/mcp
active Production-safe Score 89/100 http no auth
At a glance
| Endpoint | https://blit386.dev/mcp |
|---|---|
| Source | https://raw.githubusercontent.com/blit386/blit386/main/.agents/mcp_config.json |
| Transport | http |
| Tools | 3 |
| Auth | none |
| First seen | 2026-11-01 18:04:37 |
| Last checked | 2026-11-17 21:42:02 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 834 / 1420 ms |
| Last successful check | 2026-11-17 21:42:02 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (3)
search_docs— Keyword search across the BLIT386 documentation. Returns matching page titles, URLs, and excerpts. Use short keywords, not a sentence: "spriget_doc_page— Return the full markdown of one BLIT386 documentation page. Pass a URL from search_docs or get_docs_summary, or a site path such as "/docs/gget_docs_summary— Return the llms.txt summary of the BLIT386 documentation site.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:42:02 | ✓ | ✓ | 928 ms | 89 | active |
| 2026-11-17 20:57:10 | ✓ | ✓ | 1400 ms | 86 | active |
| 2026-11-17 20:34:09 | ✓ | ✓ | 891 ms | 89 | active |
| 2026-11-17 19:44:06 | ✓ | ✓ | 1004 ms | 86 | active |
| 2026-11-17 19:18:17 | ✓ | ✓ | 1211 ms | 86 | active |
| 2026-11-17 18:42:06 | ✓ | ✓ | 922 ms | 90 | active |
| 2026-11-17 17:58:11 | ✓ | ✓ | 1719 ms | 86 | active |
| 2026-11-17 17:31:42 | ✓ | ✓ | 612 ms | 90 | active |
| 2026-11-17 16:42:56 | ✓ | ✓ | 243 ms | 93 | active |
| 2026-11-17 16:00:18 | ✓ | ✓ | 908 ms | 90 | active |
| 2026-11-17 15:25:32 | ✓ | ✓ | 1679 ms | 86 | active |
| 2026-11-17 14:40:37 | ✓ | ✓ | 1493 ms | 86 | active |
| 2026-11-17 13:43:13 | ✓ | ✓ | 639 ms | 90 | active |
| 2026-11-17 13:25:40 | ✓ | ✓ | 1312 ms | 86 | active |
| 2026-11-17 12:42:02 | ✓ | ✓ | 753 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://blit386.dev/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/blit386-dev-mcp # JSON