MCP File Tools
MCP server for file operations on non-UTF-8 text: detects the encoding from the bytes, hands the model UTF-8, and writes back in the original encoding with BOM and CRLF/LF intact. 24 encodings — Cyrillic/CP1251, CP1252, KOI8, ISO-8859, UTF-16, GBK/GB18030.
Is MCP File Tools safe? Promising trust profile, but some evidence still deserves review.
Compare MCP File Tools
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: MCP File Tools scores 57.8/100 (Grade C), ranked #691 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 8.0/10; 6% of recent commits are signed; last pushed 2026-09-19. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP File Tools compares in MCP Servers
- #381 Agent Search MCP 58.0 +0.2
- #382 webclaw 57.9 +0.1
- #383 MCP File Tools 57.8 this agent
- #384 MCP For Stata 57.8 ±0
- #385 Rust MCP Sdk 57.7 −0.1
Bars show each HVTrust score; the tick marks MCP File Tools’s 57.8.
Where the 57.8 comes from
HVTrust dimensions vs the MCP Servers average
57.8 / 100 · 100.0% confidenceMCP File Tools MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
52.4 / 100Supply Chain Trust
Common questions about MCP File Tools
Does MCP File Tools publish package provenance?
Does MCP File Tools have an OpenSSF Scorecard?
Is MCP File Tools actively maintained?
What license does MCP File Tools use?
Are MCP File Tools's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to MCP File Tools's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain MCP File Tools?
For maintainers
HVTrust scores MCP File Tools from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcp-file-tools)
<a href="https://hvtracker.net/agents/mcp-file-tools"><img src="https://hvtracker.net/badge/mcp-file-tools.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON