Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
Doom is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Obsolescence-risk screening: predicts if a product gets absorbed into core LLM-platform features.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http doomscore-doom-mcp https://mcp.doomscore.vc
# 2 — ask your agent for something these tools do
# doom_prep, assess_product, get_assessment and 8 more
Doom costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DOAll 1 server
doomscore1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http doomscore-doom-mcp https://mcp.doomscore.vcReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product.
No parameter schema on file.
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | no | — |
| url | string | no | — |
| pitch_company_id | string | no | — |
| deck_text | string | no | — |
| mode | string | no | — |
| requested_by | string | no | Who is requesting this assessment (name/handle/agent id) — shown in the #doom-activity feed; defaults to anonymous. |
Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | — |
Recent assessments, filterable by verdict.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| verdict | string | no | — |
| limit | number | no | — |
Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operator_key | string | yes | — |
| job_id | string | no | — |
| product | string | no | — |
| actual_outcome | string | yes | — |
| expected_verdict | string | yes | — |
| year_observed | number | no | — |
| notes | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operator_key | string | yes | — |
| status | string | no | — |
| limit | number | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operator_key | string | yes | — |
| candidate_id | string | yes | — |
| action | string | yes | — |
List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operator_key | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operator_key | string | yes | — |
| signal_id | string | yes | — |
| reason | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operator_key | string | yes | — |
| case_id | string | yes | — |
| reason | string | yes | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Doom or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Doom can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.