https://powmcp.com/epub-check/mcp ↗
Run EPUBCheck for EPUB specification errors and compare two exports.
Ebook File Check is a remote MCP server published at powmcp.com. It has been probed 7 times since 9/12/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 408 ms, placing it among the faster endpoints. It offers a narrow, focused set of 2 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
ebook_check — Description truncated mid-sentence, missing critical output details.ebook_compare — Description truncated, no explanation of regression/fixed findings reporting.ebook_check — Parameters 'url' and 'file' are both optional but mutually exclusive; no validation logic implied.Risk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
ebook_checkValidates 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.3.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 th
urlstringfileobjectmaxMessagesintegerebook_compareRuns the identical pinned EPUBCheck 5.3.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
urlsarrayfilesarraymaxMessagesintegerDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/com-powmcp-epub-check)<a href="https://mcpmetrics.io/servers/com-powmcp-epub-check"><img src="https://mcpmetrics.io/badge/com.powmcp/epub-check/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Matroska EBML check, file discarded
ICO magic-byte check, file discarded
AVI RIFF check, file discarded
WebAssembly magic-byte check, file discarded
STL solid/header check, file discarded
WebM EBML check, file discarded
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 04:35:29 | Dual-era | 200 | 357 | 200 | 378 | 2026-07-28 |
| 2026-09-13 01:33:33 | Dual-era | 200 | 369 | 200 | 377 | 2026-07-28 |
| 2026-09-12 23:31:36 | Dual-era | 200 | 420 | 200 | 408 | 2026-07-28 |
| 2026-09-12 21:29:15 | Dual-era | 200 | 476 | 200 | 452 | 2026-07-28 |
| 2026-09-12 19:27:29 | Dual-era | 200 | 400 | 200 | 408 | 2026-07-28 |
| 2026-09-12 17:24:09 | Dual-era | 200 | 428 | 200 | 407 | 2026-07-28 |
| 2026-09-12 15:21:42 | Dual-era | 200 | 426 | 200 | 411 | 2026-07-28 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.