updated 2026-10-18 00:07 UTC

Doom MCP

Repository

Play DOOM via MCP - works with Claude Code, Cursor, and any MCP client

MCP Servers Rust Listed MIT

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

OSSF Scorecard 3.4 / 10
Provenance Attested
Signed commits 26%
Last push 219d ago
Advisories None known
Compare Doom MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Doom MCP scores 53.5/100 (Grade C), ranked #896 of 1378 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 3.4/10; 26% of recent commits are signed; no published advisory affects its latest release (doom-mcp); last pushed 2026-03-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Doom 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 Doom 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 Partly signed

    github.com/gunnargrosch/doom-mcp, MIT, last pushed 2026-03-13. 26% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    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 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked and attested

    • npm doom-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: doom-mcp 0.1.3. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-04 OSSF Scorecard: 3.4/10

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

  1. #497 Pgedge Postgres MCP 53.5 ±0
  2. #498 Elasticsearch MCP Server 53.5 ±0
  3. #499 Doom MCP 53.5 this agent
  4. #500 Gmc MCP 53.5 ±0
  5. #501 Lumino MCP Server 53.4 −0.1

Bars show each HVTrust score; the tick marks Doom MCP’s 53.5.

Where the 53.5 comes from

HVTrust dimensions vs the MCP Servers average

53.5 / 100 · 100.0% confidence

Doom MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.1 / 25
2.5 above avg 10.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.4 above avg 13.6
Transparency50% declared license · 50% OSSF Scorecard
11.4 / 17
0.9 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.0 / 20
2.4 below avg 7.4

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-10-15
Rank Moved
Rank dropped 13 spots (#876 → #889)
2026-10-09
Rank Moved
Rank dropped 20 spots (#842 → #862)
2026-09-25
Rank Moved
Rank dropped 11 spots (#823 → #834)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.4/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 219 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Doom MCP View MCP Servers Report missing data
10.2
Activity sub-score · out of 100
#499
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 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-18 00:07 UTC · Repo last pushed 219 days ago — may be stale

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
13
Forks
4
Last Push
2026-03-13
219 days ago
Commits (4 wk)
0
Downloads (7d)
52
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼1
was #895

Analysis

Activity Inputs

10.2 / 100
StarsRepository reach
6.9 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.3 / 20

Common questions about Doom MCP

Public trust evidence for Doom 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 Doom MCP publish package provenance?
Yes. Doom MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Doom MCP have an OpenSSF Scorecard?
Doom MCP has an OpenSSF Scorecard score of 3.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 Doom MCP actively maintained?
Stale. The repository has not been pushed to in 219 days. Consider whether the project is still being maintained.
What license does Doom MCP use?
Doom MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Doom MCP's commits signed?
26% of the last 100 commits to Doom 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
Doom MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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 Doom 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
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Doom MCP?

For maintainers

HVTrust scores Doom 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 3Listed 2Grade 2Scorecard 1Delisted 1Provenance 1MCP 1
2026-10-15
Rank Moved
Rank dropped 13 spots (#876 → #889)
2026-10-09
Rank Moved
Rank dropped 20 spots (#842 → #862)
2026-09-25
Rank Moved
Rank dropped 11 spots (#823 → #834)
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 → C
2026-09-23
Rank Moved
Rank rose 465 spots (#1286 → #821)
2026-09-23
HVTrust Changed
HVTrust up 40.1pts (13.7 → 53.8)
2026-09-22
Newly Listed
First tracked at rank #1286
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 15 spots (#829 → #814)
2026-09-11
Rank Moved
Rank dropped 22 spots (#795 → #817)
2026-09-09
Rank Moved
Rank dropped 12 spots (#786 → #798)
2026-09-07
Rank Moved
Rank dropped 45 spots (#732 → #777)
2026-09-06
Rank Moved
Rank dropped 12 spots (#720 → #732)
2026-09-05
Rank Moved
Rank dropped 71 spots (#649 → #720)
2026-09-04
Scorecard Added
OSSF Scorecard: 3.4/10
2026-09-04
Grade Changed
Trust grade D → C
2026-09-04
Rank Moved
Rank rose 185 spots (#834 → #649)
2026-09-04
HVTrust Changed
HVTrust up 7.1pts (47.1 → 54.2)
2026-09-03
Rank Moved
Rank dropped 49 spots (#785 → #834)
2026-09-02
Rank Moved
Rank rose 319 spots (#1104 → #785)
2026-09-02
HVTrust Changed
HVTrust up 15.6pts (31.6 → 47.2)
2026-09-01
Rank Moved
Rank dropped 42 spots (#1062 → #1104)
2026-08-31
Rank Moved
Rank dropped 31 spots (#1031 → #1062)
2026-08-30
Rank Moved
Rank dropped 56 spots (#975 → #1031)
2026-08-29
Rank Moved
Rank dropped 48 spots (#927 → #975)
2026-08-28
Rank Moved
Rank dropped 38 spots (#889 → #927)
2026-08-27
Rank Moved
Rank dropped 28 spots (#861 → #889)
2026-08-26
Rank Moved
Rank dropped 110 spots (#751 → #861)
2026-08-16
Rank Moved
Rank dropped 15 spots (#735 → #750)
2026-08-10
Rank Moved
Rank dropped 39 spots (#694 → #733)
2026-08-08
Newly Listed
First tracked at rank #694
GitHub → npm: doom-mcp

Embed Badge Badge guide for maintainers →

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