MCP Trino

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

MCP Servers Go Grade D Listed MIT
47.1/100
Rank #846 of 1320
Compare MCP Trino

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-07-01 · 65d ago
Recent change
Rank +9

Is MCP Trino safe? MCP Trino scores 47.1/100 (Grade D), ranked #846 of 1320 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 →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 15 spots (#831 → #846)
2026-09-03
Rank Moved
Rank dropped 49 spots (#782 → #831)
2026-09-02
Rank Moved
Rank dropped 45 spots (#737 → #782)
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 65 days ago. Fresh activity helps separate stable projects from stale ones.
36.5
Activity sub-score · out of 100
#454

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 →

Signals refreshed 2026-09-04 14:03 UTC · Repo last pushed 65 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
120
Forks
52
Last Push
2026-07-01
65 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
17
Rank Change
▼15
was #831

Analysis

HVTrust Dimensions vs MCP Servers

47.1 / 100 · 100.0% confidence

MCP Trino MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.7 / 25
in line with avg 9.5
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 11.8
Maintenance60% last-push freshness · 40% commit activity
7.7 / 20
4.5 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.0 / 20
1.2 below avg 6.2

Activity Inputs

36.5 / 100
StarsRepository reach
12.5 / 30
FreshnessLast push recency
16.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.4 / 10
OpenSSF Scorecard · scanned Sep 2, 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

Is MCP Trino safe?

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 65 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.
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

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.

Reputation Timeline

Signal history
Rank 15Listed 1HVTrust 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 15 spots (#831 → #846)
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 47.1 Grade D
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