com.ascent-partners/opencode-workbench
REMOTE · OPENCODE-WORKBENCH.SIMONMAK.COM · 2 COMPONENTS
Provision an OpenCode workbench and MCP stack on any Linux box, local or over SSH.
Available components
Last scanned (2 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (apply_clone). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2267 tokens (~226/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://opencode-workbench.simonmak.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.simonmak.com | CN=YR1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA256-RSA | 60c9b6a74abc74166d9a473b939c88a8f13 |
| SANs: *.simonmak.com, simonmak.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of opencode-workbench.simonmak.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| simonmak.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://opencode-workbench.simonmak.com/mcp | Verified | 200 | |
| http (plaintext) | http://opencode-workbench.simonmak.com/mcp | HTTPS enforced | 308 | https://opencode-workbench.simonmak.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
apply_clone Apply a Workbench clone ~320
Apply the Workbench profile to a target: clone the repo and install missing components (OpenCode CLI, Node/pnpm, MCP servers, skills, plugins, optional Docker). It OVERWRITES `<home>/.config/opencode/opencode.json`, copies `AGENTS.md`, resets an existing profile repo to `origin/main`, and runs global installs that need write permission (plus SSH for `mode:ssh`) and can take minutes. Writes a names-only `~/.env.workbench` (mode 600); never secret values. Consent-gated and idempotent: without `confirm:true` it returns the plan and changes nothing. Parameter semantics: `components` defaults to required+core; `workspace` defaults to `~/opencode-workbench`; `skipRepo` skips the clone/update; `profileUrl` overrides the git remote; `dryRun` returns the plan. To preview only, use plan_clone.
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | – | Component ids to include; defaults to required+core. |
| confirm | boolean | – | Set true to actually install. When absent, the call returns a plan and makes no changes. |
| dryRun | boolean | – | Report only; make no changes. |
| profileUrl | string | – | Override profile git URL. |
| skipRepo | boolean | – | Do not clone/update the profile repo on the target. |
| target | object | yes | The machine to operate on: this host (local) or a remote host over SSH (ssh). |
| workspace | string | – | Target directory for the profile repo. |
| Name | Type | Req | Description |
|---|---|---|---|
| configPath | string | yes | Path of the written opencode.json. |
| degraded | array | yes | Capabilities disabled because required credentials are absent; fill the named env vars to enable them. |
| dryRun | boolean | yes | True when the run made no changes. |
| envPath | string | yes | Path of the written ~/.env.workbench template. |
| envVars | array | yes | Environment variable names listed in the env template. |
| installed | array | yes | Components installed, with exit codes and output. |
| model | string | yes | Default model selected for the target (DeepSeek when its key is present, else the OpenCode Zen free floor). |
| plan | object | – | Presented when confirmation is required. |
| providerMode | string | yes | Which provider the model resolves to. |
| requiresConfirmation | boolean | – | True when the call returned a plan without applying; re-call with confirm:true to install. |
| skipped | array | yes | Component ids skipped (already present or manual). |
| target | string | yes | Label of the target. |
| workspace | string | yes | Directory where the profile repo was cloned. |
No examples provided.
describe_workbench Workbench server info ~96
Describe this MCP server from its bundled profile without contacting any target or making a network call: repository URL, the default component set, components grouped by tier (required/core/optional), and optional MCP add-ons. It takes no parameters, is always safe, and returns instantly. Use it first to resolve a component id for install_component/remove_component/update_component or to see available add-ons; use inspect_target for a machine's live state.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | yes | Every component with id, tier and description. |
| defaultComponents | array | yes | Component ids installed by default. |
| optionalMcp | array | yes | Optional MCP add-on ids available in the profile. |
| packageRoot | string | yes | Filesystem path of the installed package. |
| repo | string | yes | Web URL of the workbench repository. |
| repoGit | string | yes | Git clone URL of the workbench repository. |
No examples provided.
inspect_target Inspect a Linux target ~224
Probe one Linux machine — this host (`local`) or a remote host over SSH (`ssh`) — and report its OS, kernel, architecture, package manager, Node/npm, OpenCode, Docker, and per-tool detection flags, plus the names (never values) of credentials present. Read-only: it runs one shell probe as the target user (over SSH when `mode:ssh`), installs nothing, writes nothing, contacts no external service, and can take a few seconds per hop. Parameter semantics: `target.mode` selects local vs ssh (default `local`); `target.host` is required only for ssh; `target.user` defaults to the ssh config/current user; `target.cwd` sets the directory for relative checks; `target.port`/`identityFile` pass straight to ssh. Use it to see what a clone would touch, then plan_clone to turn that into an ordered plan and apply_clone to perform it.
| Name | Type | Req | Description |
|---|---|---|---|
| target | object | yes | The machine to operate on: this host (local) or a remote host over SSH (ssh). |
| Name | Type | Req | Description |
|---|---|---|---|
| arch | string | – | CPU architecture (e.g. x86_64, aarch64). |
| configDir | string | yes | OpenCode config directory on the target. |
| dockerRunning | boolean | – | Whether the Docker daemon is reachable. |
| envPresent | string | – | Space-separated names of credentials present on the target (values are never read). |
| has | object | yes | Detection flags for git, curl, node, npm, corepack, pnpm, docker, uv, gh, opencode, sudo. |
| home | string | yes | Home directory on the target. |
| kernel | string | – | Kernel name and release. |
| nodeVersion | string | – | Installed Node.js version, if any. |
| npmModules | string | – | npm global modules directory. |
| opencodeBin | string | – | Path to the opencode binary, if installed. |
| osId | string | – | OS identifier (e.g. ubuntu, debian, rhel). |
| osName | string | – | Human-readable OS name. |
| osVersion | string | – | OS version string. |
| packageManager | string | – | Detected package manager (apt-get, dnf, yum, apk, pacman, zypper, or none). |
| user | string | yes | Detected user on the target. |
| workspaceDefault | string | yes | Default directory where the profile repo will be cloned. |
No examples provided.
install_component Install one Workbench component ~237
Install a single Workbench component by id (e.g. `node`, `opencode`, `npm-mcps`, `skills`) on a target; `component` must be an id from describe_workbench. Overwrites that component's files when present (e.g. `skills`/`plugins` replace the copies under `<home>/.config/opencode`); global installs need write permission and can take minutes. Idempotent and consent-gated: without `confirm:true` it returns the plan. Parameter semantics: `component` is required; `workspace` defaults to `~/opencode-workbench`; `confirm` defaults to false (plan only). Use it for one targeted component; use apply_clone to install the full default set.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Component id from describe_workbench. |
| confirm | boolean | – | Set true to actually install. When absent, the call returns a plan and makes no changes. |
| target | object | yes | The machine to operate on: this host (local) or a remote host over SSH (ssh). |
| workspace | string | – | Target directory for the profile repo. |
| Name | Type | Req | Description |
|---|---|---|---|
| configPath | string | yes | Path of the written opencode.json. |
| degraded | array | yes | Capabilities disabled because required credentials are absent; fill the named env vars to enable them. |
| dryRun | boolean | yes | True when the run made no changes. |
| envPath | string | yes | Path of the written ~/.env.workbench template. |
| envVars | array | yes | Environment variable names listed in the env template. |
| installed | array | yes | Components installed, with exit codes and output. |
| model | string | yes | Default model selected for the target (DeepSeek when its key is present, else the OpenCode Zen free floor). |
| plan | object | – | Presented when confirmation is required. |
| providerMode | string | yes | Which provider the model resolves to. |
| requiresConfirmation | boolean | – | True when the call returned a plan without applying; re-call with confirm:true to install. |
| skipped | array | yes | Component ids skipped (already present or manual). |
| target | string | yes | Label of the target. |
| workspace | string | yes | Directory where the profile repo was cloned. |
No examples provided.
list_required_credentials List required credentials ~179
List the credentials the profile references, which the target already provides, and how to acquire each missing one. Value-blind: it reads only whether each env var is set — no values, no network, no writes — via one read-only probe. Parameter semantics: `target` selects the machine (`local` or SSH) and its `home` sets the returned `template` path and the env file the presence check reads; there are no other parameters. Returns `present`/`missing` var-name arrays plus one guidance record per credential (`var`, `purpose`, `url`, `method`, `command`). Use it after plan_clone to see what would degrade; act on one credential with run_auth_flow.
| Name | Type | Req | Description |
|---|---|---|---|
| target | object | yes | The machine to operate on: this host (local) or a remote host over SSH (ssh). |
| Name | Type | Req | Description |
|---|---|---|---|
| credentials | array | yes | Every credential the profile references with its acquisition guidance. |
| missing | array | yes | Credential names not present. |
| present | array | yes | Credential names already present on the target. |
| target | string | yes | Label of the inspected target. |
| template | string | yes | Path of the env file to fill in. |
No examples provided.
plan_clone Plan a Workbench clone ~232
Return a read-only plan for a target: compare it against the Workbench profile and list each component as `install`, `present`, or `manual`, with the commands that would run. It still runs a detection probe on the target (same access as inspect_target) but clones nothing and writes nothing. Parameter semantics: `components` restricts the diff to those ids (default: required+core); `workspace` sets the expected profile path on the target (default `~/opencode-workbench`); `profileUrl` overrides the git remote. Use it to preview before apply_clone, which performs the changes.
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | – | Component ids to include; defaults to required+core. |
| dryRun | boolean | – | Report only; make no changes. |
| profileUrl | string | – | Override profile git URL. |
| skipRepo | boolean | – | Do not clone/update the profile repo on the target. |
| target | object | yes | The machine to operate on: this host (local) or a remote host over SSH (ssh). |
| workspace | string | – | Target directory for the profile repo. |
| Name | Type | Req | Description |
|---|---|---|---|
| inspect | object | yes | Full inspection of the target. |
| steps | array | yes | Per-component plan. |
| target | string | yes | Label of the inspected target. |
| toInstall | array | yes | Component ids that will be installed. |
No examples provided.
remove_component Remove one Workbench component ~285
Uninstall one Workbench component by id from a target — the inverse of install_component — for a bounded, documented subset with an automated uninstall (e.g. `opencode`, `pnpm`, `npm-mcps`, `skills`, `docker-containers`); `component` must be an id from describe_workbench. Idempotent: an already-absent component reports `absent`; a component with no automated uninstall (system packages such as git/curl/node) reports `manual`. Destructive and consent-gated: without `confirm:true` it returns a preview and changes nothing, and it deletes only that component's files — never `opencode.json` or the profile repo. Parameter semantics: `workspace` sets the profile path some removals need; `dryRun` reports without changing. Use it to tear down one component; for several, call it per id.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Component id from describe_workbench. |
| confirm | boolean | – | Set true to actually remove. When absent, the call returns a preview and makes no changes. |
| dryRun | boolean | – | Report the action without changing anything. |
| target | object | yes | The machine to operate on: this host (local) or a remote host over SSH (ssh). |
| workspace | string | – | Profile repo directory (used by components whose removal needs it). |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What happened: removed, updated, already absent, or manual (no automated uninstall). |
| code | number | yes | Exit code of the action. |
| id | string | yes | Component id acted on. |
| output | string | yes | Captured output (truncated). |
| requiresConfirmation | boolean | – | True when the call returned a preview without acting; re-call with confirm:true. |
| target | string | yes | Label of the target. |
No examples provided.
run_auth_flow Acquire one credential (best-effort) ~202
Return the acquisition plan for one credential on a target: the provider URL, the exact non-interactive command when one exists (e.g. `opencode auth login`, `opencode mcp auth vercel`, `gh auth login`), and whether it is already present. Read-only and value-blind: it emits guidance and re-checks presence with one read-only probe; it does not run the commands or handle secret values. Parameter semantics: `var` must be an env var name returned by list_required_credentials (unknown names error); `target` selects the machine and its `home` is where the value should be written. Use it for a single credential; it does not replace that listing.
| Name | Type | Req | Description |
|---|---|---|---|
| target | object | yes | The machine to operate on: this host (local) or a remote host over SSH (ssh). |
| var | string | yes | Credential env var name from list_required_credentials (e.g. OPENCODE_API_KEY). |
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | Command for the agent/user to run. |
| method | string | yes | Acquisition method. |
| next | string | yes | What to do next. |
| present | boolean | yes | Whether the credential is present now. |
| target | string | yes | Label of the target. |
| url | string | – | Provider URL to open. |
| var | string | yes | Credential being acquired. |
| verified | boolean | yes | True when the credential is present and ready. |
No examples provided.
update_component Update one Workbench component ~234
Update one Workbench component in place by id: re-run its install script to fetch the current version (e.g. `opencode` re-runs the official installer; `npm-mcps` reinstalls the latest globals). It OVERWRITES the component's files, needs write permission, and can take minutes for global installs; the resolved version may change. Parameter semantics: `component` must be an id from describe_workbench; `workspace` defaults to `~/opencode-workbench`; `dryRun` previews; `confirm` defaults to false — set `confirm:true` to apply. For the whole profile use apply_clone.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Component id from describe_workbench. |
| confirm | boolean | – | Set true to actually update. When absent, the call returns a preview and makes no changes. |
| dryRun | boolean | – | Report the action without changing anything. |
| target | object | yes | The machine to operate on: this host (local) or a remote host over SSH (ssh). |
| workspace | string | – | Profile repo directory (used by components whose update needs it). |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What happened: removed, updated, already absent, or manual (no automated uninstall). |
| code | number | yes | Exit code of the action. |
| id | string | yes | Component id acted on. |
| output | string | yes | Captured output (truncated). |
| requiresConfirmation | boolean | – | True when the call returned a preview without acting; re-call with confirm:true. |
| target | string | yes | Label of the target. |
No examples provided.
verify_clone Verify a Workbench clone ~258
Re-check a target after a clone: return a per-component `present`/`missing` list plus whether `opencode.json` and `~/.env.workbench` exist. Read-only and idempotent: it runs a detection probe (SSH or local) and checks files, writing nothing. `target` selects the machine (`local` or SSH) and its `home` is where the `opencode.json` and `~/.env.workbench` checks run; `components` restricts the check to those ids (omit it to check every component, the default); `workspace` sets the profile path used by component checks. Use it after apply_clone and after component changes; for a pre-clone preview use plan_clone.
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | – | Component ids to include; defaults to required+core. |
| dryRun | boolean | – | Report only; make no changes. |
| profileUrl | string | – | Override profile git URL. |
| skipRepo | boolean | – | Do not clone/update the profile repo on the target. |
| target | object | yes | The machine to operate on: this host (local) or a remote host over SSH (ssh). |
| workspace | string | – | Target directory for the profile repo. |
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | yes | Per-component presence detection. |
| configExists | boolean | yes | Whether opencode.json exists on the target. |
| envExists | boolean | yes | Whether ~/.env.workbench exists on the target. |
| missing | array | yes | Component ids detected as missing. |
| target | string | yes | Label of the target. |
No examples provided.
How do I install the com.ascent-partners/opencode-workbench MCP server?
com.ascent-partners/opencode-workbench is a hosted endpoint at https://opencode-workbench.simonmak.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · opencode-workbench.simonmak.com
claude mcp add --transport http com-ascent-partners-opencode-workbench 'https://opencode-workbench.simonmak.com/mcp'
What is the com.ascent-partners/opencode-workbench MCP server?
com.ascent-partners/opencode-workbench is an MCP server listed in the public MCP registry as com.ascent-partners/opencode-workbench. Provision an OpenCode workbench and MCP stack on any Linux box, local or over SSH. This page covers its hosted endpoint (https://opencode-workbench.simonmak.com/mcp).
Is the com.ascent-partners/opencode-workbench MCP server safe to use?
com.ascent-partners/opencode-workbench scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.ascent-partners/opencode-workbench MCP server expose?
com.ascent-partners/opencode-workbench exposes 10 tools: describe_workbench, inspect_target, plan_clone, apply_clone, verify_clone, and 5 more. Their descriptions and schemas cost roughly 2,267 tokens of context every time the server is loaded.
Does the com.ascent-partners/opencode-workbench MCP server require authentication?
No. We connected to com.ascent-partners/opencode-workbench without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.ascent-partners/opencode-workbench MCP server still maintained?
com.ascent-partners/opencode-workbench is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.