Skip to content

vc.doomscore/doom

by doomscore.vc · remote · no sign-in to list tools · v0.1.0 · published by vc.doomscore

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

Changes · 7
CompareRegistry entry

11 tools: 7 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

11 tools

Changes things 7Claude Code: ask
  • assess_productAssess one product's obsolescence risk.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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).
  • doom_prepPrep Gate.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product.
  • overviewInspectable State.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run.
  • record_outcomeOutcome-feedback (learning loop).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_signalUNLEARN a KB signal that became false/obsolete (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_signal_candidateApprove or reject a KB-refresh candidate signal.No findings

    Why it is in this group

    • The description's first verb is "approve": a word for a change.
    Description, as the server wrote it
    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.
  • supersede_calibration_caseUNLEARN a calibration case whose label turned out wrong or obsolete — retires it (active=false) so the recalibration gate stops scoring it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 4Claude Code: allow
  • get_assessmentPoll an assessment job_id.No findings

    Why it is in this group

    • The name "get_assessment" says "get": a word for reading.
    Description, as the server wrote it
    Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending.
  • list_assessmentsRecent assessments, filterable by verdict.No findings

    Why it is in this group

    • The name "list_assessments" says "list": a word for reading.
    Description, as the server wrote it
    Recent assessments, filterable by verdict.
  • list_kb_signalsList the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire.No findings

    Why it is in this group

    • The name "list_kb_signals" says "list": a word for reading.
    Description, as the server wrote it
    List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only.
  • list_signal_candidatesKB-refresh review queue.No findings

    Why it is in this group

    • The name "list_signal_candidates" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__doom__get_assessment",
      "mcp__doom__list_assessments",
      "mcp__doom__list_signal_candidates",
      "mcp__doom__list_kb_signals"
    ],
    "ask": [
      "mcp__doom__doom_prep",
      "mcp__doom__assess_product",
      "mcp__doom__overview",
      "mcp__doom__record_outcome",
      "mcp__doom__review_signal_candidate",
      "mcp__doom__retire_signal",
      "mcp__doom__supersede_calibration_case"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as doom. Review it before you use it.