Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.cyanheads/cyanheads-mcp-server

REMOTE · CYANHEADS.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 22

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

Available components

remote · cyanheads.caseyjhand.com 82 npm · @cyanheads/cyanheads-mcp-server 39
0 this week 82 Trust /100
Trust breakdown (7 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 → Why this is hard to 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
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 459 tokens (~229/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.cyanheads/cyanheads-mcp-server server?

io.github.cyanheads/cyanheads-mcp-server is a hosted endpoint at https://cyanheads.caseyjhand.com/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 · cyanheads.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-cyanheads-mcp-server 'https://cyanheads.caseyjhand.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cyanheads-cyanheads-mcp-server": {
      "url": "https://cyanheads.caseyjhand.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cyanheads-cyanheads-mcp-server": {
      "type": "http",
      "url": "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"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cyanheads-cyanheads-mcp-server": {
      "Transport": "http",
      "Url": "https://cyanheads.caseyjhand.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cyanheads-cyanheads-mcp-server -t streamable-http -u '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.

  • 19 Sept 26 0
    • Server version: 0.4.1 → 0.4.2 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 −1
    • Stability: pass → 0.93 functional
  • 26 Aug 26 +16
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Aug 26 0
    • Tool “cyanheads_search_catalog” rewrote its description, which is the text the model reads security
    • Tool “cyanheads_describe_entry” rewrote its description, which is the text the model reads security
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 0.4.0 → 0.4.1 functional
  • 11 Aug 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
  • 10 Aug 26 0
    • Stability: unverified → fail ▼ security
    • HSTS header: fail → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: 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. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 8 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: fail → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
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 22 Sept 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 4 Sept 2026 3 Dec 2026 ECDSA 256 ECDSA-SHA256 a6985204ed51ae050e7738aa6be668e9
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

Background: What to check on a remote MCP endpoint →

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

Background: How OAuth 2.1 works in the 2026 MCP spec →

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 · ~362 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. 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 →

Tool Tokens
cyanheads_describe_entry ~206

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.

NameTypeReqDescription
clientstring–Return install snippets for this client only (both local and remote transports when available). Omit to return snippets for all supported clients.
kindstring–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.
namestringyesTool 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.
NameTypeReqDescription
errorobject–Present when the call failed. Absent on success.
result––The resolved entry — either a tool detail or a server detail depending on the resolved kind.

No examples provided.

cyanheads_search_catalog ~156

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.

NameTypeReqDescription
categorystring–Filter by catalog category. Omit to search all categories.
limitinteger–Maximum number of results to return (1-20). Default 5.
querystringyesNatural language search query. Describe what you want to accomplish, a workflow, or a capability area. 1-500 characters.
scopestring–What to search. "tools" returns individual tool matches; "servers" returns server-level matches.
NameTypeReqDescription
effectiveQuerystring–The query that was searched.
errorobject–Present when the call failed. Absent on success.
noticestring–Guidance when no results matched — e.g. how to broaden the query or try a different scope. Absent on successful result pages.
resultsarray–Ranked matches, best first.
scopestring–Scope that was searched.
serversarray–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…
serversTotalnumber–Total distinct servers in the full match set (before the cap of 10 is applied). Present only when servers is present.
totalCountnumber–Total relevant matches before the limit was applied.

No examples provided.

Common questions

What is the io.github.cyanheads/cyanheads-mcp-server server?

io.github.cyanheads/cyanheads-mcp-server is listed in the public MCP registry as io.github.cyanheads/cyanheads-mcp-server. Fleet discovery for the cyanheads MCP ecosystem, semantic search + install snippets. This page covers its hosted endpoint (https://cyanheads.caseyjhand.com/mcp).

Is the io.github.cyanheads/cyanheads-mcp-server server safe to use?

io.github.cyanheads/cyanheads-mcp-server 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 io.github.cyanheads/cyanheads-mcp-server server expose?

io.github.cyanheads/cyanheads-mcp-server exposes 2 tools: cyanheads_search_catalog, cyanheads_describe_entry. Their descriptions and schemas cost roughly 362 tokens of context every time the server is loaded.

Does the io.github.cyanheads/cyanheads-mcp-server server require authentication?

No. We connected to io.github.cyanheads/cyanheads-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.cyanheads/cyanheads-mcp-server server still maintained?

io.github.cyanheads/cyanheads-mcp-server is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.