com.headlesson/catalog

Est-ce que com.headlesson/catalog est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.headlesson/catalog » 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 4 outils

• headlesson_feedback≈ 386 tokens

  This content is sent to the headlesson operator. Feedback about headlesson itself is sufficient. Do not include personal information or conversation contents.

  Paramètres, retour & exemple (5)

  Paramètres

  • kind · string · optionnel · comment | worked | failed | missing | tip
    Report type: comment, worked, failed, missing or tip; receipt does not verify the claim.
  • text · string · requis
    Feedback to the headlesson operator, 1–2000 Unicode characters; exclude personal information and conversation text.
  • about · string · optionnel
    Optional record ID that the feedback concerns; feedback about headlesson itself needs no product ID.
  • model · string · optionnel
    Optional model name associated with the report, without conversation content.
  • client · string · optionnel
    Optional client name only; do not include full User-Agent, account IDs or credentials.

  Exemple d'appel

  {"name": "headlesson_feedback", "arguments": {"text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• headlesson_get≈ 408 tokens

  Get one record by an ID from headlesson_search: an app, usecase, feature, concept or change. For an app, sections ["lesson","gotchas"] return the install, check and first-task steps with the recorded test result (a dated observation by the headlesson operator) and known failure conditions; "relations" lists alternatives and what it wraps or depends on; "axes" returns every compared fact. Without sections you get the description, interfaces and six main axes. Each fact carries its source and check date; private sources appear as labels, not links. Official MCP Registry listing IDs are fetched live and are unverified; a failed lookup does not prove the ID absent.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · string · requis
    Record ID or the special axes/search-guide ID; missing records return nearby ID suggestions.
  • sections · array · optionnel
    App sections to return in text and structuredContent; omitted means description, interfaces and six major axes.

  Exemple d'appel

  {"name": "headlesson_get", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• headlesson_search≈ 976 tokens

  Find command-line tools, MCP servers and APIs for a task, and compare them. Ask in plain English or Japanese ("extract text from scanned PDFs") or by product name. Each result gives an ID, a one-line reason it matches, and when it was checked. Pass the ID to headlesson_get with sections ["lesson","gotchas"] to get the steps (install, check, first task) with their recorded test result (most were run by an agent; a few are untested) and known failure conditions, such as a tool that exits 0 with empty or wrong output. Filter or compare with axes such as auth, pricing, license and remote_mcp (where, axes, ids). Curated records come first. If none match, or include:["registry"] is set, one public word from the query is looked up in the Official MCP Registry; those listings are unverified (what is sent is described on the query field).

  Paramètres, retour & exemple (7)

  Paramètres

  • ids · array · optionnel
    Up to 20 explicit app IDs to compare; any missing ID produces an error instead of being silently omitted.
  • axes · array · optionnel
    Axes to compare: auth, pricing, license, cli, local_mcp, remote_mcp are useful starting points; licence is normalized to license.
  • sort · object · optionnel
    Optional axis ordering before relevance; unknown values remain last.
  • limit · integer · optionnel
    Maximum app results, from 1 to 20; default is 5.
  • query · string · optionnel
    Task or product name in English or Japanese. External Registry lookup sends only one ASCII public name fragment (longest significant ASCII word from free text, or a supplied namespace; max 200 chars) when curated matches are absent or include registry is requested; the full free text is not sent. Recognized credential/URL/PII patterns are skipped; this is not a complete secret filter. Do not include secrets.
  • where · object · optionnel
    Confirmed axis filters: AND across axes, OR inside a value array; known spelling aliases are normalized.
  • include · array · optionnel
    Explicitly request the supplemental Official Registry name lookup alongside curated results. Otherwise it is attempted only when curated matches are absent. At most five unverified listings; one-page comparison only.

  Exemple d'appel

  {"name": "headlesson_search", "arguments": {"ids": [], "axes": [], "sort": {}, "limit": 1, "query": "texte", "where": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• headlesson_whats_new≈ 412 tokens

  List dated changes in agent tools and standards (new tools, renames, deprecations, breaking changes, new standards) since a date, optionally by kind or affected record. Useful for checking what changed after your training data. Public source URLs are kept; private sources appear as labels.

  Paramètres, retour & exemple (4)

  Paramètres

  • about · string · optionnel
    Affected record ID to filter changes, such as an app or protocol.
  • kinds · array · optionnel
    Change kinds to include; the array is an OR-list.
  • limit · integer · optionnel
    Maximum changes, from 1 to 100; default is 20.
  • since · string · optionnel
    Inclusive event-date lower bound in YYYY-MM-DD; omitted uses the previous 90 days, not source confirmation dates.

  Exemple d'appel

  {"name": "headlesson_whats_new", "arguments": {"about": "texte", "kinds": [], "limit": 1, "since": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

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