doom

Name: doom
Author: vc.doomscore

MCP serverMCP

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

by vc.doomscorerepository ↗homepage ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"doom","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability108/108 checks ok

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	17 ms	server doom 0.1.0 · protocol 2024-11-05 · 11 tools
12 h ago	mcp initialize	ok	200	10 ms	server doom 0.1.0 · protocol 2024-11-05 · 11 tools
19 h ago	mcp initialize	ok	200	16 ms	server doom 0.1.0 · protocol 2024-11-05 · 11 tools
25 h ago	mcp initialize	ok	200	10 ms	server doom 0.1.0 · protocol 2024-11-05 · 11 tools
32 h ago	mcp initialize	ok	200	36 ms	server doom 0.1.0 · protocol 2024-11-05 · 11 tools
2 d ago	mcp initialize	ok	200	55 ms	server doom 0.1.0 · protocol 2024-11-05 · 11 tools
2 d ago	mcp initialize	ok	200	8 ms	server doom 0.1.0 · protocol 2024-11-05 · 11 tools
2 d ago	mcp initialize	ok	200	16 ms	server doom 0.1.0 · protocol 2024-11-05 · 11 tools
3 d ago	mcp initialize	ok	200	43 ms	server doom 0.1.0 · protocol 2024-11-05 · 11 tools
3 d ago	mcp initialize	ok	200	12 ms	server doom 0.1.0 · protocol 2024-11-05 · 11 tools

Tools observed via MCP handshake

doom_prep — Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product.
assess_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
get_assessment — Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending.
list_assessments — Recent assessments, filterable by verdict.
overview — Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run.
record_outcome — Outcome-feedback (learning loop). Record what ACTUALLY happened to a previously-assessed product as a labeled calibration case; the weekly recalibration folds i
list_signal_candidates — KB-refresh review queue. List auto-scraped candidate roadmap signals (default: pending). Operator-only. Approve/reject with review_signal_candidate; the weekly
review_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 ru
list_kb_signals — List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only.
retire_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
supersede_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 t

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryvc.doomscore/doom

first seen 1 mo ago · fetched 27 h agoopen ↗

Field history (7 recent events)

1 mo ago · declared · summary → "Obsolescence-risk screening: predicts if a product gets absorbed into core LLM-platform features."
1 mo ago · declared · description → "Obsolescence-risk screening: predicts if a product gets absorbed into core LLM-platform features."
1 mo ago · declared · publisherName → "vc.doomscore"
1 mo ago · declared · homepageUrl → "https://doomscore.vc"
1 mo ago · declared · repoUrl → "https://github.com/capitalthought/doom"
1 mo ago · declared · version → "0.1.0"
1 mo ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from