mcpbeat

opchain MCP Server

io.github.asfbay-bit/opchain-skills
answering

opchain is answering right now. Last checked 7 min ago. It exposes 6 tools. Last commit 28 Jul 2026.

Claude Code / MCP skills for the dev pipeline: discover, spec, design, build, ship, operate.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
158 ms
Response time
average over 24h
0
Stars
last commit 28 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add opchain-skills --transport http https://opchain.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "opchain-skills": {
      "url": "https://opchain.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.opchain-skills]
url = "https://opchain.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "opchain-skills": {
      "url": "https://opchain.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "opchain-skills": {
      "url": "https://opchain.dev/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

checkpoint
read_checkpoint
Read a skill's saved session checkpoint (where you left off). sessionId scopes state to one project/conversation.
write_checkpoint
Persist a skill's session checkpoint so progress survives across sessions, per the opchain checkpoint protocol.
orchestrator
get_orchestrator
Return the shared orchestrator protocol (welcome flow, pipeline map, active-chaining rules). Read once at the start of a session.
route
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.
skill
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_skill in a session.
skills
list_skills
List every opchain skill (id, displayName, description, phases, commands). Call this first to see the concept→ship pipeline.

Endpoints

URLTransportStateLatencyChecked
https://opchain.dev/mcp streamable-http answering 152 ms 7 min ago

opchain — questions

Answers built from our own checks of this server.

What can opchain do?
It exposes 6 tools, read directly from the server on our last check. Among them: get_orchestrator, get_skill, list_skills, read_checkpoint, route, write_checkpoint. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is opchain working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 158 ms. The bar chart above shows every period we have measured.
How do I connect opchain?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does opchain need an API key?
No. opchain completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is opchain?
It answers our handshake in 158 ms on average, which is faster than 72% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is opchain open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.