Single conversion tool discovered
The server exposed exactly one tool, convert_to_markdown, taking a uri argument.
evidence/trust5/2026-06-13-mcp-pilot.json
MCP serverPublished
MarkItDown MCP Server
Microsoft's MarkItDown MCP server passed a real MCP smoke test: it converted a local HTML fixture into clean markdown. The score is good for a focused conversion tool, with caution because it accepts file and http URIs, giving it local-file-read and network-egress reach that the client must constrain.
Independent trust badge
The visible trust mark for this verdict.
Badge clicks resolve to this canonical verdict so the score, test date, evidence, limitations, and reply status remain attached.
Embed
Show this badge on your site
[](https://silentcritique.com/verdicts/mcp-markitdown)Markdown works in GitHub READMEs. The badge always links back to this verdict.
Editorial notice
This page reflects SilentCritique's independent editorial opinion based on the specific test evidence shown. It is not an allegation of unlawful, malicious, fraudulent, or bad-faith conduct. SilentCritique does not accept payment to remove criticism, change a score, suppress a verdict, or improve an outcome.
Claim tested
Can the public MarkItDown MCP server convert a document referenced by URI into markdown over MCP?
Evaluator panel
Protocol harnessSafety reviewerOperator skeptic
Evidence reviewed
HTML converted to clean markdown
Converting the fixture returned "# SilentCritique Trust 5\n\nMarkItDown fixture." with the heading and paragraph preserved.
evidence/trust5/2026-06-13-mcp-pilot.json
File URI scheme accepted
The tool accepted a file:// URI; its documentation also lists http:, https:, and data: schemes.
evidence/trust5/2026-06-13-mcp-pilot.json
Test setup
- Wrote a small HTML fixture to a temporary directory.
- Started markitdown-mcp via uvx over MCP stdio and called convert_to_markdown on the file URI.
- Stored the full tool-call evidence in evidence/trust5/2026-06-13-mcp-pilot.json.
Strengths
- Conversion preserved document structure cleanly in the smoke test.
- The single-tool surface is simple to integrate and reason about.
- Output was compact, model-friendly markdown.
Failure modes
- Accepting file: URIs means a permissive client could have it read arbitrary local files.
- Accepting http(s) URIs gives it network egress, an SSRF surface similar to a fetch tool.
- The test exercised only HTML; other formats may convert with varying fidelity.
What would improve the score
- Let clients restrict which URI schemes are permitted.
- Document recommended sandboxing for local-file conversion.
- Publish fidelity expectations across the supported input formats.
Limitations
- This was an unsolicited smoke test of the public package, not a full security audit.
- Only a single local HTML file on macOS was tested.
- The test did not probe large files, binary formats, or remote URIs.
Visible dissent
- The protocol harness scored this well because the conversion was accurate and well-formed.
- The safety reviewer withheld points because file and http URI support gives one tool both local-read and egress reach.
Right of reply
No vendor reply has been requested or published as of 2026-06-13. SilentCritique will publish factual corrections or a right of reply through the corrections process.
Methodology matters
Scores are only meaningful when the rubric, date, evidence, and dissent are visible.
Read methodology