Slack Explorer MCP

MCP Servers Go Listed MIT

Is Slack Explorer MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.6 / 10
Provenance None
Signed commits 100%
Last push 85d ago
Compare Slack Explorer MCP
Suggest a correction

In detail: Slack Explorer MCP scores 45.4/100 (Grade D), ranked #1052 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.6/10; 100% of recent commits are signed; last pushed 2026-07-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How Slack Explorer MCP compares in MCP Servers

  1. #615 MCP Sports Hub 45.6 +0.2
  2. #616 Wudao A-Share Stock Data MCP 45.5 +0.1
  3. #617 Slack Explorer MCP 45.4 this agent
  4. #618 Memory MCP 45.4 ±0
  5. #619 Perplexity Comet MCP 45.4 ±0

Bars show each HVTrust score; the tick marks Slack Explorer MCP’s 45.4.

Where the 45.4 comes from

HVTrust dimensions vs the MCP Servers average

45.4 / 100 · 100.0% confidence

Slack Explorer MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.8 / 25
0.5 above 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
12.4 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
6.3 / 20
5.8 below avg 12.1
AdoptionLog-scaled stars · package downloads
4.1 / 20
3.1 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 → implemented
2026-09-23
Rank Moved
Rank rose 101 spots (#1142 → #1041)
2026-09-23
HVTrust Changed
HVTrust up 24.8pts (20.8 → 45.6)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/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.
Refresh maintenance signals The repo was last pushed 85 days ago. Fresh activity helps separate stable projects from stale ones.
26.3
Activity sub-score · out of 100
#617

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 85 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
50
Forks
3
Last Push
2026-07-03
85 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
3
Rank Change
=
was #1052

Analysis

Activity Inputs

26.3 / 100
StarsRepository reach
10.2 / 30
FreshnessLast push recency
13.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.6 / 10
OpenSSF Scorecard · scanned Sep 25, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 0
SAST 6
Security-Policy 10
Signed-Releases -1
Token-Permissions 9
Vulnerabilities 0

Common questions about Slack Explorer MCP

Public trust evidence for Slack Explorer MCP 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 Slack Explorer MCP publish package provenance?
No published build provenance is currently detected for Slack Explorer 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 Slack Explorer MCP have an OpenSSF Scorecard?
Slack Explorer MCP has an OpenSSF Scorecard score of 4.6/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 Explorer MCP actively maintained?
Slowing down. Last push was 85 days ago — keep an eye on whether activity resumes.
What license does Slack Explorer MCP use?
Slack Explorer MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Slack Explorer MCP's commits signed?
100% of the last 100 commits to Slack Explorer 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
medium confidence
Implemented
Slack Explorer MCP 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
N/A
No package source configured
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 Explorer MCP'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

Maintain Slack Explorer MCP?

For maintainers

HVTrust scores Slack Explorer 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.

Reputation Timeline

Signal history
Rank 22HVTrust 8Listed 2Scorecard 1Delisted 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 101 spots (#1142 → #1041)
2026-09-23
HVTrust Changed
HVTrust up 24.8pts (20.8 → 45.6)
2026-09-22
Newly Listed
First tracked at rank #1142
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank rose 254 spots (#1276 → #1022)
2026-09-18
HVTrust Changed
HVTrust up 15.0pts (31.0 → 46.0)
2026-09-17
Rank Moved
Rank dropped 255 spots (#1021 → #1276)
2026-09-17
HVTrust Changed
HVTrust down 15.1pts (46.1 → 31.0)
2026-09-12
Rank Moved
Rank rose 252 spots (#1270 → #1018)
2026-09-12
HVTrust Changed
HVTrust up 15.1pts (31.3 → 46.4)
2026-09-11
Rank Moved
Rank dropped 275 spots (#995 → #1270)
2026-09-11
HVTrust Changed
HVTrust down 15.2pts (46.5 → 31.3)
2026-09-09
Rank Moved
Rank rose 268 spots (#1263 → #995)
2026-09-09
HVTrust Changed
HVTrust up 15.2pts (31.4 → 46.6)
2026-09-08
Rank Moved
Rank dropped 293 spots (#970 → #1263)
2026-09-08
HVTrust Changed
HVTrust down 15.3pts (46.7 → 31.4)
2026-09-07
Scorecard Added
OSSF Scorecard: 4.6/10
2026-09-07
Rank Moved
Rank rose 339 spots (#1309 → #970)
2026-09-07
HVTrust Changed
HVTrust up 27.6pts (19.1 → 46.7)
2026-09-03
Rank Moved
Rank dropped 13 spots (#1280 → #1293)
2026-09-02
Rank Moved
Rank dropped 16 spots (#1264 → #1280)
2026-09-01
Rank Moved
Rank dropped 14 spots (#1250 → #1264)
2026-08-31
Rank Moved
Rank dropped 16 spots (#1234 → #1250)
2026-08-30
Rank Moved
Rank dropped 18 spots (#1216 → #1234)
2026-08-29
Rank Moved
Rank dropped 19 spots (#1197 → #1216)
2026-08-28
Rank Moved
Rank dropped 17 spots (#1180 → #1197)
2026-08-27
Rank Moved
Rank dropped 14 spots (#1166 → #1180)
2026-08-26
Rank Moved
Rank dropped 52 spots (#1114 → #1166)
2026-08-24
Rank Moved
Rank dropped 10 spots (#1101 → #1111)
2026-08-20
Rank Moved
Rank dropped 11 spots (#1096 → #1107)
2026-08-16
Rank Moved
Rank dropped 28 spots (#1070 → #1098)
2026-08-12
Rank Moved
Rank rose 10 spots (#1076 → #1066)
2026-08-10
Rank Moved
Rank dropped 60 spots (#1011 → #1071)
2026-08-08
Newly Listed
First tracked at rank #1000

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 45.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/slack-explorer-mcp.svg)](https://hvtracker.net/agents/slack-explorer-mcp)
HTML:
<a href="https://hvtracker.net/agents/slack-explorer-mcp"><img src="https://hvtracker.net/badge/slack-explorer-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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