Is Discord MCP safe to use?

Discord MCP has an HVTrust score of 54.8/100 (Grade C), ranked #622 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Discord MCP?

Discord MCP scores 54.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 73 GitHub stars and is categorized under MCP Servers.

Discord MCP

cappyeo/discord-mcp

Caller-owned Discord operations for AI agents - 208 typed tools, safety controls, resumable guild builds, and Activity E

MCP Servers TypeScript Grade C Listed Apache-2.0

54.8/100

Rank #622 of 1320

Compare Discord MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-30 · 5d ago

Recent change

Rank +14

Is Discord MCP safe? Discord MCP scores 54.8/100 (Grade C), ranked #622 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.4/10; 19% of recent commits are signed; last pushed 2026-08-30. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#299 MCP Probe Kit — 54.8 (C) → #300 SunoMCP — 54.8 (C) → #302 Perplexity MCP Server — 54.7 (C) → #303 fastctx — 54.7 (C) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-04

Rank Moved

Rank dropped 17 spots (#605 → #622)

2026-09-03

Rank Moved

Rank dropped 37 spots (#568 → #605)

2026-09-02

Grade Changed

Trust grade A → C

Maintainer Checklist

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

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

65.7

Activity sub-score · out of 100

#301

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

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-08-30

5 days ago

Commits (4 wk)

142

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼17

was #605

Analysis

HVTrust Dimensions vs MCP Servers

54.8 / 100 · 67.0% confidence

Discord MCP MCP Servers average (778 agents)

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

17.7 / 25

8.1 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.8 / 17

3.0 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

19.7 / 20

7.5 above avg 12.2

AdoptionLog-scaled stars · package downloads

4.5 / 20

1.8 below avg 6.3

Activity Inputs

65.7 / 100

StarsRepository reach

11.2 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

5.2 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

7.4 / 10

OpenSSF Scorecard · scanned Sep 1, 2026

Signed Commits

19%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

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 10

SAST 5

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 10

Is Discord MCP safe?

Public trust evidence for Discord 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 Discord MCP publish package provenance?

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

Does Discord MCP have an OpenSSF Scorecard?

Discord MCP has an OpenSSF Scorecard score of 7.4/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 Discord MCP actively maintained?

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

What license does Discord MCP use?

Discord MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Discord MCP's commits signed?

19% of the last 100 commits to Discord 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

Discord 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

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 Discord 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-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain Discord MCP?

For maintainers

HVTrust scores Discord 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

2026-09-04

Rank Moved

Rank dropped 17 spots (#605 → #622)

2026-09-03

Rank Moved

Rank dropped 37 spots (#568 → #605)

2026-09-02

Grade Changed

Trust grade A → C

2026-09-02

Rank Moved

Rank dropped 495 spots (#73 → #568)

2026-09-02

HVTrust Changed

HVTrust down 29.0pts (83.9 → 54.9)

2026-09-01

Scorecard Added

OSSF Scorecard: 7.4/10

2026-09-01

Grade Changed

Trust grade B → A

2026-09-01

Rank Moved

Rank rose 156 spots (#229 → #73)

2026-09-01

HVTrust Changed

HVTrust up 15.6pts (68.3 → 83.9)

2026-08-31

Grade Changed

Trust grade D → B

2026-08-31

Rank Moved

Rank rose 540 spots (#769 → #229)

2026-08-31

HVTrust Changed

HVTrust up 24.3pts (44.0 → 68.3)

2026-08-30

Grade Changed

Trust grade B → D

2026-08-30

Rank Moved

Rank dropped 543 spots (#226 → #769)

2026-08-30

HVTrust Changed

HVTrust down 23.3pts (67.3 → 44.0)

2026-08-26

Rank Moved

Rank dropped 15 spots (#218 → #233)

2026-08-24

Grade Changed

Trust grade D → B

2026-08-24

Rank Moved

Rank rose 336 spots (#552 → #216)

2026-08-24

HVTrust Changed

HVTrust up 22.5pts (43.7 → 66.2)

2026-08-22

Grade Changed

Trust grade B → D

2026-08-22

Rank Moved

Rank dropped 358 spots (#198 → #556)

2026-08-22

HVTrust Changed

HVTrust down 23.3pts (67.0 → 43.7)

2026-08-19

Grade Changed

Trust grade D → B

2026-08-19

Rank Moved

Rank rose 357 spots (#553 → #196)

2026-08-19

HVTrust Changed

HVTrust up 23.2pts (43.9 → 67.1)

2026-08-17

Grade Changed

Trust grade B → D

2026-08-17

Rank Moved

Rank dropped 370 spots (#183 → #553)

2026-08-17

HVTrust Changed

HVTrust down 23.8pts (67.7 → 43.9)

2026-08-16

License Changed

License changed from NOASSERTION to Apache-2.0

2026-08-16

Rank Moved

Rank dropped 11 spots (#172 → #183)

2026-08-15

License Changed

License changed from MIT to NOASSERTION

2026-08-13

Grade Changed

Trust grade D → B

2026-08-13

Rank Moved

Rank rose 372 spots (#545 → #173)

2026-08-13

HVTrust Changed

HVTrust up 24.0pts (43.9 → 67.9)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-12

Grade Changed

Trust grade B → D

2026-08-12

Rank Moved

Rank dropped 383 spots (#162 → #545)

2026-08-12

HVTrust Changed

HVTrust down 24.7pts (68.6 → 43.9)

2026-08-10

Rank Moved

Rank dropped 17 spots (#145 → #162)

2026-08-08

Newly Listed

First tracked at rank #161

GitHub → npm: @discord-mcp/cli

Embed Badge Badge guide for maintainers →

For maintainers

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