Is MCP Trino safe to use?

MCP Trino has an HVTrust score of 45.6/100 (Grade D), ranked #1046 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Trino?

MCP Trino scores 45.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 121 GitHub stars and is categorized under MCP Servers.

MCP Trino

tuannvm/mcp-trino

A high-performance Model Context Protocol (MCP) server for Trino implemented in Go.

MCP Servers Go Listed MIT

Is MCP Trino safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.4 / 10

Provenance None

Signed commits 83%

Last push 87d ago

Compare MCP Trino

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Trino scores 45.6/100 (Grade D), ranked #1046 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 4.4/10; 83% of recent commits are signed; last pushed 2026-07-01. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Trino compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP Trino’s 45.6.

Where the 45.6 comes from

HVTrust dimensions vs the MCP Servers average

45.6 / 100 · 100.0% confidence

MCP Trino MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

9.7 / 25

0.6 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

6.2 / 20

5.9 below avg 12.1

AdoptionLog-scaled stars · package downloads

5.0 / 20

2.2 below avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.4/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Refresh maintenance signals The repo was last pushed 87 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for MCP Trino View MCP Servers Report missing data

33.6

Activity sub-score · out of 100

#612

In MCP Servers

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

2026-08-11 2026-09-26

Activity & Reach

Stars

121

Forks

Last Push

2026-07-01

87 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1045

Analysis

Activity Inputs

33.6 / 100

StarsRepository reach

12.5 / 30

FreshnessLast push recency

12.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

8.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.4 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

83%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 9

CII-Best-Practices 0

Code-Review 2

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 9

Security-Policy 4

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about MCP Trino

Public trust evidence for MCP Trino 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 MCP Trino publish package provenance?

No published build provenance is currently detected for MCP Trino. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Trino have an OpenSSF Scorecard?

MCP Trino has an OpenSSF Scorecard score of 4.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is MCP Trino actively maintained?

Slowing down. Last push was 87 days ago — keep an eye on whether activity resumes.

What license does MCP Trino use?

MCP Trino ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Trino's commits signed?

83% of the last 100 commits to MCP Trino 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

MCP Trino appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

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 MCP Trino'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-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain MCP Trino?

For maintainers

HVTrust scores MCP Trino 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 367 spots (#668 → #1035)

2026-09-23

HVTrust Changed

HVTrust up 14.3pts (31.5 → 45.8)

2026-09-22

Newly Listed

First tracked at rank #668

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 15 spots (#1000 → #1015)

2026-09-11

Rank Moved

Rank dropped 12 spots (#988 → #1000)

2026-09-09

Rank Moved

Rank dropped 14 spots (#977 → #991)

2026-09-08

Rank Moved

Rank dropped 14 spots (#963 → #977)

2026-09-07

Rank Moved

Rank dropped 34 spots (#929 → #963)

2026-09-06

Rank Moved

Rank dropped 14 spots (#915 → #929)

2026-09-05

Rank Moved

Rank dropped 54 spots (#861 → #915)

2026-09-04

Rank Moved

Rank dropped 30 spots (#831 → #861)

2026-09-03

Rank Moved

Rank dropped 49 spots (#782 → #831)

2026-09-02

Rank Moved

Rank dropped 45 spots (#737 → #782)

2026-09-01

Rank Moved

Rank dropped 29 spots (#708 → #737)

2026-08-31

Rank Moved

Rank dropped 36 spots (#672 → #708)

2026-08-30

Rank Moved

Rank dropped 23 spots (#649 → #672)

2026-08-29

Rank Moved

Rank dropped 41 spots (#608 → #649)

2026-08-28

Scorecard Added

OSSF Scorecard: 4.4/10

2026-08-28

Rank Moved

Rank rose 536 spots (#1144 → #608)

2026-08-28

HVTrust Changed

HVTrust up 27.4pts (20.1 → 47.5)

2026-08-27

Rank Moved

Rank dropped 13 spots (#1131 → #1144)

2026-08-26

Rank Moved

Rank dropped 56 spots (#1075 → #1131)

2026-08-24

Rank Moved

Rank dropped 16 spots (#1060 → #1076)

2026-08-17

Rank Moved

Rank rose 14 spots (#1070 → #1056)

2026-08-16

Rank Moved

Rank dropped 39 spots (#1031 → #1070)

2026-08-12

Rank Moved

Rank rose 16 spots (#1038 → #1022)

2026-08-10

Rank Moved

Rank dropped 56 spots (#977 → #1033)

2026-08-08

Newly Listed

First tracked at rank #967

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-trino.svg)](https://hvtracker.net/agents/mcp-trino)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-trino"><img src="https://hvtracker.net/badge/mcp-trino.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
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