opchain.dev
https://opchain.dev/mcp
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://opchain.dev/mcp |
|---|---|
| Source | https://github.com/asfbay-bit/opchain/blob/main/.github/workflows/publish-mcp-registry.yml |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-08-29 15:54:27 |
| Last checked | 2026-11-17 21:51:32 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 317 / 527 ms |
| Last successful check | 2026-11-17 21:51:32 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
list_skills— List every opchain skill (id, displayName, description, phases, commands). Call this first to see the concept→ship pipeline.route— Map a request or an /oc-* command to the skill that should handle it, with the entry phase. Use when you're unsure which skill fits.get_skill— Return the full SKILL.md (the instructions) for one skill id. Load it, then follow it. Read get_orchestrator once before your first get_skilget_orchestrator— Return the shared orchestrator protocol (welcome flow, pipeline map, active-chaining rules). Read once at the start of a session.create_checkpoint_session— Create a private server-issued session for checkpoint storage. Retain the returned sessionId and use it with read_checkpoint/write_checkpoinread_checkpoint— Read a skill's saved session checkpoint (where you left off). sessionId must be a private token returned by create_checkpoint_session.write_checkpoint— Persist a skill's session checkpoint so progress survives across sessions. Stores the object as given (any JSON object up to 64 KiB); it doe
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:51:32 | ✓ | ✓ | 191 ms | 94 | active |
| 2026-11-17 21:36:21 | ✓ | ✓ | 405 ms | 90 | active |
| 2026-11-17 21:21:06 | ✓ | ✓ | 350 ms | 90 | active |
| 2026-11-17 21:05:59 | ✓ | ✓ | 380 ms | 90 | active |
| 2026-11-17 20:50:38 | ✓ | ✓ | 262 ms | 94 | active |
| 2026-11-17 20:35:23 | ✓ | ✓ | 404 ms | 90 | active |
| 2026-11-17 20:20:17 | ✓ | ✓ | 300 ms | 90 | active |
| 2026-11-17 20:05:10 | ✓ | ✓ | 381 ms | 90 | active |
| 2026-11-17 19:49:45 | ✓ | ✓ | 386 ms | 90 | active |
| 2026-11-17 19:34:35 | ✓ | ✓ | 356 ms | 90 | active |
| 2026-11-17 19:19:27 | ✓ | ✓ | 299 ms | 94 | active |
| 2026-11-17 19:04:10 | ✓ | ✓ | 326 ms | 90 | active |
| 2026-11-17 18:49:00 | ✓ | ✓ | 457 ms | 90 | active |
| 2026-11-17 18:33:48 | ✓ | ✓ | 228 ms | 94 | active |
| 2026-11-17 18:18:37 | ✓ | ✓ | 352 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://opchain.dev/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/opchain-dev-mcp # JSON