doom_prep
Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product.
Takes no parameters.
Doom
vc.doomscorePublished by doomscore.vcOfficial publisherv0.1.0Updated Oct 24, 2026
Obsolescence-risk screening: predicts if a product gets absorbed into core LLM-platform features.
Overview
AI-generated overview
A remote MCP endpoint that screens products for obsolescence risk from being absorbed into core LLM-platform features.
- What you can do
- Doom is a remote MCP server reached over streamable HTTP at a fixed endpoint. Its stated purpose is obsolescence-risk screening: it predicts whether a product will be absorbed into core LLM-platform features. No tools, inputs, or outputs are listed in the supplied material, so the exact operations an assistant can call are not documented here.
- When to use it
- Consider it when you want an assistant to assess whether a product or product category is at risk of being subsumed by capabilities shipped by major LLM platforms. It is a screening aid, not a general-purpose tool.
- Requirements
- A remote MCP client that supports streamable HTTP, plus network access to the provider's endpoint. No packages, environment variables, headers, or authentication are declared.
Before you install
The endpoint is third-party and remote, so any prompt or product details you send go to that provider; no authentication is declared, so do not send confidential or proprietary information. The prediction is an estimate and should not be treated as a factual or financial judgment.
Installation
In SourceWeft
- Open Doom in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/vc.doomscore%2Fdoom/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"doom": {
"type": "http",
"url": "https://mcp.doomscore.vc/"
}
}
}README
This repository has no README.
Tools
11assess_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 to deep mode. Optionally pass requested_by to identify the caller (shown in the activity feed).
Parameters
urlmodedeck_textdescriptionrequested_bypitch_company_idget_assessment
Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending.
Parameters
job_idrequiredlist_assessments
Recent assessments, filterable by verdict.
Parameters
limitverdictoverview
Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run.
Takes no parameters.
record_outcome
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.
Parameters
notesjob_idproductoperator_keyrequiredyear_observedactual_outcomerequiredexpected_verdictrequiredlist_signal_candidates
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.
Parameters
limitstatusoperator_keyrequiredreview_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 run; rejected ones are dropped. Controls what becomes grounding truth.
Parameters
actionrequiredcandidate_idrequiredoperator_keyrequiredlist_kb_signals
List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only.
Parameters
operator_keyrequiredretire_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 grounding assessments immediately — recoverable. Operator-only. Find the id via list_kb_signals.
Parameters
reasonrequiredsignal_idrequiredoperator_keyrequiredsupersede_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 the wrong case then record_outcome the right one. Operator-only.
Parameters
reasonrequiredcase_idrequiredoperator_keyrequiredVersion history
1- v0.1.0LatestSep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.