_ registry / mcp http-sse · checked 23m ago

cyanheads-mcp-server

https://cyanheads.caseyjhand.com

Registry code: a8f658853ab44a65

api record

This server is the discovery front door to the cyanheads MCP fleet. Use cyanheads_search_catalog to find tools or servers by describing what you want to do. Use cyanheads_describe_entry to get descriptions, connection metadata, and per-client install snippets for any result. Tool schemas are available from the connected server through tools/list. Continue searches with nextOffset and, in tools scope, nextServersOffset; reuse the same query and filters. Scope "tools" (default) finds individual tools; scope "servers" finds which server owns a workflow. cyanheads_describe_entry also resolves…

endpoint
https://cyanheads.caseyjhand.com/mcp
protocol
http-sse ·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 cyanheads-mcp-server live?
Yes — it answered the hub's last check (checked 23m ago). It answered 100% of checks over the last 30 days.
Is cyanheads-mcp-server free to use?
Yes — the hub reached it with no key and no payment.
What tools does cyanheads-mcp-server have?
2 tools: cyanheads_search_catalog, cyanheads_describe_entry.
Is cyanheads-mcp-server 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 99.5%· all time 99.5%

latency
493ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 397 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search a catalog of mcp tools and servers
  • get install snippets for an mcp server
takes → gives
text → data
tools
2 reads
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • cyanheads_search_catalog reads unknown 14h ago

    Search fleet tools and servers by natural-language description. Returns ranked matches with brief summaries and the server each tool belongs to. Use scope "servers" to find which server handles a workflow; use the default scope "tools" to find specific tools.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 1,
          "description": "Maximum number of results to return (1-20). Default 5."
        },
        "query": {
          "type": "string",
          "pattern": "\\S",
          "maxLength": 500,
          "minLength": 1,
          "description": "Natural language search query. Describe what you want to accomplish, a workflow, or a capability area. 1-500 raw characters; surrounding whitespace is trimmed. Must contain non-whitespace text."
        },
        "scope": {
          "enum": [
            "tools",
            "servers"
          ],
          "type": "string",
          "default": "tools",
          "description": "What to search. \"tools\" returns individual tool matches; \"servers\" returns server-level matches."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Result offset. Use nextOffset with the same query, scope, category, and limit; pages use the current catalog."
        },
        "category": {
          "enum": [
            "research",
            "government",
            "public-data",
            "utility"
          ],
          "type": "string",
          "description": "Filter by catalog category. Omit to search all categories."
        },
        "serversOffset": {
          "type": "integer",
          "default": 0,
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Independent server roll-up offset (10 per page). Use nextServersOffset; must be zero in servers scope."
        }
      },
      "additionalProperties": false
    }
    arguments 57 lines
  • cyanheads_describe_entry reads unknown 14h ago

    Return the description and install snippets for a named tool or server. For tools: the description, owning server, and connection metadata. For either kind: local (stdio, via npx) install snippets for every published server, plus remote (HTTP) connection snippets when a hosted endpoint exists — for every supported client, or one client via the client parameter.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "name"
      ],
      "properties": {
        "kind": {
          "enum": [
            "tool",
            "server"
          ],
          "type": "string",
          "description": "Whether name refers to a tool or server. Omit to auto-detect: names containing underscores are treated as tools; names containing hyphens are treated as servers."
        },
        "name": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Tool name (snake_case, e.g. \"earthquake_search\") or server name (kebab-case, e.g. \"earthquake-mcp-server\"). 1-64 characters. Exact names win; unique case-insensitive names resolve to canonical names. Use cyanheads_search_catalog to discover valid names."
        },
        "client": {
          "enum": [
            "claude-code",
            "codex",
            "cursor",
            "curl",
            "gemini",
            "streamable-http"
          ],
          "type": "string",
          "description": "Return install snippets for this client only (both local and remote transports when available). Omit to return snippets for all supported clients."
        }
      },
      "additionalProperties": false
    }
    arguments 36 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 a8f658853ab44a65.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a8f658853ab44a65/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/a8f658853ab44a65/badge.svg)](https://brick.blue/agent/a8f658853ab44a65?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
60%

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.

_ also on caseyjhand.com 109 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

101 more sit on this domain. All of them.