doom MCP server
vc.doomscore/doomdoomscore.vcstreamable-httpv0.1.0Scanned
Obsolescence-risk screening: predicts if a product gets absorbed into core LLM-platform features.
11 tools: 7 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
7 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the doom MCP server can do
The doom MCP server is published by doomscore.vc, a domain the MCP Registry verified. It has 11 tools. It can create or change data (7 tools: doom_prep, assess_product, overview, record_outcome and 3 more), but cannot delete data. 4 tools only read.
1 tool brings in text other people can write (list_signal_candidates); 1 tool can send data out of your system (assess_product).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Changes things 7Claude Code: ask
assess_productAssess one product's obsolescence risk.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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_prepPrep Gate.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product.
overviewInspectable State.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run.
record_outcomeOutcome-feedback (learning loop).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_signalUNLEARN a KB signal that became false/obsolete (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_candidateApprove or reject a KB-refresh candidate signal.No findings
Why it is in this group
- The description's first verb is "approve": a word for a change.
Description, as the server wrote it 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_caseUNLEARN a calibration case whose label turned out wrong or obsolete — retires it (active=false) so the recalibration gate stops scoring it.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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 4Show 4 read-only tools
get_assessmentPoll an assessment job_id.No findings
Why it is in this group
- The name "get_assessment" says "get": a word for reading.
Description, as the server wrote it Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending.
list_assessmentsRecent assessments, filterable by verdict.No findings
Why it is in this group
- The name "list_assessments" says "list": a word for reading.
Description, as the server wrote it Recent assessments, filterable by verdict.
list_kb_signalsList the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire.No findings
Why it is in this group
- The name "list_kb_signals" says "list": a word for reading.
Description, as the server wrote it List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only.
list_signal_candidatesKB-refresh review queue.Reads text others writeNo findings
Why it is in this group
- The name "list_signal_candidates" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:21 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.doomscore.vc: tools/list returned 11 tools to an anonymous client, including doom_prep (write), assess_product (write), overview (write), record_outcome (write), review_signal_candidate (write) and 2 more
Posture changes
- Nov 6, 2026
- HTTP status of an anonymous initialize: 429 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 7
- Protocol version: none to 2024-11-05
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2024-11-05 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 429 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 7 (and 1 more).View diff
- HTTP status of an anonymous initialize: 429 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 7
- Protocol version: none to 2024-11-05
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 7 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2024-11-05 to none
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http doom https://mcp.doomscore.vcclaude mcp add --transport http doom https://mcp.doomscore.vcRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.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": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as doom. Review it before you use it.
Capability tags behind 2 rules
- mcp__doom__assess_product outbound
- mcp__doom__list_signal_candidates untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/vc.doomscore/doom/verify?hash=6dba1b1ef9f8c09525a9c603e6d1fd157ae33d4b582ac9e6c40ccb6724b5953e" | jq -e '.changed == false'Pinned hash 6dba1b1ef9f8, from Nov 18, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/vc.doomscore/doom/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/vc.doomscore/doom)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:55 UTC.
doom MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the doom MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the doom MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the doom MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the doom MCP server have?
- 11 tools: 7 write, 4 read. doom_prep, assess_product, overview, record_outcome, review_signal_candidate, retire_signal, supersede_calibration_case, get_assessment and 3 more.
Does the doom MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the doom MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): assess_product.
Has the doom MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.