Is Slack MCP Server safe to use?

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

What is the trust score for Slack MCP Server?

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

Slack MCP Server

jtalk22/slack-mcp-server

Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth. 21 tools.

MCP Servers JavaScript Listed MIT

Is Slack MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.7 / 10

Provenance Attested

Signed commits 90%

Last push yesterday

Compare Slack MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Slack MCP Server scores 75.0/100 (Grade B), ranked #222 of 1325 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 5.7/10; 90% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Slack MCP Server compares in MCP Servers

#128 Komodo MCP Server 75.2 +0.2
#129 Quicken Mac MCP 75.2 +0.2
#130 Slack MCP Server 75.0 this agent
#131 Zenrows MCP 75.0 ±0
#132 Sonilo Music & Sound Effects 74.9 −0.1

Bars show each HVTrust score; the tick marks Slack MCP Server’s 75.0.

Where the 75.0 comes from

HVTrust dimensions vs the MCP Servers average

75.0 / 100 · 100.0% confidence

Slack MCP Server MCP Servers average (775 agents)

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

19.1 / 25

8.8 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

13.3 / 17

1.1 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.1 / 20

1.0 above avg 12.1

AdoptionLog-scaled stars · package downloads

6.8 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-25

Rank Moved

Rank rose 11 spots (#233 → #222)

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 5.7/10. Tighten the weakest checks to improve public safety evidence.

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

47.9

Activity sub-score · out of 100

#130

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-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

262

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #222

Analysis

Activity Inputs

47.9 / 100

StarsRepository reach

8.9 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

7.5 / 25

CommunityFork signal

6.5 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.7 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

90%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 9

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 9

SAST 0

Security-Policy 4

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 6

Common questions about Slack MCP Server

Public supply-chain signals for Slack MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Slack MCP Server carries less obvious unverified-evidence risk than projects with thin signals.

Does Slack MCP Server publish package provenance?

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

Does Slack MCP Server have an OpenSSF Scorecard?

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

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

What license does Slack MCP Server use?

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

Are Slack MCP Server's commits signed?

90% of the last 100 commits to Slack 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

Slack 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

medium confidence

1 tags

Broad capability areas detected.

browser

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 Slack 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 Slack MCP Server?

For maintainers

HVTrust scores Slack 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-25

Rank Moved

Rank rose 11 spots (#233 → #222)

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 654 spots (#879 → #225)

2026-09-23

HVTrust Changed

HVTrust up 47.8pts (27.2 → 75.0)

2026-09-22

Newly Listed

First tracked at rank #879

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 12 spots (#201 → #213)

2026-09-11

Grade Changed

Trust grade C → B

2026-09-11

Rank Moved

Rank rose 712 spots (#913 → #201)

2026-09-11

HVTrust Changed

HVTrust up 25.9pts (50.0 → 75.9)

2026-09-10

Grade Changed

Trust grade D → C

2026-09-10

Rank Moved

Rank rose 10 spots (#923 → #913)

2026-09-09

Rank Moved

Rank dropped 16 spots (#907 → #923)

2026-09-07

Rank Moved

Rank dropped 42 spots (#856 → #898)

2026-09-06

Grade Changed

Trust grade C → D

2026-09-06

Rank Moved

Rank dropped 71 spots (#785 → #856)

2026-09-05

Rank Moved

Rank dropped 66 spots (#719 → #785)

2026-09-04

Rank Moved

Rank dropped 26 spots (#693 → #719)

2026-09-03

Rank Moved

Rank dropped 57 spots (#636 → #693)

2026-09-02

Rank Moved

Rank dropped 30 spots (#606 → #636)

2026-09-01

Rank Moved

Rank dropped 21 spots (#585 → #606)

2026-08-31

Rank Moved

Rank dropped 30 spots (#555 → #585)

2026-08-29

Rank Moved

Rank dropped 29 spots (#522 → #551)

2026-08-27

Rank Moved

Rank dropped 19 spots (#503 → #522)

2026-08-26

Scorecard Added

OSSF Scorecard: 5.9/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 26 spots (#529 → #503)

2026-08-26

HVTrust Changed

HVTrust up 7.9pts (45.2 → 53.1)

2026-08-24

Rank Moved

Rank dropped 12 spots (#516 → #528)

2026-08-22

Rank Moved

Rank rose 10 spots (#529 → #519)

2026-08-10

Rank Moved

Rank dropped 13 spots (#508 → #521)

2026-08-08

Newly Listed

First tracked at rank #505

GitHub → npm: @jtalk22/slack-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/slack-mcp-server.svg)](https://hvtracker.net/agents/slack-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/slack-mcp-server"><img src="https://hvtracker.net/badge/slack-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.3 · Raw JSON