mcpbeat

Doom MCP Server

vc.doomscore/doom
answering

Doom is answering right now. Last checked 15 min ago. It exposes 11 tools.

Obsolescence-risk screening: predicts if a product gets absorbed into core LLM-platform features.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 44 hours of history
44 hours agonow
100.0%
Uptime 24h
91 of 91 checks
11
Tools
read from the server
99 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add doom --transport http https://mcp.doomscore.vc
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "doom": {
      "url": "https://mcp.doomscore.vc"
    }
  }
}
~/.codex/config.toml
[mcp_servers.doom]
url = "https://mcp.doomscore.vc"
.cursor/mcp.json
{
  "mcpServers": {
    "doom": {
      "url": "https://mcp.doomscore.vc"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "doom": {
      "url": "https://mcp.doomscore.vc"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

assess
assess_product
Assess one product's obsolescence risk. Provide exactly ONE of description/url/pitch_company_id/deck_text. Async — returns job_id; poll get_assessment. Defaults to deep mode. Optionally pass requested_by to identify the caller (shown in the activity feed).
assessment
get_assessment
Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending.
assessments
list_assessments
Recent assessments, filterable by verdict.
doom
doom_prep
Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product.
overview
overview
Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run.
record
record_outcome
Outcome-feedback (learning loop). Record what ACTUALLY happened to a previously-assessed product as a labeled calibration case; the weekly recalibration folds it into the gate. Operator-only (requires operator_key). Provide either job_id (links the case to that assessment + reuses its product) or product text.
retire
retire_signal
UNLEARN a KB signal that became false/obsolete (e.g. a rumored feature cancelled, or a signal no longer predictive). Soft-deletes it (active=false) so it stops grounding assessments immediately — recoverable. Operator-only. Find the id via list_kb_signals.
review
review_signal_candidate
Approve or reject a KB-refresh candidate signal. Operator-only. Approved candidates are signed (Ed25519) into the live roadmap_signals KB by the next refresh run; rejected ones are dropped. Controls what becomes grounding truth.
signal
list_signal_candidates
KB-refresh review queue. List auto-scraped candidate roadmap signals (default: pending). Operator-only. Approve/reject with review_signal_candidate; the weekly cron signs approved ones into the live KB.
signals
list_kb_signals
List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only.
supersede
supersede_calibration_case
UNLEARN a calibration case whose label turned out wrong or obsolete — retires it (active=false) so the recalibration gate stops scoring it. To correct, retire the wrong case then record_outcome the right one. Operator-only.

Endpoints

URLTransportStateLatencyChecked
https://mcp.doomscore.vc streamable-http answering 106 ms 15 min ago

Doom — questions

Answers built from our own checks of this server.

What can Doom do?
It exposes 11 tools, read directly from the server on our last check. Among them: assess_product, doom_prep, get_assessment, list_assessments, list_kb_signals, list_signal_candidates and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Doom working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 99 ms. The bar chart above shows every period we have measured.
Is Doom still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Doom?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Doom need an API key?
No. Doom completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Doom?
It answers our handshake in 99 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.