# `vc.doomscore/doom` on anlyon.dev > Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by anlyon.dev. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX]. > No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour. - Page: https://anlyon.dev/servers/vc.doomscore/doom - JSON: https://anlyon.dev/api/v1/servers/vc.doomscore/doom - Version: 0.1.0 (active) - Publisher: vc.doomscore (domain proven to the MCP Registry) - Runs: remote (streamable-http) - Sign-in to list tools: none - Repository: https://github.com/capitalthought/doom - Metadata from the official MCP Registry, synced 2026-10-21T18:55:44.960Z Title and description, as the publisher wrote them: ```untrusted-server-text Obsolescence-risk screening: predicts if a product gets absorbed into core LLM-platform features. ``` Scanned 2026-10-21T19:16:28.535Z over streamable-http. **11 tools: 7 change things and 4 only read.** | Group | Class | Tools | Claude Code | | --- | --- | --- | --- | | Deletes or cancels | destructive | 0 | deny | | Can't be undone | irreversible | 0 | ask | | Changes things | write | 7 | ask | | Only reads | read | 4 | allow | ## Findings No check matched anything in these tool definitions. ## Changes things (7) Creates or changes something that can be changed back. Claude Code: ask. ### `assess_product` - Nothing in its name or description says what it does, so it is counted as a write. Description, as the server wrote it: ```untrusted-server-text 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_prep` - Nothing in its name or description says what it does, so it is counted as a write. Description, as the server wrote it: ```untrusted-server-text Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product. ``` ### `overview` - Nothing in its name or description says what it does, so it is counted as a write. Description, as the server wrote it: ```untrusted-server-text Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run. ``` ### `record_outcome` - Nothing in its name or description says what it does, so it is counted as a write. Description, as the server wrote it: ```untrusted-server-text 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_signal` - Nothing in its name or description says what it does, so it is counted as a write. Description, as the server wrote it: ```untrusted-server-text 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_candidate` - The description's first verb is "approve": a word for a change. Description, as the server wrote it: ```untrusted-server-text 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_case` - Nothing in its name or description says what it does, so it is counted as a write. Description, as the server wrote it: ```untrusted-server-text 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 (4) Looks things up and changes nothing. Claude Code: allow. ### `get_assessment` - The name "get_assessment" says "get": a word for reading. Description, as the server wrote it: ```untrusted-server-text Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending. ``` ### `list_assessments` - The name "list_assessments" says "list": a word for reading. Description, as the server wrote it: ```untrusted-server-text Recent assessments, filterable by verdict. ``` ### `list_kb_signals` - The name "list_kb_signals" says "list": a word for reading. Description, as the server wrote it: ```untrusted-server-text List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only. ``` ### `list_signal_candidates` - The name "list_signal_candidates" says "list": a word for reading. Description, as the server wrote it: ```untrusted-server-text 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. ``` ## Claude Code permissions For `.claude/settings.json`, assuming the server is installed as `doom`: ```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": [] } } ```