TUUI

A desktop MCP client designed as a tool unitary utility integration, accelerating AI adoption through the Model Context

Protocols & Tool Integration TypeScript Grade D Listed Apache-2.0
17.4/100
Rank #1178 of 1283
Compare TUUI

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-05-14 · 90d ago
Recent change
Stale +1

Is TUUI safe? TUUI scores 17.4/100 (Grade D), ranked #1178 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 1% of recent commits are signed; last pushed 2026-05-14. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-12
Activity Went Stale
No commits for 90 days
2026-08-10
Newly Listed
First tracked at rank #1175
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 90 days ago. Fresh activity helps separate stable projects from stale ones.
40.5
Activity sub-score · out of 100
#54

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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 90 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
1.2k
Forks
107
Last Push
2026-05-14
90 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
1
Rank Change
▼1
was #1177

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

17.4 / 100 · 50.0% confidence

TUUI Protocols & Tool Integration average (57 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.1 / 25
8.5 below avg 8.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
2.9 below avg 11.4
Maintenance60% last-push freshness · 40% commit activity
6.0 / 20
7.8 below avg 13.8
AdoptionLog-scaled stars · package downloads
7.3 / 20
3.1 below avg 10.4

Activity Inputs

40.5 / 100
StarsRepository reach
18.4 / 30
FreshnessLast push recency
12.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
Not available
Signed Commits
1%
of last 100 commits verified

Is TUUI safe?

Public trust evidence for TUUI is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does TUUI publish package provenance?
No published build provenance is currently detected for TUUI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does TUUI have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for TUUI. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is TUUI actively maintained?
Slowing down. Last push was 90 days ago — keep an eye on whether activity resumes.
What license does TUUI use?
TUUI ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are TUUI's commits signed?
1% of the last 100 commits to TUUI are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
high confidence
Implemented
TUUI appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
  • browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

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.

2026-08-12
Activity Went Stale
No commits for 90 days

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
Listed 1Stale 1
2026-08-12
Activity Went Stale
No commits for 90 days
2026-08-10
Newly Listed
First tracked at rank #1175

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 17.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/tuui.svg)](https://hvtracker.net/agents/tuui)
HTML:
<a href="https://hvtracker.net/agents/tuui"><img src="https://hvtracker.net/badge/tuui.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON