io.github.cyanheads/cyanheads-mcp-server

Est-ce que io.github.cyanheads/cyanheads-mcp-server est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.cyanheads/cyanheads-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 2 outils

• cyanheads_describe_entry≈ 2218 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • kind · string · optionnel · tool | server
    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 · requis
    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. A tool name that more than one server owns also needs server. Use cyanheads_search_catalog to discover valid names.
  • client · string · optionnel · claude-code | cline | codex | cursor | curl | gemini | streamable-http
    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 servers. Omit to return snippets for all supported clients.
  • server · string · optionnel
    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 owner; with a server name, it must name the same server.

  Exemple d'appel

  {"name": "cyanheads_describe_entry", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "result": "texte"}}

• cyanheads_search_catalog≈ 1731 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • limit · integer · optionnel
    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.
  • query · string · requis
    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 · optionnel · tools | servers
    What to search. "tools" returns individual tool matches; "servers" returns server-level matches.
  • offset · integer · optionnel
    Result offset. Use nextOffset with the same query, scope, category, and limit; pages use the current catalog.
  • category · string · optionnel · research | government | public-data | utility
    Filter by catalog category. Omit to search all categories.
  • serversOffset · integer · optionnel
    Independent server roll-up offset (10 per page). Use nextServersOffset; must be zero in servers scope.

  Exemple d'appel

  {"name": "cyanheads_search_catalog", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "error": {}, "scope": "tools", "shown": 1, "notice": "texte", "offset": 1, "results": [], "servers": [], "truncated": true, "nextOffset": 1, "totalCount": 1, "serversTotal": 1}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://cyanheads.caseyjhand.com/mcp