Is the Ascent Partners Opencode Workbench MCP server down?

mcp-registry/com.ascent-partners/opencode-workbench · v4.0.2

Also listed as github/simonmak-ascent/opencode-workbench

As of 2026-10-21 19:09 UTC, the Ascent Partners Opencode Workbench MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

Provision an OpenCode workbench and MCP stack on any Linux box, local or over SSH.

claude mcp add --transport http ascent-partners-opencode-workbench-mcp-s https://opencode-workbench.simonmak.com/mcp

{
  "mcpServers": {
    "ascent-partners-opencode-workbench-mcp-s": {
      "type": "http",
      "url": "https://opencode-workbench.simonmak.com/mcp"
    }
  }
}

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

Agent-readiness: A (97/100)

What to fix (1)

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/com.ascent-partners/opencode-workbench"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.ascent-partners/opencode-workbench"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~4,320 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• apply_clone ~537 tokens
• plan_clone ~500 tokens
• verify_clone ~500 tokens
• remove_component ~496 tokens
• update_component ~495 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ascent-partners%2Fopencode-workbench.svg)](https://glimind.com/server/mcp-registry%2Fcom.ascent-partners%2Fopencode-workbench?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.ascent-partners%2Fopencode-workbench?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ascent-partners%2Fopencode-workbench.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ascent-partners%2Fopencode-workbench.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.ascent-partners%2Fopencode-workbench?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:39197db5fa6f9462…, first seen 2026-10-17, included at leaf 16272 of 41,143. Version history · verify what your client received.

Tools (12)

• apply_clone
• describe_workbench
• inspect_target
• install
• install_component
• list_required_credentials
• plan_clone
• remove
• remove_component
• run_auth_flow
• update_component
• verify_clone

Compare: most reliable devops servers · most reliable knowledge servers · most reliable security servers

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

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

FAQ

Is the Ascent Partners Opencode Workbench MCP server down right now?

As of 2026-10-21 19:09 UTC, the Ascent Partners Opencode Workbench MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Ascent Partners Opencode Workbench MCP server provide?

Ascent Partners Opencode Workbench MCP server advertises 12 tools, including apply_clone, describe_workbench, inspect_target, install, install_component.

How do I install Ascent Partners Opencode Workbench MCP server?

Point your MCP client at this streamable-http endpoint: https://opencode-workbench.simonmak.com/mcp

Is the Ascent Partners Opencode Workbench MCP server safe to connect to an AI agent?

Glimind scanned all 10 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 Ascent Partners Opencode Workbench 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.