fyi.clairvoyance/mcp

Est-ce que fyi.clairvoyance/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « fyi.clairvoyance/mcp » 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 17 outils

• abstraction-quality≈ 142 tokens

  Evaluates whether abstractions provide a genuinely different way of thinking or are structurally shallow. Use when adjacent layers feel redundant, wrappers add boilerplate without depth, or an abstraction feels leaky. Not for a single module's interface-to-implementation ratio (use deep-modules) or information leakage across boundaries (use information-hiding).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "abstraction-quality", "arguments": {}}

  Exemple de retour

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

• code-evolution≈ 141 tokens

  Evaluates whether changes to existing code maintain or degrade design quality. Use when the user asks to review a diff or PR (for example before merging it), or asks about recently modified files, to judge whether each change looks designed-in or bolted-on. Not for scanning design smells (use red-flags) or assessing overall design investment (use strategic-mindset).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "code-evolution", "arguments": {}}

  Exemple de retour

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

• comments-docs≈ 127 tokens

  Reviews comment quality and documentation practices: the four comment types, comments-first workflow, and comment rot. Use when reviewing comments or docs, when comments just repeat the code, or when something is hard to describe in a sentence. Not for naming or code obviousness (use naming-obviousness).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "comments-docs", "arguments": {}}

  Exemple de retour

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

• complexity-recognition≈ 130 tokens

  Diagnoses whether complexity exists and where it comes from, using the three-symptom, two-root-cause framework. Use when code feels harder to work with than it should but the specific problem is unclear. Not for scanning known design smells (use red-flags) or evaluating a module's depth (use deep-modules).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "complexity-recognition", "arguments": {}}

  Exemple de retour

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

• deep-modules≈ 140 tokens

  Measures module depth: whether the interface is simple relative to the implementation behind it. Use when an interface has too many parameters or methods, many small classes each do too little, or methods just forward calls. Not for whether adjacent layers provide different abstractions (use abstraction-quality) or merging/splitting modules (use module-boundaries).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "deep-modules", "arguments": {}}

  Exemple de retour

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

• design-it-twice≈ 187 tokens

  Generates and compares at least two fundamentally different design alternatives on concrete criteria before committing. Use when the user asks to design something twice, or before committing to any significant design of classes, modules, APIs, or architecture. Also use when asked how to structure or architect a feature, or when writing the design or alternatives section of an RFC, design doc, or ADR. Not for judging strategic vs. tactical investment in existing code (use strategic-mindset) or whether a change degrades design (use code-evolution).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "design-it-twice", "arguments": {}}

  Exemple de retour

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

• design-review≈ 180 tokens

  Orchestrates a structured design review, running the other skills as a diagnostic funnel from complexity triage to a full red-flags sweep. Use when the user asks for a comprehensive or prioritized design assessment of a file, module, or PR. Not for an open-ended "anything off here?" or "take a look at this" prompt that names no review goal (use red-flags), a plain diff review before merge or analyzing how code changed over time (use code-evolution), or applying one specific lens (use that skill directly).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "design-review", "arguments": {}}

  Exemple de retour

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

• diagnose≈ 112 tokens

  Routes a vague symptom or complaint to the most relevant Clairvoyance skill via a decision tree. Use when someone describes a problem but doesn't know which skill to reach for. Not for a comprehensive review (use design-review) or a checklist scan (use red-flags).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "diagnose", "arguments": {}}

  Exemple de retour

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

• error-design≈ 145 tokens

  Reviews error handling and exception design, applying the "define errors out of existence" principle. Use when reviewing error handling, when a module throws too many exceptions, or when callers must handle errors they shouldn't need to know about. Not for general caller-burden complexity (use pull-complexity-down); this skill is specifically for exception and error-condition strategy.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "error-design", "arguments": {}}

  Exemple de retour

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

• fetch-reference≈ 275 tokens

  Fetch a supporting file from a Clairvoyance skill's references/ folder, when the skill's instructions point to one. Available: information-hiding (back-door-leakage.md); pull-complexity-down (configuration-parameter-audit.md); comments-docs (comments-first-workflow.md); design-it-twice (pre-mortem-fallback.md); red-flags (flag-interaction-map.md); design-review (workflow-builder.md).

  Paramètres, retour & exemple (2)

  Paramètres

  • file · string · requis · back-door-leakage.md | comments-first-workflow.md | configuration-parameter-audit.md | flag-interaction-map.md | pre-mortem-fallback.md | workflow-builder.md
    The file name inside the skill's references/ folder
  • skill · string · requis · information-hiding | pull-complexity-down | comments-docs | design-it-twice | red-flags | design-review
    The skill the file belongs to

  Exemple d'appel

  {"name": "fetch-reference", "arguments": {"file": "back-door-leakage.md", "skill": "information-hiding"}}

  Exemple de retour

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

• general-vs-special≈ 140 tokens

  Evaluates whether interfaces are appropriately general-purpose. Use when checking interface generality, when if-branches or parameters serve only one caller, or when getters/setters expose internal representation. Not for information leakage across boundaries (use information-hiding) or auditing configuration parameters (use pull-complexity-down).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "general-vs-special", "arguments": {}}

  Exemple de retour

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

• information-hiding≈ 148 tokens

  Checks for information leakage across module boundaries, including temporal decomposition and false encapsulation. Use when modules change together, implementation details leak across boundaries, or structure follows execution order rather than knowledge ownership. Not for merge/split decisions (use module-boundaries) or interfaces over-specialized for one caller (use general-vs-special).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "information-hiding", "arguments": {}}

  Exemple de retour

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

• module-boundaries≈ 138 tokens

  Evaluates where module boundaries are drawn and whether modules should be merged or split. Use when deciding whether to combine or separate two modules, when modules are tightly coupled, or when a change to one forces changes to another. Not for depth within a single module (use deep-modules) or abstraction-layer quality (use abstraction-quality).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "module-boundaries", "arguments": {}}

  Exemple de retour

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

• naming-obviousness≈ 130 tokens

  Reviews naming quality and code obviousness via the isolation test, scope-length principle, and consistency audit. Use when names feel vague, something is hard to name (a design signal, not a vocabulary problem), or behavior isn't obvious on first read. Not for comment quality or documentation (use comments-docs).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "naming-obviousness", "arguments": {}}

  Exemple de retour

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

• pull-complexity-down≈ 151 tokens

  Checks whether complexity is pushed to callers or absorbed by implementations — the direction complexity flows. Use when callers must do significant setup, handle errors the module could resolve, or configure things they don't understand. Not for module depth (use deep-modules), knowledge leakage (use information-hiding), or exception strategy once an error must surface (use error-design).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "pull-complexity-down", "arguments": {}}

  Exemple de retour

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

• red-flags≈ 215 tokens

  Scans code against 17 design smells (the book's 14 named Red Flags plus 3 process-stage signals) and produces a structured diagnostic report. Use when the user asks for a red flags or design smell scan, asks to check code against a checklist, is evaluating unfamiliar code, or asks open-endedly whether anything is off in a named or pasted file, class, or function, or asks you to look it over. Not for a specific bug, error, or failing test the user has already identified. Not for a plain diff or PR review before merge, or whether a PR maintains design trajectory (use code-evolution for both), or diagnosing why code feels complex (use complexity-recognition).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "red-flags", "arguments": {}}

  Exemple de retour

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

• strategic-mindset≈ 140 tokens

  Assesses whether code reflects strategic or tactical thinking, including the 10-20% investment rule and tactical-tornado patterns. Use when evaluating design investment, when code was written under time pressure, or when working code consistently degrades the system. Not for judging whether a specific diff looks designed-in or bolted-on (use code-evolution).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "strategic-mindset", "arguments": {}}

  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://clairvoyance.fyi/mcp