updated 2026-10-11 04:08 UTC

Sentry MCP

Repository Website by getsentry

Agentic tooling for Sentry

MCP Servers TypeScript Listed NOASSERTION Source-available

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

OSSF Scorecard 4.9 / 10
Provenance None
Signed commits 91%
Last push yesterday
Advisories None known
Compare Sentry MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Sentry MCP scores 67.3/100 (Grade B), ranked #425 of 1371 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 4.9/10; 91% of recent commits are signed; no published advisory affects its latest release (@sentry/mcp-server); last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Sentry MCP 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 Sentry MCP 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 Signed

    github.com/getsentry/toolkit, NOASSERTION, last pushed 2026-10-10. 91% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review1
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow0
    • Token Permissions0
    • Pinned Dependencies6
    All 18 Scorecard checks
    Binary-Artifacts 8
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 1
    Contributors 10
    Dangerous-Workflow 0
    Dependency-Update-Tool 10
    Fuzzing 10
    License 9
    Maintained 10
    Packaging -1
    Pinned-Dependencies 6
    SAST 9
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Not linked

    • npm @sentry/mcp-server Source link points to getsentry/sentry-mcp, same owner No build attestation

    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: @sentry/mcp-server 0.42.0. No published advisory affects it (OSV, checked 2026-10-11).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Sentry MCP.

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 Sentry MCP’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 Sentry MCP compares in MCP Servers

  1. #247 Wet MCP 67.3 ±0
  2. #248 Korean Law MCP 67.3 ±0
  3. #249 Sentry MCP 67.3 this agent
  4. #250 World Model MCP 67.2 −0.1
  5. #251 Idea Reality MCP 67.2 −0.1

Bars show each HVTrust score; the tick marks Sentry MCP’s 67.3.

Where the 67.3 comes from

HVTrust dimensions vs the MCP Servers average

67.3 / 100 · 100.0% confidence

Sentry MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.7 / 25
in line with avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.7 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.7 above avg 12.2
AdoptionLog-scaled stars · package downloads
13.8 / 20
6.4 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-10
Rank Moved
Rank rose 14 spots (#438 → #424)
2026-10-09
Rank Moved
Rank dropped 16 spots (#422 → #438)
2026-10-08
Rank Moved
Rank rose 15 spots (#437 → #422)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/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.
Compare with another agent Get email alerts for Sentry MCP View MCP Servers Report missing data
78.1
Activity sub-score · out of 100
#249
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 →

Signals refreshed 2026-10-11 04:08 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
922
Forks
161
Last Push
2026-10-10
yesterday
Commits (4 wk)
263
Downloads (7d)
102,729
npm
HN mentions (30d)
—
Open Issues
86
Rank Change
▼1
was #424

Analysis

Activity Inputs

78.1 / 100
StarsRepository reach
17.8 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
10.3 / 20

Common questions about Sentry MCP

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Sentry MCP may have internal security practices not visible through public signals.
Sentry MCP 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 Sentry MCP publish package provenance?
No published build provenance is currently detected for Sentry MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Sentry MCP have an OpenSSF Scorecard?
Sentry MCP has an OpenSSF Scorecard score of 4.9/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 Sentry MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Sentry MCP use?
Sentry MCP ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Sentry MCP's commits signed?
91% of the last 100 commits to Sentry MCP 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
Sentry MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • code
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

Maintain Sentry MCP?

For maintainers

HVTrust scores Sentry MCP 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 22HVTrust 5Grade 2
2026-10-10
Rank Moved
Rank rose 14 spots (#438 → #424)
2026-10-09
Rank Moved
Rank dropped 16 spots (#422 → #438)
2026-10-08
Rank Moved
Rank rose 15 spots (#437 → #422)
2026-10-03
Rank Moved
Rank dropped 128 spots (#307 → #435)
2026-10-03
HVTrust Changed
HVTrust down 5.0pts (71.3 → 66.3)
2026-10-02
Rank Moved
Rank dropped 29 spots (#278 → #307)
2026-10-01
Rank Moved
Rank rose 16 spots (#294 → #278)
2026-09-23
Rank Moved
Rank dropped 180 spots (#116 → #296)
2026-09-21
Rank Moved
Rank rose 185 spots (#302 → #117)
2026-09-12
Rank Moved
Rank rose 110 spots (#409 → #299)
2026-09-12
HVTrust Changed
HVTrust up 4.7pts (66.4 → 71.1)
2026-09-11
Rank Moved
Rank dropped 13 spots (#396 → #409)
2026-09-10
Rank Moved
Rank dropped 104 spots (#292 → #396)
2026-09-10
HVTrust Changed
HVTrust down 4.7pts (71.1 → 66.4)
2026-09-07
Rank Moved
Rank dropped 25 spots (#263 → #288)
2026-09-05
Grade Changed
Trust grade D → B
2026-09-05
Rank Moved
Rank rose 689 spots (#944 → #255)
2026-09-05
HVTrust Changed
HVTrust up 27.2pts (44.2 → 71.4)
2026-09-04
Rank Moved
Rank dropped 26 spots (#918 → #944)
2026-09-03
Rank Moved
Rank dropped 46 spots (#872 → #918)
2026-09-02
Grade Changed
Trust grade B → D
2026-09-02
Rank Moved
Rank dropped 686 spots (#186 → #872)
2026-09-02
HVTrust Changed
HVTrust down 27.2pts (71.3 → 44.1)
2026-08-31
Rank Moved
Rank dropped 21 spots (#163 → #184)
2026-08-29
Rank Moved
Rank dropped 13 spots (#157 → #170)
2026-08-28
Rank Moved
Rank dropped 10 spots (#147 → #157)
2026-08-26
Rank Moved
Rank dropped 16 spots (#123 → #139)
2026-08-08
Rank Moved
Rank dropped 12 spots (#108 → #120)
2026-07-27
Rank Moved
Rank rose 10 spots (#115 → #105)
GitHub → Website → npm: @sentry/mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 67.3 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/sentry-mcp.svg)](https://hvtracker.net/agents/sentry-mcp)
HTML:
<a href="https://hvtracker.net/agents/sentry-mcp"><img src="https://hvtracker.net/badge/sentry-mcp.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