markitdown-mcp: why it is not safe to use

What we found

Our review of `trsdn/markitdown-mcp` did not identify findings that would prevent approval. In the inspected repository, we found no hidden or disguised agent-targeting instructions, no hardcoded credentials, and no obfuscated or intentionally concealed code. The server logic appeared to process files locally and return markdown over MCP, with no evidence of sending file contents to undisclosed third parties.

We also did not find delete-style or irreversible send actions exposed by the server. File writes appeared limited to temporary-file handling needed for conversion, with cleanup afterward. We found no runtime remote code fetch or execution in the server logic. Installation materials do reference pulling packages from named sources during setup, which is consistent with ordinary installation behavior rather than undisclosed runtime fetching. We also found no evidence of keychain, browser, SSH key, or unrelated credential access, and no signs of sudo use, permission changes, or sandbox escape behavior.

What to do instead

This skill passed our security and privacy review based on the inspected repo. As with any third-party tool, use normal caution: review requested file access, install from expected sources, and test with non-sensitive data first if your environment requires it.