Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Coder

REMOTE · {CODER_HOSTNAME} · SCANNED AUG 3

Manage Coder workspaces, templates, and cloud development environments

Available components

remote · {coder_hostname} 0
0 this week 0 Trust /100

Degraded

One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

Trust breakdown (6 categories)

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 →

Endpoint Security0
  • TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
  • Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
  • HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
  • HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
  • DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · {coder_hostname}

# add to Claude Code
claude mcp add --transport http coder-coder https://{coder_hostname}/api/experimental/mcp/http
# ~/.codex/config.toml
[mcp_servers.coder-coder]
url = "https://{coder_hostname}/api/experimental/mcp/http"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "coder-coder": {
      "type": "remote",
      "url": "https://{coder_hostname}/api/experimental/mcp/http",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add coder-coder --url https://{coder_hostname}/api/experimental/mcp/http --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  coder-coder:
    url: "https://{coder_hostname}/api/experimental/mcp/http"
// mcp.json
{
  "mcpServers": {
    "coder-coder": {
      "type": "http",
      "url": "https://{coder_hostname}/api/experimental/mcp/http"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://{coder_hostname}/api/experimental/mcp/http

TLS unreached
DNSSEC inconclusive

Validation of https://{coder_hostname}/api/experimental/mcp/http. — Inconclusive

Zone DS Keys Algorithms Outcome
https://{coder_hostname}/api/experimental/mcp/http. Error no A/AAAA/CNAME RRset answered for the name
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://{coder_hostname}/api/experimental/mcp/http Unreachable
http (plaintext) Inconclusive
MCP tools

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.

No tool schema has been captured from this endpoint yet.