updated 2026-11-10 04:07 UTC

Greptimedb MCP Server

Repository

A Model Context Protocol (MCP) server for GreptimeDB

MCP Servers Python Listed MIT

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

OSSF Scorecard 5.8 / 10
Provenance None
Signed commits 21%
Last push 29d ago
Advisories None known
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 50.9/100 (Grade C), ranked #981 of 1374 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 5.8/10; 21% of recent commits are signed; no published advisory affects its latest release (greptimedb-mcp-server); last pushed 2026-10-12. Every point is earned from checkable signals — never paid placement. How scoring works →

How Greptimedb MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Greptimedb MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/GreptimeTeam/greptimedb-mcp-server, MIT, last pushed 2026-10-12. 21% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.8/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 2
    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

  3. Published packages Not linked

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: greptimedb-mcp-server 0.6.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-04 OSSF Scorecard: 5.4/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Greptimedb MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Greptimedb MCP Server compares in MCP Servers

  1. #550 MCP Neo4j 51.0 +0.1
  2. #551 MCP Server Motherduck 51.0 +0.1
  3. #552 Greptimedb MCP Server 50.9 this agent
  4. #553 Zapier 50.9 ±0
  5. #554 UnrealMCP — AI Bridge for Unreal Engine 5 50.9 ±0

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

Where the 50.9 comes from

HVTrust dimensions vs the MCP Servers average

50.9 / 100 · 100.0% confidence

Greptimedb MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.3 / 25
2.5 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
13.4 / 17
1.1 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
12.5 / 20
in line with avg 12.2
AdoptionLog-scaled stars · package downloads
5.9 / 20
1.7 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-07
Rank Moved
Rank rose 10 spots (#985 → #975)
2026-10-25
Rank Moved
Rank dropped 13 spots (#943 → #956)
2026-10-23
Rank Moved
Rank dropped 108 spots (#841 → #949)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.8/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
View MCP Servers Report missing data
42.7
Activity sub-score · out of 100
#552
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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 29 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
29
Forks
12
Last Push
2026-10-12
29 days ago
Commits (4 wk)
3
Downloads (7d)
57
pypi
HN mentions (30d)
—
Open Issues
6
Rank Change
▼6
was #975

Analysis

Activity Inputs

42.7 / 100
StarsRepository reach
8.9 / 30
FreshnessLast push recency
21.0 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
5.2 / 20

Common questions about Greptimedb MCP Server

Public trust evidence for Greptimedb MCP Server 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 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 5.8/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?
Maintained. Last push was 29 days ago.
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?
21% 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
Rank 34Score 4HVTrust 4Grade 2Scorecard 1Delisted 1Listed 1MCP 1
2026-11-07
Rank Moved
Rank rose 10 spots (#985 → #975)
2026-10-25
Rank Moved
Rank dropped 13 spots (#943 → #956)
2026-10-23
Rank Moved
Rank dropped 108 spots (#841 → #949)
2026-10-23
Activity Score Changed
Activity score down 8pts (53 → 45)
2026-10-20
Rank Moved
Rank dropped 11 spots (#825 → #836)
2026-10-15
Rank Moved
Rank dropped 12 spots (#795 → #807)
2026-10-14
Rank Moved
Rank dropped 24 spots (#771 → #795)
2026-10-12
Rank Moved
Rank rose 67 spots (#838 → #771)
2026-10-12
Activity Score Changed
Activity score up 8pts (48 → 56)
2026-10-11
Rank Moved
Rank dropped 11 spots (#827 → #838)
2026-10-09
Rank Moved
Rank dropped 52 spots (#778 → #830)
2026-10-07
Rank Moved
Rank dropped 36 spots (#744 → #780)
2026-10-04
Rank Moved
Rank rose 10 spots (#752 → #742)
2026-10-01
Rank Moved
Rank dropped 12 spots (#743 → #755)
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)
GitHub → PyPI: greptimedb-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.9 Grade C
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.4 · Raw JSON