_ registry / mcp streamable-http · checked 2h ago

runheed

https://runheed.com

Registry code: 268efdd2327a66de

api record

Runheed holds the production errors reported by this workspace's apps. runheed_get_recent and runheed_search_errors list error groups with their IDs; runheed_get_error and runheed_get_error_context return one group in full; runheed_resolve_error marks a group fixed and takes the fixing commit as its comment.

endpoint
https://runheed.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is runheed live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is runheed free to use?
Not measured yet.
What tools does runheed have?
9 tools: runheed_unignore_error, runheed_search_errors, runheed_get_error, runheed_get_recent, runheed_get_trends, runheed_get_error_context, runheed_resolve_error, runheed_ignore_error, ….
Is runheed safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
345ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
9 never probed 0 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • runheed_unignore_error unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "errorId"
  ],
  "properties": {
    "errorId": {
      "type": "string",
      "description": "The error ID to unignore"
    }
  }
}
    arguments 13 lines
  • runheed_search_errors unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "number",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum number of errors to return"
    },
    "query": {
      "type": "string",
      "description": "Search query to filter errors by message or type"
    },
    "status": {
      "enum": [
        "unresolved",
        "resolved",
        "ignored"
      ],
      "type": "string",
      "description": "Filter by error status"
    },
    "projectId": {
      "type": "string",
      "description": "Filter by project ID"
    }
  }
}
    arguments 30 lines
  • runheed_get_error unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "errorId"
  ],
  "properties": {
    "errorId": {
      "type": "string",
      "description": "The error ID to get details for"
    }
  }
}
    arguments 13 lines
  • runheed_get_recent unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "number",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Number of recent errors to return"
    },
    "projectId": {
      "type": "string",
      "description": "Filter by project ID"
    }
  }
}
    arguments 17 lines
  • runheed_get_trends unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "period": {
      "enum": [
        "24h",
        "7d",
        "30d"
      ],
      "type": "string",
      "default": "24h",
      "description": "Time period to analyze"
    },
    "projectId": {
      "type": "string",
      "description": "Filter by project ID"
    }
  }
}
    arguments 20 lines
  • runheed_get_error_context unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "errorId"
  ],
  "properties": {
    "errorId": {
      "type": "string",
      "description": "The error ID to get context for"
    }
  }
}
    arguments 13 lines
  • runheed_resolve_error unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "errorId"
  ],
  "properties": {
    "comment": {
      "type": "string",
      "description": "Optional comment about the fix"
    },
    "errorId": {
      "type": "string",
      "description": "The error ID to resolve"
    }
  }
}
    arguments 17 lines
  • runheed_ignore_error unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "errorId"
  ],
  "properties": {
    "reason": {
      "type": "string",
      "description": "Reason for ignoring this error"
    },
    "errorId": {
      "type": "string",
      "description": "The error ID to ignore"
    }
  }
}
    arguments 17 lines
  • runheed_get_project_health unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "projectId": {
      "type": "string",
      "description": "Project ID (uses default if not specified)"
    }
  }
}
    arguments 10 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 268efdd2327a66de.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/268efdd2327a66de/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/268efdd2327a66de/badge.svg)](https://brick.blue/agent/268efdd2327a66de?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.