ToolsMCP
emperor-pdf
Listed in the official MCP Registry with an installable cargo package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- yarenty (GitHub)
- Prerequisites
- Install emperor-pdf from cargo (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.1.3 · updated
- Official links
Publisher’s description
Read, search and render the PDFs in one folder; merge, extract and create them from Markdown.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.3, registry status active. 1 package (cargo)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- yarenty (GitHub)
- Version observed
- 0.1.3
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.yarenty%2Femperor-pdf/versions/0.1.3
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Extract structured data from PDFs | Publisher description mentions “pdf”, “pdfs”, “extract”. | No connection check or task run. Capability is as described by the publisher. | Rule pdf-extraction matched: “pdf”, “pdfs”, “extract”. Rule pdf-extraction. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
emperor-pdf(cargo, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.yarenty/emperor-pdf
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.