# Doomscore Doom MCP server

Source: https://glimind.com/server/mcp-registry%2Fvc.doomscore%2Fdoom
Registry id: `mcp-registry/vc.doomscore/doom`
Status: live (checked 2026-10-27T04:15:29.624Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 4937
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "doomscore-doom-mcp-server": {
      "type": "http",
      "url": "https://mcp.doomscore.vc"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http doomscore-doom-mcp-server https://mcp.doomscore.vc
```

## Tools (11)

- `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
- `doom_prep`: Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product.
- `get_assessment`: Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending.
- `list_assessments`: Recent assessments, filterable by verdict.
- `list_kb_signals`: List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only.
- `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 
- `overview`: Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run.
- `record_outcome`: Outcome-feedback (learning loop). Record what ACTUALLY happened to a previously-assessed product as a labeled calibration case; the weekly recalibration folds i
- `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 
- `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 ru
- `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 t

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
