vc.doomscore/doom
REMOTE · MCP.DOOMSCORE.VC · SCANNED AUG 3
Obsolescence-risk screening: predicts if a product gets absorbed into core LLM-platform features.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 772 tokens (~70/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 3% of tool parameters carry a description.Partial
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.doomscore.vc
claude mcp add --transport http vc-doomscore-doom https://mcp.doomscore.vc/
[mcp_servers.vc-doomscore-doom] url = "https://mcp.doomscore.vc/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vc-doomscore-doom": {
"type": "remote",
"url": "https://mcp.doomscore.vc/",
"enabled": true
}
}
} openclaw mcp add vc-doomscore-doom --url https://mcp.doomscore.vc/ --transport streamable-http
mcp_servers:
vc-doomscore-doom:
url: "https://mcp.doomscore.vc/" {
"mcpServers": {
"vc-doomscore-doom": {
"type": "http",
"url": "https://mcp.doomscore.vc/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.doomscore.vc
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=doomscore.vc | CN=WE1,O=Google Trust Services,C=US | 28 Jul 2026 | 26 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 52dd291c7605486113e0be796c525d36 |
| SANs: doomscore.vc, mcp.doomscore.vc, *.mcp.doomscore.vc | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of mcp.doomscore.vc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| vc. | present | 54391 | 8 | Verified |
| doomscore.vc. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.doomscore.vc | Verified | 200 | |
| http (plaintext) | http://mcp.doomscore.vc | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
assess_product ~135
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).
| Name | Type | Req | Description |
|---|---|---|---|
| deck_text | string | — | — |
| description | string | — | — |
| mode | string | — | — |
| pitch_company_id | string | — | — |
| requested_by | string | — | Who is requesting this assessment (name/handle/agent id) — shown in the #doom-activity feed; defaults to anonymous. |
| url | string | — | — |
No output schema declared.
No examples provided.
doom_prep ~41
Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_assessment ~40
Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | — |
No output schema declared.
No examples provided.
list_assessments ~32
Recent assessments, filterable by verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | — |
| verdict | string | — | — |
No output schema declared.
No examples provided.
list_kb_signals ~45
List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only.
| Name | Type | Req | Description |
|---|---|---|---|
| operator_key | string | yes | — |
No output schema declared.
No examples provided.
list_signal_candidates ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | — |
| operator_key | string | yes | — |
| status | string | — | — |
No output schema declared.
No examples provided.
overview ~30
Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
record_outcome ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| actual_outcome | string | yes | — |
| expected_verdict | string | yes | — |
| job_id | string | — | — |
| notes | string | — | — |
| operator_key | string | yes | — |
| product | string | — | — |
| year_observed | number | — | — |
No output schema declared.
No examples provided.
retire_signal ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| operator_key | string | yes | — |
| reason | string | yes | — |
| signal_id | string | yes | — |
No output schema declared.
No examples provided.
review_signal_candidate ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | — |
| candidate_id | string | yes | — |
| operator_key | string | yes | — |
No output schema declared.
No examples provided.
supersede_calibration_case ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | — |
| operator_key | string | yes | — |
| reason | string | yes | — |
No output schema declared.
No examples provided.