io.github.cyanheads/cyanheads-mcp-server

REMOTE · CYANHEADS.CASEYJHAND.COM · 2 COMPONENTS · SCANNED AUG 3

Fleet discovery for the cyanheads MCP ecosystem — semantic search + install snippets.

Available components

remote · cyanheads.caseyjhand.com 65 npm · @cyanheads/cyanheads-mcp-server 33

+2 this week 65 65 Trust /100

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 Security66

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability66

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 489 tokens (~244/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability check failed: schema churn in the 8 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail

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
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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 · cyanheads.caseyjhand.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http cyanheads-cyanheads-mcp-server https://cyanheads.caseyjhand.com/mcp

# ~/.codex/config.toml

[mcp_servers.cyanheads-cyanheads-mcp-server]
url = "https://cyanheads.caseyjhand.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-cyanheads-mcp-server": {
      "type": "remote",
      "url": "https://cyanheads.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add cyanheads-cyanheads-mcp-server --url https://cyanheads.caseyjhand.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  cyanheads-cyanheads-mcp-server:
    url: "https://cyanheads.caseyjhand.com/mcp"

// mcp.json

{
  "mcpServers": {
    "cyanheads-cyanheads-mcp-server": {
      "type": "http",
      "url": "https://cyanheads.caseyjhand.com/mcp"
    }
  }
}

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 +2
- 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 −1
- Stability: unverified → fail ▼ security
- 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 64

First indexed and scored.

Show 2 earlier entries Hide earlier entries

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://cyanheads.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=caseyjhand.com	CN=WE1,O=Google Trust Services,C=US	7 Jul 2026	5 Oct 2026	ECDSA 256	ECDSA-SHA256	5aad900eb2055a0b0ea55912ec19680c
SANs: caseyjhand.com, *.caseyjhand.com
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC secure

Validation of cyanheads.caseyjhand.com. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
caseyjhand.com.	present	2371	13	Verified
cyanheads.caseyjhand.com.				Verified address RRset verified with the apex keys

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=63072000; includeSubDomains; preload
x-content-type-options	nosniff

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://cyanheads.caseyjhand.com/mcp	Verified	200
http (plaintext)	http://cyanheads.caseyjhand.com/mcp	HTTPS enforced	301	https://cyanheads.caseyjhand.com/mcp

MCP tools — 2 exposed · ~392 tokens

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.

Tool Tokens

cyanheads_describe_entry Describe Fleet Tool or Server ~217

Return the description and install snippets for a named tool or server. For tools: the description and the server it belongs to. For servers: 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. Call cyanheads_search_catalog first to find valid names.

Input Output Examples

Name	Type	Req	Description
client	string	—	Return install snippets for this client only (both local and remote transports when available). Omit to return snippets for all supported clients.
kind	string	—	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	string	yes	Tool name (snake_case, e.g. "earthquake_search") or server name (kebab-case, e.g. "earthquake-mcp-server"). 1-64 characters. Use cyanheads_search_catalog to discover valid names.

Name	Type	Req	Description
result	—	yes	The resolved entry — either a tool detail or a server detail depending on the resolved kind.

No examples provided.

cyanheads_search_catalog Search Fleet Tools and Servers ~175

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. Call cyanheads_describe_entry on a result name to get install snippets and the connection URL.

Input Output Examples

Name	Type	Req	Description
category	string	—	Filter by catalog category. Omit to search all categories.
limit	integer	—	Maximum number of results to return (1-20). Default 5.
query	string	yes	Natural language search query. Describe what you want to accomplish, a workflow, or a capability area. 1-500 characters.
scope	string	—	What to search. "tools" returns individual tool matches; "servers" returns server-level matches.

Name	Type	Req	Description
effectiveQuery	string	yes	The query that was searched.
notice	string	—	Guidance when no results matched — e.g. how to broaden the query or try a different scope. Absent on successful result pages.
results	array	yes	Ranked matches, best first.
scope	string	yes	Scope that was searched.
servers	array	—	Roll-up of distinct servers across the full match set, before the limit slice. Present only for scope "tools". Ordered by topScore desc (name-tiebroken); capped at 10. Use serversTotal to see how man…
serversTotal	number	—	Total distinct servers in the full match set (before the cap of 10 is applied). Present only when servers is present.
totalCount	number	yes	Total relevant matches before the limit was applied.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	64
27 Jul	63
28 Jul	63
29 Jul	63
30 Jul	63
31 Jul	65
1 Aug	65
2 Aug	65
3 Aug	65