# opchain

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

- name: io.github.asfbay-bit/opchain-skills
- version: 2.0.4
- connection class: unknown (unknown)
- trust: 97/100
- quality: 71/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.asfbay-bit%2Fopchain-skills
- tools: https://api.protogrid.dev/v1/servers/io.github.asfbay-bit%2Fopchain-skills/tools

**Not classified yet.** The remote endpoints have not been probed successfully, or the listing has nothing to connect to.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "opchain-skills": {
      "type": "http",
      "url": "https://opchain.dev/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 99
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-97% +updated-23d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 71/100 (needs work)

### protocol: n/a (weight 25)

- n/a `protocol.modern`, `protocol.stateless`, `protocol.transport`, `protocol.list_ttl`: no remote answered a protocol handshake (not probed yet, unreachable, or local-only)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: read_checkpoint (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_skills (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_skill (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 655 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history not recorded yet

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 7, about 655 tokens to load them all
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.asfbay-bit/opchain-skills.svg)](https://protogrid.dev/servers/io.github.asfbay-bit/opchain-skills)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://opchain.dev/mcp (streamable-http, auth unknown, reachable true, uptime30d 0.974359)

## Packages

_none_

## Tools (7)

- `create_checkpoint_session`: 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.
- `get_orchestrator`: Return the shared orchestrator protocol (welcome flow, pipeline map, active-chaining rules). Read once at the start of a session.
- `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.
- `list_skills`: List every opchain skill (id, displayName, description, phases, commands). Call this first to see the concept→ship pipeline.
- `read_checkpoint`: Read a skill's saved session checkpoint (where you left off). sessionId must be a private token returned by create_checkpoint_session.
- `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.
- `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 does not validate it against the opchain checkpoint protocol, so write the shape the protocol documents.