Is Greptimedb MCP Server safe to use?

Greptimedb MCP Server has an HVTrust score of 56.8/100 (Grade C), ranked #722 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Greptimedb MCP Server?

Greptimedb MCP Server scores 56.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 29 GitHub stars and is categorized under MCP Servers.

Greptimedb MCP Server

GreptimeTeam/greptimedb-mcp-server

A Model Context Protocol (MCP) server for GreptimeDB

MCP Servers Python Listed MIT

Is Greptimedb MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.2 / 10

Provenance None

Signed commits 24%

Last push 3d ago

Compare Greptimedb MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Greptimedb MCP Server scores 56.8/100 (Grade C), ranked #722 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.2/10; 24% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How Greptimedb MCP Server compares in MCP Servers

#398 Orcaslicer MCP 56.9 +0.1
#399 AgentPhone 56.9 +0.1
#400 Greptimedb MCP Server 56.8 this agent
#401 MaverickMCP 56.8 ±0
#402 Oxylabs MCP 56.8 ±0

Bars show each HVTrust score; the tick marks Greptimedb MCP Server’s 56.8.

Where the 56.8 comes from

HVTrust dimensions vs the MCP Servers average

56.8 / 100 · 100.0% confidence

Greptimedb MCP Server MCP Servers average (775 agents)

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

8.9 / 25

1.4 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

13.8 / 17

1.6 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.6 / 20

5.5 above avg 12.1

AdoptionLog-scaled stars · package downloads

5.7 / 20

1.5 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

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 53 spots (#762 → #709)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.2/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

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

56.9

Activity sub-score · out of 100

#400

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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-23

3 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #720

Analysis

Activity Inputs

56.9 / 100

StarsRepository reach

8.9 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

18.1 / 25

CommunityFork signal

5.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.2 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

24%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 6

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 10

Security-Policy 0

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 10

Common questions about Greptimedb MCP Server

Greptimedb MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Greptimedb MCP Server publish package provenance?

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

Does Greptimedb MCP Server have an OpenSSF Scorecard?

Greptimedb MCP Server has an OpenSSF Scorecard score of 6.2/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 Greptimedb MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 3 day(s).

What license does Greptimedb MCP Server use?

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

Are Greptimedb MCP Server's commits signed?

24% of the last 100 commits to Greptimedb MCP Server 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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

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

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

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 Greptimedb MCP Server'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

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintain Greptimedb MCP Server?

For maintainers

HVTrust scores Greptimedb MCP Server 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

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 53 spots (#762 → #709)

2026-09-23

HVTrust Changed

HVTrust up 27.3pts (29.7 → 57.0)

2026-09-22

Newly Listed

First tracked at rank #762

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-16

Rank Moved

Rank dropped 10 spots (#679 → #689)

2026-09-14

Rank Moved

Rank rose 52 spots (#738 → #686)

2026-09-11

Rank Moved

Rank rose 45 spots (#773 → #728)

2026-09-09

Rank Moved

Rank dropped 12 spots (#756 → #768)

2026-09-07

Rank Moved

Rank rose 63 spots (#816 → #753)

2026-09-07

HVTrust Changed

HVTrust up 3.5pts (51.2 → 54.7)

2026-09-07

Activity Score Changed

Activity score up 6pts (48 → 54)

2026-09-06

Rank Moved

Rank dropped 27 spots (#789 → #816)

2026-09-05

Rank Moved

Rank dropped 65 spots (#724 → #789)

2026-09-04

Scorecard Added

OSSF Scorecard: 5.4/10

2026-09-04

Grade Changed

Trust grade D → C

2026-09-04

Rank Moved

Rank rose 510 spots (#1234 → #724)

2026-09-04

HVTrust Changed

HVTrust up 25.0pts (27.0 → 52.0)

2026-09-03

Rank Moved

Rank dropped 41 spots (#1193 → #1234)

2026-09-02

Rank Moved

Rank dropped 35 spots (#1158 → #1193)

2026-09-01

Rank Moved

Rank dropped 42 spots (#1116 → #1158)

2026-08-31

Rank Moved

Rank dropped 31 spots (#1085 → #1116)

2026-08-30

Rank Moved

Rank dropped 49 spots (#1036 → #1085)

2026-08-29

Rank Moved

Rank dropped 51 spots (#985 → #1036)

2026-08-28

Rank Moved

Rank dropped 38 spots (#947 → #985)

2026-08-27

Rank Moved

Rank dropped 27 spots (#920 → #947)

2026-08-26

Rank Moved

Rank dropped 111 spots (#809 → #920)

2026-08-22

Rank Moved

Rank rose 10 spots (#809 → #799)

2026-08-17

Rank Moved

Rank rose 10 spots (#807 → #797)

2026-08-16

Rank Moved

Rank rose 56 spots (#863 → #807)

2026-08-16

HVTrust Changed

HVTrust up 3.8pts (23.9 → 27.7)

2026-08-16

Activity Score Changed

Activity score up 15pts (33 → 48)

2026-08-13

Rank Moved

Rank dropped 13 spots (#858 → #871)

2026-08-10

Rank Moved

Rank dropped 48 spots (#812 → #860)

2026-08-08

Newly Listed

First tracked at rank #804

GitHub → PyPI: greptimedb-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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