Is the Asfbay Bit Opchain Skills MCP server down?

mcp-registry/io.github.asfbay-bit/opchain-skills · v0f3410c

healthy
Last checked 2026-10-19 16:29 UTC · handshake 145ms

As of 2026-10-19 16:29 UTC, the Asfbay Bit Opchain Skills MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,804
outages (90d)
0
tools
7

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

Install Asfbay Bit Opchain Skills MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http asfbay-bit-opchain-skills-mcp-server https://opchain.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "asfbay-bit-opchain-skills-mcp-server": {
      "type": "http",
      "url": "https://opchain.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 3 warning(s) across 7 tool(s); ~807 tokens of tool definitions.
Scores higher than 30% of 15,350 MCP servers Glimind has audited.
Its tool list costs an agent ~807 tokens per session — lighter than 80% of servers.
78 → 78 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions70
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (4)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: create_checkpoint_session, get_orchestrator, get_skill, list_skills, read_checkpoint and 2 more

2 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: read_checkpoint, write_checkpoint

Handshake + tools/list takes ~1,627 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.asfbay-bit%2Fopchain-skills/fixes

create_checkpoint_session 1 change
{
  "name": "create_checkpoint_session",
  "description": "Create a private server-issued session for checkpoint storage. Retain the returned sessionId and use it with read_checkpoint/write_checkpoint; never invent or share one.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
get_orchestrator 1 change
{
  "name": "get_orchestrator",
  "description": "Return the shared orchestrator protocol (welcome flow, pipeline map, active-chaining rules). Read once at the start of a session.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_skill 1 change
{
  "name": "get_skill",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "Skill id, e.g. oc-app-architect."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.asfbay-bit/opchain-skills"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.asfbay-bit/opchain-skills"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.asfbay-bit%2Fopchain-skills.svg)](https://glimind.com/server/mcp-registry%2Fio.github.asfbay-bit%2Fopchain-skills?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.asfbay-bit%2Fopchain-skills?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.asfbay-bit%2Fopchain-skills.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.asfbay-bit%2Fopchain-skills.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.asfbay-bit%2Fopchain-skills?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:24782b0fa0ebd974…, first seen 2026-10-17, included at leaf 12159 of 27,632. Version history · verify what your client received.

Tools (7)

Compare: most reliable other servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Asfbay Bit Opchain Skills MCP server down right now?

As of 2026-10-19 16:29 UTC, the Asfbay Bit Opchain Skills MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Asfbay Bit Opchain Skills MCP server provide?

Asfbay Bit Opchain Skills MCP server advertises 7 tools, including create_checkpoint_session, get_orchestrator, get_skill, list_skills, read_checkpoint.

How do I install Asfbay Bit Opchain Skills MCP server?

Point your MCP client at this streamable-http endpoint: https://opchain.dev/mcp

Is the Asfbay Bit Opchain Skills MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Asfbay Bit Opchain Skills MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve