ezmd
PYPI · EZMD-MCP
Convert files, URLs and text to LLM-ready Markdown with paging, provenance and warnings.
Available components
Last scanned (1 day ago)
Scores higher than 89% of PyPI servers
Category Documents and Files
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 Security99
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 88 of 89 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 88 of 89 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to larpey/ezmd). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 11 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 571 tokens (~114/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
- Package version: 0.1.0 → 0.1.1 functional
- 21 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
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 4 Nov 2026 · Analysed pypi/ezmd-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | larpey/ezmd |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/larpey/ezmd/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 3421442830 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:0a39d5bc6f7c456a01b660c54cde80e03e5051634574cb8e917b28280d78b4e9 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 88 packages
| Packages resolved | 88 |
|---|---|
| Stale | 14 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
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 →
convert_file ~126
Convert a local file (PDF, DOCX, PPTX, XLSX, HTML, CSV, images, audio, ...) to Markdown. path must be absolute and inside the server's allowed directories. Clients without a filesystem may instead pass data_url (a base64 data: URL under 1 MB). Returns page 1, sections, warnings and next_cursor. options: as for convert_url (output options; limits may only be lowered).
| Name | Type | Req | Description |
|---|---|---|---|
| data_url | – | – | – |
| max_tokens | – | – | – |
| options | – | – | – |
| path | – | – | – |
| profile | – | – | – |
No output schema declared.
No examples provided.
convert_text ~77
Convert pasted text, HTML, CSV, JSON, Markdown or any string to clean Markdown. source_hint is a MIME type or extension ("text/html", "csv") used to break ties; detection runs on the content.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | – | – | – |
| profile | – | – | – |
| source_hint | – | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
convert_url ~150
Convert a web page or document URL (http/https) to Markdown. Returns page 1 of the result (at most max_tokens, default 8000, max 50000), the section list, warnings, and next_cursor for get_job. profile: full | compact | rag | agent (default agent). options: output options such as {"ocr": false, "languages": ["en"], "max_pages": 50}; limits (max_pages, max_bytes, max_seconds, max_duration_seconds) may only be lowered, and extra, converter and experimental are refused.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | – | – | – |
| options | – | – | – |
| profile | – | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
get_job ~83
Return a job's status while it runs, otherwise the page at cursor (or page 1). This is the pagination endpoint for all convert tools: pass the previous result's next_cursor unchanged. A cursor is bound to its job and profile.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| job_id | string | yes | – |
| max_tokens | – | – | – |
| profile | – | – | – |
No output schema declared.
No examples provided.
list_capabilities ~54
Supported input types and converters (with the extra each needs when not installed), profiles, limits, and whether URL fetching is allowed. Call it to decide whether to try an input or ask the user to upload it instead.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the ezmd MCP server?
ezmd runs locally as a PyPI package, launched with uvx ezmd-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · ezmd-mcp
claude mcp add larpey-ezmd -- uvx ezmd-mcp
What is the ezmd MCP server?
ezmd is an MCP server listed in the public MCP registry as io.github.larpey/ezmd. Convert files, URLs and text to LLM-ready Markdown with paging, provenance and warnings. This page covers its PyPI package (ezmd-mcp).
Is the ezmd MCP server safe to use?
ezmd scores 86 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 ezmd MCP server expose?
ezmd exposes 5 tools: convert_url, convert_file, convert_text, get_job, list_capabilities. Their descriptions and schemas cost roughly 490 tokens of context every time the server is loaded.
Is the ezmd MCP server still maintained?
ezmd is still listed as active in the MCP registry. We last reached this channel on 4 November 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 ezmd MCP server under?
ezmd declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.