# Runheed (remote · runheed.com)

Production errors your coding agent can read: search, stack traces, context, trends, resolve.

- Trust score: 82/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `runheed.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-runheed-runheed/api-mcp.md), [page](https://verifymcp.io/servers/com-runheed-runheed/api-mcp)

## Channel facts

- Endpoint: `https://runheed.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 682 tokens (~75/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Runheed MCP server?

Runheed is a hosted endpoint at https://runheed.com/api/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.

### Claude

```bash
claude mcp add --transport http com-runheed-runheed 'https://runheed.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-runheed-runheed": {
      "url": "https://runheed.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-runheed-runheed": {
      "type": "http",
      "url": "https://runheed.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-runheed-runheed]
url = "https://runheed.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-runheed-runheed": {
      "type": "remote",
      "url": "https://runheed.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-runheed-runheed --url 'https://runheed.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-runheed-runheed:
    url: "https://runheed.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-runheed-runheed": {
      "Transport": "http",
      "Url": "https://runheed.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-runheed-runheed -t streamable-http -u 'https://runheed.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-runheed-runheed": {
      "type": "http",
      "url": "https://runheed.com/api/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +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.

### 2026-11-03 (score 81, +1)

- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “runheed_get_project_health” reworded the description of “projectId”
- [cosmetic] “runheed_get_recent” reworded the description of “projectId”
- [cosmetic] “runheed_get_trends” reworded the description of “projectId”
- [cosmetic] “runheed_search_errors” reworded the description of “projectId”

### 2026-11-02 (score 80)

First indexed and scored.

## MCP tools (9)

### `runheed_search_errors` (~109 tokens)

Search errors

Searches the workspace's error groups by text (type or message), status and project. Returns each matching group with its status, type, message, event count, last-seen time and ID.

Input parameters:

- `limit` (number): Maximum number of errors to return
- `projectId` (string): Filter by project id or slug (e.g. shop-api)
- `query` (string): Search query to filter errors by message or type
- `status` (string): Filter by error status

### `runheed_get_error` (~57 tokens)

Get an error

Returns one error group in full: message, status, counts, first and last seen, environment, agent context, the top stack frames and the latest breadcrumbs.

Input parameters:

- `errorId` (string, required): The error ID to get details for

### `runheed_get_recent` (~71 tokens)

Get recent errors

Returns the error groups seen most recently, newest first, with status, type, message, event count, last-seen time and ID.

Input parameters:

- `limit` (number): Number of recent errors to return
- `projectId` (string): Filter by project id or slug (e.g. shop-api)

### `runheed_get_trends` (~77 tokens)

Get error trends

Returns error statistics for the last 24 hours, 7 days or 30 days: total, new and resolved counts, the most frequent errors and the hourly error rate.

Input parameters:

- `period` (string): Time period to analyze
- `projectId` (string): Filter by project id or slug (e.g. shop-api)

### `runheed_get_error_context` (~57 tokens)

Get error context

Returns everything recorded around an error: every breadcrumb, platform, runtime, OS, environment, release, the affected user, the agent session and extra data.

Input parameters:

- `errorId` (string, required): The error ID to get context for

### `runheed_resolve_error` (~69 tokens)

Resolve an error

Marks an error group resolved, with an optional note such as the fixing commit. The group reopens on its own if the error happens again. Returns a confirmation.

Input parameters:

- `comment` (string): Optional comment about the fix
- `errorId` (string, required): The error ID to resolve

### `runheed_ignore_error` (~58 tokens)

Ignore an error

Marks an error group ignored, for known or expected errors, so new occurrences stop alerting. Returns a confirmation.

Input parameters:

- `errorId` (string, required): The error ID to ignore
- `reason` (string): Reason for ignoring this error

### `runheed_unignore_error` (~44 tokens)

Stop ignoring an error

Moves an ignored error group back to unresolved, so new occurrences alert again. Returns a confirmation.

Input parameters:

- `errorId` (string, required): The error ID to unignore

### `runheed_get_project_health` (~74 tokens)

Get project health

Returns a 0 to 100 health score for a project (or the whole workspace), errors in the last 24 hours, the unresolved count, the error rate, recent issues and recommendations.

Input parameters:

- `projectId` (string): Project id or slug (e.g. shop-api); all projects if not specified

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-runheed-runheed/api-mcp#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80

## Common questions

### What is the Runheed MCP server?

Runheed is an MCP server listed in the public MCP registry as com.runheed/runheed. Production errors your coding agent can read: search, stack traces, context, trends, resolve. This page covers its hosted endpoint (https://runheed.com/api/mcp).

### Is the Runheed MCP server safe to use?

Runheed scores 82 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 Runheed MCP server expose?

Runheed exposes 9 tools: runheed_search_errors, runheed_get_error, runheed_get_recent, runheed_get_trends, runheed_get_error_context, and 4 more. Their descriptions and schemas cost roughly 616 tokens of context every time the server is loaded.

### Does the Runheed MCP server require authentication?

Yes. Runheed asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Runheed MCP server still maintained?

Runheed is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://runheed.com/api/mcp
- Website: https://runheed.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-runheed-runheed/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-runheed-runheed/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-runheed-runheed/api-mcp