Is Upstash MCP Server safe to use?

Upstash MCP Server has an HVTrust score of 71.4/100 (Grade B), ranked #304 of 1343 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Upstash MCP Server?

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

Upstash MCP Server

Repository by upstash

Upstash Model Context Server

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 4.1 / 10

Provenance Attested

Signed commits 80%

Last push 30d ago

Advisories None known

Compare Upstash MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Upstash MCP Server scores 71.4/100 (Grade B), ranked #304 of 1343 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.1/10; 80% of recent commits are signed; no published advisory affects its latest release (@upstash/mcp-server); last pushed 2026-09-01. Every point is earned from checkable signals — never paid placement. How scoring works →

How Upstash 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.

Raise the OSSF Scorecard from 4.1 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Dependency-Update-Tool 0 +10.2 → 81.6 A · #62 of 778
Sign every commit80% signed today +1.0 → 72.4 B · #170 of 778

Already done? Suggest a correction Add the trust badge

How Upstash MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks Upstash MCP Server’s 71.4.

Where the 71.4 comes from

HVTrust dimensions vs the MCP Servers average

71.4 / 100 · 100.0% confidence

Upstash MCP Server MCP Servers average (778 agents)

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

16.6 / 25

6.3 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.0 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

11.2 / 20

0.9 below avg 12.1

AdoptionLog-scaled stars · package downloads

8.6 / 20

1.3 above avg 7.3

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-30

Rank Moved

Rank dropped 15 spots (#290 → #305)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

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

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

40.8

Activity sub-score · out of 100

#180

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 B 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-09-29 2026-09-30

Activity & Reach

Stars

Forks

Last Push

2026-09-01

30 days ago

Commits (4 wk)

Downloads (7d)

1,933

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #305

Analysis

Activity Inputs

40.8 / 100

StarsRepository reach

10.7 / 30

FreshnessLast push recency

20.8 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

5.3 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.1 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

80%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 7

CII-Best-Practices 0

Code-Review 6

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Upstash MCP Server

Upstash 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 Upstash MCP Server publish package provenance?

Yes. Upstash MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Upstash MCP Server have an OpenSSF Scorecard?

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

Maintained. Last push was 30 days ago.

What license does Upstash MCP Server use?

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

Are Upstash MCP Server's commits signed?

79% of the last 100 commits to Upstash 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

high confidence

Implemented

Upstash MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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

high confidence

Match

Published package metadata matches the tracked repo

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 Upstash 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 → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Upstash MCP Server?

For maintainers

HVTrust scores Upstash 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-30

Rank Moved

Rank dropped 15 spots (#290 → #305)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 746 spots (#1017 → #271)

2026-09-23

HVTrust Changed

HVTrust up 48.2pts (24.5 → 72.7)

2026-09-22

Newly Listed

First tracked at rank #1017

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Rank Moved

Rank dropped 13 spots (#220 → #233)

2026-09-09

Rank Moved

Rank rose 22 spots (#242 → #220)

2026-09-07

Rank Moved

Rank dropped 23 spots (#215 → #238)

2026-09-05

Scorecard Added

OSSF Scorecard: 4.1/10

2026-09-05

Rank Moved

Rank rose 104 spots (#315 → #211)

2026-09-05

HVTrust Changed

HVTrust up 8.5pts (65.6 → 74.1)

2026-09-04

Rank Moved

Rank dropped 14 spots (#301 → #315)

2026-08-31

Grade Changed

Trust grade C → B

2026-08-31

Rank Moved

Rank dropped 25 spots (#267 → #292)

2026-08-30

Grade Changed

Trust grade B → C

2026-08-29

Rank Moved

Rank dropped 13 spots (#258 → #271)

2026-08-26

Rank Moved

Rank dropped 20 spots (#235 → #255)

2026-08-24

Grade Changed

Trust grade C → B

2026-08-22

Rank Moved

Rank rose 14 spots (#241 → #227)

2026-08-20

Grade Changed

Trust grade B → C

2026-08-19

Grade Changed

Trust grade C → B

2026-08-16

Newly Listed

First tracked at rank #238

GitHub → npm: @upstash/mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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