Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Microsoft MarkItDown MCPShortlist candidate | Exa MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Microsoft · Publisher source ↗ | First-party MCP Exa · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Sep 23, 2026 Package: Sep 21, 2026 |
| Popularity evidence | ||
| GitHub stars | Not documented | 5,045 GitHub stars · checked 2026-09-24T04:14:16.246000Z |
| Package downloads / 30 days | 90,012 package downloads / 30 days · checked 2026-10-20 | 248,026 package downloads / 30 days · checked 2026-09-24T04:17:39.104000Z |
| Shared repository stars | 191,307 Shared repository stars (not MCP-specific) · checked 2026-10-20 | Not documented |
| External adoption evidence | Not documented |
|
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | No authentication is supported by the MCP server. | Authentication follows the publisher's documented endpoint or local-server configuration. OAuth scopes, API-key handling, and revocation behavior remain review items. |
| Cost | No separate MCP fee is documented for the open-source package. | No MCP100 cost conclusion is published yet. The publisher's account plan, API usage, infrastructure, or per-action charges may apply. |
| Permissions | The process runs with the privileges of the local user and `convert_to_markdown` can read any file that user can access plus HTTP/HTTPS/data URIs. | Exact permissions and the read/write boundary have not yet completed MCP100 independent review; consult the linked publisher sources and use the narrowest available scope. |
| Data handling | Conversion runs in the local server process. Local files or remote URLs selected by the caller are read and converted to Markdown. | Publisher-accessible account or application data may be returned to the MCP client and its selected model. Retention and subprocess behavior require candidate-specific review. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | The tool is a powerful local file/network reader. Exposing HTTP/SSE beyond localhost can give other network users access to files and network resources available to the server account. | Use a test workspace or non-production account, least privilege, read-only controls where available, explicit approval for mutations, and credential revocation after evaluation. |
| Evidence date | ||
| Editorial review | 2026-10-19 | 2026-07-24 |
| Candidate evidence | 2026-10-20 | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →