@cyanheads/cyanheads-mcp-server
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: caseyjhand.com, huggingface.co, us.aws.cdn.hf.co
Its tool definitions changed since version 0.5.0. If you approved the earlier ones, read them again.
What it contacted
caseyjhand.comhuggingface.cous.aws.cdn.hf.co
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @cyanheads/cyanheads-mcp-server@0.5.1
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
cyanheads_search_catalog | Returned a result under 0.1 s · 2,506 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
cyanheads_search_catalog query, scope, category, limit, offset, serversOffset
Search fleet tools and servers by natural-language description. Returns ranked matches with the full catalog description of each entry and the server each tool belongs to. Omit query to list every tool or server in name order instead, optionally filtered by category. Use scope "servers" to find which server handles a workflow; use the default scope "tools" to find specific tools.
cyanheads_describe_entry name, server, kind, client
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.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Files it wrote
/tmp/ cyanheads-mcp-server/ hf-cache/ Snowflake/ snowflake-arctic-embed-m-v1.5/ config.json /tmp/ cyanheads-mcp-server/ hf-cache/ Snowflake/ snowflake-arctic-embed-m-v1.5/ tokenizer.json /tmp/ cyanheads-mcp-server/ hf-cache/ Snowflake/ snowflake-arctic-embed-m-v1.5/ tokenizer_config.json /tmp/ cyanheads-mcp-server/ hf-cache/ Snowflake/ snowflake-arctic-embed-m-v1.5/ onnx/ model.onnx
Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.
Install facts
| License | Apache-2.0 |
|---|---|
| Needs | node >=24.0.0 |
| Source | github.com/cyanheads/cyanheads-mcp-server |
| Install scripts | onnxruntime-node, protobufjs declare them. This runner does not run them. |
| Tarball | sha512-QFMW+WSpvilJOheWWwZFpRo+kRb/PbOQ/nqHQfPUzPX6z6+R0MCZok0gRtS6NhQObt5wTNhZ5LxYC7ud2rYJhQ== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 0.5.1 | 2026-11-16 | Starts with no setup | 2 |
| 0.5.0 | 2026-11-12 | Starts with no setup | 2 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40cyanheads/cyanheads-mcp-server)
New version out? Ask for a fresh report.