# vc.doomscore/doom (remote · mcp.doomscore.vc)

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

- Trust score: 53/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.doomscore.vc`: 53/100 (this document), [markdown](https://verifymcp.io/servers/vc-doomscore-doom/mcp.md), [page](https://verifymcp.io/servers/vc-doomscore-doom/mcp)

## Channel facts

- Endpoint: `https://mcp.doomscore.vc`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 772 tokens (~70/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 68/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 3% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.vc-doomscore-doom]
url = "https://mcp.doomscore.vc/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vc-doomscore-doom": {
      "type": "remote",
      "url": "https://mcp.doomscore.vc/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vc-doomscore-doom --url https://mcp.doomscore.vc/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vc-doomscore-doom:
    url: "https://mcp.doomscore.vc/"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 52, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 52, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 50, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 49)

First indexed and scored.

## MCP tools (11)

### `doom_prep` (~41 tokens)

Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product.

### `assess_product` (~135 tokens)

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).

Input parameters:

- `deck_text` (string)
- `description` (string)
- `mode` (string)
- `pitch_company_id` (string)
- `requested_by` (string): Who is requesting this assessment (name/handle/agent id) — shown in the #doom-activity feed; defaults to anonymous.
- `url` (string)

### `get_assessment` (~40 tokens)

Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending.

Input parameters:

- `job_id` (string, required)

### `list_assessments` (~32 tokens)

Recent assessments, filterable by verdict.

Input parameters:

- `limit` (number)
- `verdict` (string)

### `overview` (~30 tokens)

Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run.

### `record_outcome` (~128 tokens)

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.

Input parameters:

- `actual_outcome` (string, required)
- `expected_verdict` (string, required)
- `job_id` (string)
- `notes` (string)
- `operator_key` (string, required)
- `product` (string)
- `year_observed` (number)

### `list_signal_candidates` (~72 tokens)

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.

Input parameters:

- `limit` (number)
- `operator_key` (string, required)
- `status` (string)

### `review_signal_candidate` (~78 tokens)

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.

Input parameters:

- `action` (string, required)
- `candidate_id` (string, required)
- `operator_key` (string, required)

### `list_kb_signals` (~45 tokens)

List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only.

Input parameters:

- `operator_key` (string, required)

### `retire_signal` (~89 tokens)

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.

Input parameters:

- `operator_key` (string, required)
- `reason` (string, required)
- `signal_id` (string, required)

### `supersede_calibration_case` (~82 tokens)

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.

Input parameters:

- `case_id` (string, required)
- `operator_key` (string, required)
- `reason` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vc-doomscore-doom/mcp#diagnostics

## Score history

- 2026-08-03: 53
- 2026-08-02: 53
- 2026-08-01: 52
- 2026-07-31: 52
- 2026-07-30: 52
- 2026-07-29: 51
- 2026-07-28: 51
- 2026-07-27: 50
- 2026-07-26: 49

## Links

- Remote endpoint: https://mcp.doomscore.vc/
- Repository: https://github.com/capitalthought/doom
- Website: https://doomscore.vc/
- Changelog RSS feed: https://verifymcp.io/servers/vc-doomscore-doom/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/vc-doomscore-doom/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/vc-doomscore-doom/mcp