com.powmcp/epub-check

Est-ce que com.powmcp/epub-check est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.powmcp/epub-check » 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

• ebook_check≈ 2486 tokens

  Validates one EPUB (a directly hosted public URL or a file attached in chat) against the EPUB 2/3 specification using a pinned local EPUBCheck 5.4.0 engine run in a no-network sandbox. Each call takes exactly one source: the url parameter or the file attachment, never both. Returns the automated verdict: pass boolean, EPUB version, message counts by severity (fatal/error/warning/usage), findings grouped most-severe-first with EPUBCheck rule id (RSC-005, OPF-014, …), file path and line/column, plus a structural inventory (spine items, media types, remote-resource state), SHA-256 of the exact bytes, and truncation metadata. Use for one-file readiness and diagnosis: 'is this ebook valid', 'does this EPUB have specification problems before upload', 'what is wrong with it'. A pass means only that the bytes satisfied the automated profile; it never renders the book, judges accessibility, or guarantees any store will accept it, and human review of how the book reads and looks is always required. Downloads and validates a live EPUB under a 110-second call deadline; tell the user before the call.

  Paramètres, retour & exemple (3)

  Paramètres

  • url · string · optionnel
    Direct public HTTP(S) URL to the EPUB file bytes, including the protocol, not a ChatGPT file id, local path, cloud-drive share, archive/viewer page, or authenticated URL needing a login. Each call takes either URL sources or attached-file sources, never both STRICT RULE: Ebook check failed: provide either an EPUB URL or an attached EPUB file, not both STRICT RULE: Ebook check failed: provide a public EPUB URL or attach the EPUB file
  • file · object · optionnel
    An EPUB file attached in chat, up to 25 MB, validated from its exact bytes. Provide either this attachment or url, never both.
  • maxMessages · integer · optionnel
    Maximum spec findings to return, most severe first (default 200); raise it to see more of a very noisy book, lower it to keep the answer short

  Exemple d'appel

  {"name": "ebook_check", "arguments": {"url": "texte", "file": {}, "maxMessages": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"pass": true, "bytes": 1, "counts": {}, "sha256": "texte", "finalUrl": "texte", "findings": [], "fetchedAt": "texte", "inventory": {}, "nonclaims": [], "redirects": 1, "truncation": {}, "contentType": "texte"}}

• ebook_compare≈ 2127 tokens

  Runs the identical pinned EPUBCheck 5.4.0 validation over exactly two EPUB builds (directly hosted public URLs or files attached in chat, baseline first, revised second) sequentially under one shared 110-second deadline, then reports which spec findings regressed or were fixed between them. Returns per-build hashes, EPUB versions, pass verdicts and severity counts, a regressions list (rules that appear or worsen in the revised build) and a fixed list (rules removed or reduced), and a ranking by pass state then fewer blocking findings. Use for 'did my re-export get worse', 'which build has fewer problems', and revision-over-revision questions. The ranking orders automated conformance only (it never means one build renders, reads, or sells better), and when both builds tie on pass state and blocking count it names no winner rather than crowning the first submission. It also flags when the two files declare different titles, since that usually means they are not two builds of one book. Human review remains required for both builds. A comparison can take up to 110 seconds under its shared deadline; tell the user before the call.

  Paramètres, retour & exemple (3)

  Paramètres

  • urls · array · optionnel
    Exactly two distinct direct public HTTP(S) EPUB URLs: the baseline build first, the revised build second. Provide either these URLs or files, never both. STRICT RULE: Ebook compare failed: provide either two EPUB URLs or two attached EPUB files, not both STRICT RULE: Ebook compare failed: provide two public EPUB URLs or attach two EPUB build files
  • files · array · optionnel
    Exactly two distinct EPUB builds attached in chat: the baseline build first, the revised build second. Provide either these attachments or urls, never both.
  • maxMessages · integer · optionnel
    Maximum findings to collect per build for the comparison (default 150)

  Exemple d'appel

  {"name": "ebook_compare", "arguments": {"urls": [], "files": [], "maxMessages": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"fixed": [], "limits": [], "ranking": [], "documents": [], "nonclaims": [], "truncated": true, "comparedAt": "texte", "regressions": [], "processingMs": 1, "engineVersion": "texte", "ruleProfileDate": "texte", "humanReviewItems": []}}

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://powmcp.com/epub-check/mcp