TUUI
A desktop MCP client designed as a tool unitary utility integration, accelerating AI adoption through the Model Context Protocol (MCP) and enabling cross-vendor LLM API orchestration.
Is TUUI safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare TUUI
How does it stack up against its Protocols & Tool Integration neighbours?
Pick any agent to compare →In detail: TUUI scores 36.8/100 (Grade D), ranked #1216 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 2.6/10; 1% of recent commits are signed; last pushed 2026-05-14. Every point is earned from checkable signals — never paid placement. How scoring works →
How TUUI compares in Protocols & Tool Integration
- #56 MCP-Bridge 39.8 +3.0
- #57 MCP Playwright 36.9 +0.1
- #58 TUUI 36.8 this agent
- #59 MCP Hub for Neovim 36.1 −0.7
- #60 Scira MCP Chat 30.7 −6.1
Bars show each HVTrust score; the tick marks TUUI’s 36.8.
Where the 36.8 comes from
HVTrust dimensions vs the Protocols & Tool Integration average
36.8 / 100 · 100.0% confidenceTUUI Protocols & Tool Integration average (61 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 D 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
34.3 / 100Supply Chain Trust
Common questions about TUUI
Does TUUI publish package provenance?
Does TUUI have an OpenSSF Scorecard?
Is TUUI actively maintained?
What license does TUUI use?
Are TUUI'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 TUUI'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 TUUI?
For maintainers
HVTrust scores TUUI 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/tuui)
<a href="https://hvtracker.net/agents/tuui"><img src="https://hvtracker.net/badge/tuui.svg" alt="HVTrust"></a>
Other agents in Protocols & Tool Integration
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