Runheed
REMOTE · RUNHEED.COM
Production errors your coding agent can read: search, stack traces, context, trends, resolve.
Available components
Last scanned (8 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 682 tokens (~75/item across 9 items; 9 tools + 0 resources), lean.Pass
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.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.
- 5 Nov 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.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- “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” cosmetic
- 2 Nov 26 80
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 5 Nov 2026 · Probed https://runheed.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=runheed.com | CN=YE2,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6de849a9598a0cf18067ef55dc9a0017947 |
| SANs: runheed.com, www.runheed.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of runheed.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| runheed.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://runheed.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://runheed.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://runheed.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://runheed.com/api/mcp |
| Authorisation server | https://runheed.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://runheed.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://runheed.com/api/mcp | HTTPS enforced | 301 | https://runheed.com/api/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 →
runheed_get_error Get an error ~57
Returns one error group in full: message, status, counts, first and last seen, environment, agent context, the top stack frames and the latest breadcrumbs.
| Name | Type | Req | Description |
|---|---|---|---|
| errorId | string | yes | The error ID to get details for |
No output schema declared.
No examples provided.
runheed_get_error_context Get error context ~57
Returns everything recorded around an error: every breadcrumb, platform, runtime, OS, environment, release, the affected user, the agent session and extra data.
| Name | Type | Req | Description |
|---|---|---|---|
| errorId | string | yes | The error ID to get context for |
No output schema declared.
No examples provided.
runheed_get_project_health Get project health ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | – | Project id or slug (e.g. shop-api); all projects if not specified |
No output schema declared.
No examples provided.
runheed_get_recent Get recent errors ~71
Returns the error groups seen most recently, newest first, with status, type, message, event count, last-seen time and ID.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of recent errors to return |
| projectId | string | – | Filter by project id or slug (e.g. shop-api) |
No output schema declared.
No examples provided.
runheed_get_trends Get error trends ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Time period to analyze |
| projectId | string | – | Filter by project id or slug (e.g. shop-api) |
No output schema declared.
No examples provided.
runheed_ignore_error Ignore an error ~58
Marks an error group ignored, for known or expected errors, so new occurrences stop alerting. Returns a confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| errorId | string | yes | The error ID to ignore |
| reason | string | – | Reason for ignoring this error |
No output schema declared.
No examples provided.
runheed_resolve_error Resolve an error ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Optional comment about the fix |
| errorId | string | yes | The error ID to resolve |
No output schema declared.
No examples provided.
runheed_search_errors Search errors ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
runheed_unignore_error Stop ignoring an error ~44
Moves an ignored error group back to unresolved, so new occurrences alert again. Returns a confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| errorId | string | yes | The error ID to unignore |
No output schema declared.
No examples provided.
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.
remote · runheed.com
claude mcp add --transport http com-runheed-runheed 'https://runheed.com/api/mcp'
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.