io.github.cyanheads/cyanheads-mcp-server
REMOTE · CYANHEADS.CASEYJHAND.COM · 2 COMPONENTS
Fleet discovery for the cyanheads MCP ecosystem — semantic search + install snippets.
Available components
Last scanned (3 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Search and Retrieval
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 861 tokens (~287/item across 3 items; 2 tools + 1 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 4 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 28 Oct 26 +2
- Schema quality: 363 → 287 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- New resource “cyanheads-guide” functional
- Server version: 0.4.5 → 0.5.0 functional
- “cyanheads_search_catalog” reworded the description of “category” cosmetic
- 24 Oct 26 0
- Server version: 0.4.4 → 0.4.5 functional
- “cyanheads_describe_entry” reworded the description of “name” cosmetic
- 19 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 292 → 363 ▼ functional
- Server version: 0.4.3 → 0.4.4 functional
- “cyanheads_describe_entry” added an optional parameter “server” cosmetic
- “cyanheads_describe_entry” reworded the description of “name” cosmetic
- “cyanheads_describe_entry” reworded the description of “client” cosmetic
- “cyanheads_search_catalog” reworded the description of “limit” cosmetic
- 30 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cyanheads_describe_entry” rewrote its description, which is the text the model reads security
- Schema quality: 229 → 292 ▼ functional
- Server version: 0.4.2 → 0.4.3 functional
- “cyanheads_search_catalog” added an optional parameter “offset” cosmetic
- “cyanheads_search_catalog” added an optional parameter “serversOffset” cosmetic
- “cyanheads_search_catalog” reworded the description of “query” cosmetic
- “cyanheads_describe_entry” reworded the description of “name” cosmetic
- 28 Sept 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
- 25 Sept 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
- 19 Sept 26 0
- Server version: 0.4.1 → 0.4.2 functional
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 6 Nov 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 | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 995a30681ab772540e934241ca1d576c |
| 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. | DS published | 19718 | 13 | Verified |
| caseyjhand.com. | DS published | 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 |
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 →
cyanheads_describe_entry Describe Fleet Tool or Server ~321
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Return install snippets for this client only (both local and remote transports when available). "streamable-http" selects the generic mcpServers JSON; "curl" selects a connectivity probe for hosted s… |
| 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_events") or server name (kebab-case, e.g. "earthquake-mcp-server"). 1-64 characters. Exact names win; unique case-insensitive names resolve to canonical… |
| server | string | – | Server that owns the tool to describe — the server value cyanheads_search_catalog returned with this name. 1-64 characters, resolved like a server name. Required when the tool name has more than one… |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | 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 Search Fleet Tools and Servers ~297
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by catalog category. Omit to search all categories. Categories are catalog labels, not publisher types (a federal agency API can be public-data), and a wrong guess silently drops the matching… |
| limit | integer | – | Maximum number of results to return (1-1000). Default 5. At most 20 per call: a larger limit returns up to 20, with a notice naming the offset to continue from when more matches follow. |
| offset | integer | – | Result offset. Use nextOffset with the same query, scope, category, and limit; pages use the current catalog. |
| query | string | yes | 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 | string | – | What to search. "tools" returns individual tool matches; "servers" returns server-level matches. |
| serversOffset | integer | – | Independent server roll-up offset (10 per page). Use nextServersOffset; must be zero in servers scope. |
| Name | Type | Req | Description |
|---|---|---|---|
| cap | number | – | Per-call result cap that was applied. |
| effectiveQuery | string | – | The query that was searched. |
| error | object | – | Present when the call failed. Absent on success. |
| nextOffset | number|null | – | Next ranked-result offset, or null when exhausted. |
| nextServersOffset | number|null | – | Next server roll-up offset, or null when exhausted; tools scope only. |
| notice | string | – | Guidance for zero matches, an exhausted result page, or a page cut to the 20-per-call cap with more matches following (names the offset to continue from). Absent otherwise. |
| offset | number | – | Current ranked-result offset. |
| results | array | – | Ranked matches, best first. |
| scope | string | – | Scope that was searched. |
| servers | array | – | Server roll-up from the full match set, independent of result offset/limit. Tools scope only. Ordered by topScore desc (name-tiebroken); 10 per page starting at serversOffset. Use nextServersOffset t… |
| serversOffset | number | – | Current server roll-up offset; tools scope only. |
| serversTotal | number | – | Total distinct servers in the full match set (before the cap of 10 is applied). Present only when servers is present. |
| shown | number | – | Results returned on this capped page. |
| totalCount | number | – | Total relevant matches before the limit was applied. |
| truncated | boolean | – | True when limit exceeded the 20-per-call cap and more matches follow this page. |
No examples provided.
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
claude mcp add --transport http cyanheads-cyanheads-mcp-server 'https://cyanheads.caseyjhand.com/mcp'
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 89 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 618 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 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.cyanheads/cyanheads-mcp-server server?
VerifyMCP ran 13 checks on io.github.cyanheads/cyanheads-mcp-server, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.