Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Walmes1/convertisseur-ia

NPM · CONVERTISSEUR-IA-MCP · SCANNED SEP 20

Documents (PDF, Word, Excel, PowerPoint, CSV) vers Markdown leger pour l'IA, 100 % local

+6 this week 74 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 13 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 640 tokens (~128/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.github.Walmes1/convertisseur-ia MCP server?

io.github.Walmes1/convertisseur-ia runs locally as an npm package, launched with npx -y convertisseur-ia-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · convertisseur-ia-mcp

# add to Claude Code
claude mcp add walmes1-convertisseur-ia -- npx -y convertisseur-ia-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "walmes1-convertisseur-ia": {
      "command": "npx",
      "args": [
        "-y",
        "convertisseur-ia-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "walmes1-convertisseur-ia": {
      "command": "npx",
      "args": [
        "-y",
        "convertisseur-ia-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add walmes1-convertisseur-ia -- npx -y convertisseur-ia-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "walmes1-convertisseur-ia": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "convertisseur-ia-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add walmes1-convertisseur-ia --command npx --arg -y --arg convertisseur-ia-mcp
# ~/.hermes/config.yaml
mcp_servers:
  walmes1-convertisseur-ia:
    command: "npx"
    args: ["-y", "convertisseur-ia-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "walmes1-convertisseur-ia": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "convertisseur-ia-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add walmes1-convertisseur-ia -t stdio -c npx -a -y convertisseur-ia-mcp
// mcp.json
{
  "mcpServers": {
    "walmes1-convertisseur-ia": {
      "command": "npx",
      "args": [
        "-y",
        "convertisseur-ia-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +4
    • Stability: unverified → 0.27 functional
  • 8 Sept 26 +15
    • Malware scan: unverified → pass security
  • 7 Sept 26 53

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/convertisseur-ia-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 13 packages
Packages resolved 13
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~528 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
apercu_document ~81

Aperçu bon marché d'un document : type, taille, nombre de tokens estimé avant/après conversion et les premiers caractères. Sert à décider s'il faut tout convertir ou seulement quelques pages.

NameTypeReqDescription
charsnumberNombre de caractères d'aperçu (défaut 1500)
cheminstringyesChemin complet du fichier

No output schema declared.

No examples provided.

convertir_document ~175

Convertit UN document local (PDF, Word, Excel, PowerPoint, CSV, HTML, JSON, RTF, TXT, code…) en Markdown léger, prêt à lire par l'IA, et affiche l'économie de tokens. À utiliser AVANT de lire un document lourd. Si le PDF est un scan, l'outil le dit et renvoie vers le connecteur OCR.

NameTypeReqDescription
cheminstringyesChemin complet du fichier, ex. C:\Users\lidom\Desktop\facture.pdf
max_charsnumberLongueur maximale du Markdown renvoyé (défaut 120000, 0 = illimité)
page_debutnumberPDF uniquement : première page à extraire
page_finnumberPDF uniquement : dernière page à extraire

No output schema declared.

No examples provided.

convertir_dossier ~161

Convertit TOUS les documents d'un dossier en un seul Markdown (avec un titre par fichier). Idéal pour donner un dossier entier à l'IA sans exploser les tokens.

NameTypeReqDescription
dossierstringyesChemin du dossier, ex. C:\Users\lidom\Desktop\Declarations
filtrestringFiltre simple sur le nom, ex. "2026" ou ".pdf" (optionnel)
max_chars_par_fichiernumberCoupe chaque fichier à N caractères (défaut 20000)
max_fichiersnumberNombre maximum de fichiers (défaut 25)
recursifbooleanInclure les sous-dossiers (défaut false)

No output schema declared.

No examples provided.

enregistrer_markdown ~82

Convertit un document et enregistre le résultat en fichier .md sur le disque (par défaut à côté du fichier d'origine). Utile pour garder une version légère réutilisable.

NameTypeReqDescription
cheminstringyesChemin complet du fichier à convertir
dossier_sortiestringDossier de destination (défaut : celui du fichier)

No output schema declared.

No examples provided.

formats_supportes ~29

Liste les formats que ce connecteur sait convertir et rappelle quoi faire pour les scans et les images.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.Walmes1/convertisseur-ia MCP server?

io.github.Walmes1/convertisseur-ia is an MCP server listed in the public MCP registry as io.github.Walmes1/convertisseur-ia. Documents (PDF, Word, Excel, PowerPoint, CSV) vers Markdown leger pour l'IA, 100 % local. This page covers its npm package (convertisseur-ia-mcp).

Is the io.github.Walmes1/convertisseur-ia MCP server safe to use?

io.github.Walmes1/convertisseur-ia scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Walmes1/convertisseur-ia MCP server expose?

io.github.Walmes1/convertisseur-ia exposes 5 tools: convertir_document, apercu_document, convertir_dossier, enregistrer_markdown, formats_supportes. Their descriptions and schemas cost roughly 528 tokens of context every time the server is loaded.

Is the io.github.Walmes1/convertisseur-ia MCP server still maintained?

io.github.Walmes1/convertisseur-ia is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Walmes1/convertisseur-ia MCP server under?

io.github.Walmes1/convertisseur-ia declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.