io.github.quantakrypto/pqc-tools

Est-ce que io.github.quantakrypto/pqc-tools est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.quantakrypto/pqc-tools » 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 11 outils

• apply_triage≈ 501 tokens

  Deterministically attach your triage verdicts to their findings and re-sort by exposure (highest first). Never suppresses. Pass the same 'findings' array you triaged plus a 'verdicts' array of { fingerprint, exposureScore, priority, rationale }.

  Paramètres, retour & exemple (2)

  Paramètres

  • findings · array · requis
    The findings that were triaged.
  • verdicts · array · requis
    One verdict per finding, keyed by fingerprint.

  Exemple d'appel

  {"name": "apply_triage", "arguments": {"findings": [], "verdicts": []}}

  Exemple de retour

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

• apply_verified_patch≈ 248 tokens

  Deterministically VERIFY a proposed fix before writing it — runs the same patch-policy + verify_fix + blast-radius gates as `qremediate` (offline, no key, no network). Give the finding, the file's current content, and your proposed FULL corrected content; returns approved:true only if the patch is in-policy, clears the finding, adds no new finding, introduces no network/exec sink, and is bounded in size. This does NOT write the file — you write it, only when approved, and never auto-merge.

  Paramètres, retour & exemple (3)

  Paramètres

  • finding · object · requis
    The scan finding being fixed (needs a string ruleId and location.file).
  • newContent · string · requis
    Your proposed full corrected file content.
  • originalContent · string · requis
    The file's current full content.

  Exemple d'appel

  {"name": "apply_verified_patch", "arguments": {"finding": {}, "newContent": "texte", "originalContent": "texte"}}

  Exemple de retour

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

• check_dependency≈ 130 tokens

  Check whether a package is in quantakrypto's known quantum-vulnerable dependency database (the classical crypto it exposes). Provide 'name' and optional 'ecosystem' (default npm).

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    Package name to look up (e.g. 'node-forge', 'jsonwebtoken').
  • ecosystem · string · optionnel
    Package ecosystem. Default: npm.

  Exemple d'appel

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

  Exemple de retour

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

• explain_finding≈ 162 tokens

  Explain a quantakrypto finding and its post-quantum remediation. Provide a ruleId (e.g. 'forge-rsa-keygen', 'elliptic-ec', 'node-rsa', 'pem-ec-private-key') and/or an algorithm (e.g. 'RSA', 'ECDSA'). The ruleId is resolved against the core detector set, so library and config rules explain correctly.

  Paramètres, retour & exemple (2)

  Paramètres

  • ruleId · string · optionnel
    The finding's rule id, matching a detector id prefix.
  • algorithm · string · optionnel
    The classical algorithm family involved (e.g. RSA, ECDH, ECDSA).

  Exemple d'appel

  {"name": "explain_finding", "arguments": {"ruleId": "texte", "algorithm": "texte"}}

  Exemple de retour

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

• get_fix_examples≈ 127 tokens

  Return before/after code examples for migrating a classical algorithm to a post-quantum / hybrid replacement. Provide an 'algorithm' (RSA, ECDH, ECDSA, …) or a 'ruleId' from a finding.

  Paramètres, retour & exemple (2)

  Paramètres

  • ruleId · string · optionnel
    A finding's ruleId (resolved to its algorithm).
  • algorithm · string · optionnel
    Classical algorithm family to migrate away from.

  Exemple d'appel

  {"name": "get_fix_examples", "arguments": {"ruleId": "texte", "algorithm": "texte"}}

  Exemple de retour

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

• list_rules≈ 51 tokens

  List the quantakrypto detector catalog: every detector id and what it looks for.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_rules", "arguments": {}}

  Exemple de retour

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

• remediate_findings≈ 387 tokens

  Produce a deterministic remediation REQUEST bundle (rubric + fix schema + per-finding metadata + fingerprints) for YOU (the host agent) to fix. This tool calls no model and needs no key. For each finding, propose the corrected FULL file content, then VERIFY with verify_fix and keep only fixes that clear the finding. Never touch files with secrets; never auto-merge. Pass 'findings' from scan_path --format json.

  Paramètres, retour & exemple (1)

  Paramètres

  • findings · array · requis
    Findings from a scan's JSON output.

  Exemple d'appel

  {"name": "remediate_findings", "arguments": {"findings": []}}

  Exemple de retour

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

• score_delta≈ 576 tokens

  Compute the readiness-score and HNDL change between two finding sets (e.g. before and after a migration). Pass 'before' and 'after' as arrays of findings from scan_path --format json.

  Paramètres, retour & exemple (2)

  Paramètres

  • after · array · requis
    Findings after the change.
  • before · array · requis
    Findings before the change (from a scan's JSON findings).

  Exemple d'appel

  {"name": "score_delta", "arguments": {"after": [], "before": []}}

  Exemple de retour

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

• suggest_hybrid≈ 201 tokens

  Recommend a post-quantum / hybrid migration. Provide an 'algorithm' (e.g. RSA, ECDH, ECDSA) or free-text 'context' describing the usage. Set 'tier' to 'category-5' for CNSA 2.0 / national-security systems.

  Paramètres, retour & exemple (3)

  Paramètres

  • tier · string · optionnel · category-3 | category-5
    Security tier: 'category-3' (default, commercial — ML-KEM-768 / ML-DSA-65) or 'category-5' (CNSA 2.0 / NSS, long-lived secrets — ML-KEM-1024 / ML-DSA-87).
  • context · string · optionnel
    Free-text description of the cryptographic usage (used when no algorithm is given).
  • algorithm · string · optionnel
    Classical algorithm family to migrate away from.

  Exemple d'appel

  {"name": "suggest_hybrid", "arguments": {"tier": "category-3", "context": "texte", "algorithm": "texte"}}

  Exemple de retour

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

• triage_findings≈ 367 tokens

  Produce a deterministic triage REQUEST bundle (rubric + verdict schema + per-finding metadata) for YOU (the host agent) to reason over. This tool does NOT call any model and needs no API key. Assess each finding's real-world exposure, then call apply_triage with your verdicts. Pass 'findings' as an array from scan_path --format json.

  Paramètres, retour & exemple (1)

  Paramètres

  • findings · array · requis
    Findings from a scan's JSON output.

  Exemple d'appel

  {"name": "triage_findings", "arguments": {"findings": []}}

  Exemple de retour

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

• verify_fix≈ 178 tokens

  Run the quantakrypto detectors over a code snippet (NOT the filesystem) and report any classical crypto that remains. Use this to confirm an edit actually removed the quantum-vulnerable usage. Provide 'code' plus a 'language' or 'filename'.

  Paramètres, retour & exemple (3)

  Paramètres

  • code · string · requis
    The source code to check.
  • filename · string · optionnel
    Optional filename; its extension selects the detectors (overrides 'language').
  • language · string · optionnel
    Language of the code (js, ts, python, go, java, csharp, rust, ruby, c, …).

  Exemple d'appel

  {"name": "verify_fix", "arguments": {"code": "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.quantakrypto.com/mcp