mcp server
doom
Obsolescence-risk screening: predicts if a product gets absorbed into core LLM-platform features.
Description as published by the maintainer. Source
- version 0.1.0
- active
active — Registry entry last updated 2026-06-02.
What this server can do
11 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
assess_product(url, mode, deck_text, description, requested_by, pitch_company_id)- 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- Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product.
get_assessment(job_id)- Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending. Required: job_id.
list_assessments(limit, verdict)- Recent assessments, filterable by verdict.
list_kb_signals(operator_key)- List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only. Required: operator_key.
list_signal_candidates(limit, status, operator_key)- 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. Required: operator_key.
overview- Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run.
record_outcome(notes, job_id, product, operator_key, year_observed, actual_outcome, expected_verdict)- 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. Required: operator_key, actual_outcome, expected_verdict.
retire_signal(reason, signal_id, operator_key)- 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. Required: operator_key, signal_id, reason.
review_signal_candidate(action, candidate_id, operator_key)- 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. Required: operator_key, candidate_id, action.
supersede_calibration_case(reason, case_id, operator_key)- 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. Required: operator_key, case_id, reason.
Last successful function declaration observed on . Source: https://mcp.doomscore.vc. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.doomscore.vc.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-02 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-02 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 11 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.doomscore.vc | |
| mcp endpoint status | ok | The server listed 11 functions when asked. | as of probe | mcp.doomscore.vc |
Where to get it
Also from capitalthought
-
bot.yeehaw/events
— last commit 2026-06-08
Agent-first Austin events concierge — fresh, sourced answers to what's happening in Austin.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json