_ registry / mcp streamable-http · checked 5h ago

doom

https://mcp.doomscore.vc

Registry code: e01f0b0cb1d34693

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.doomscore.vc
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is doom live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is doom free to use?
Yes — the hub reached it with no key and no payment.
What tools does doom have?
11 tools: list_assessments, supersede_calibration_case, record_outcome, list_kb_signals, doom_prep, review_signal_candidate, retire_signal, get_assessment, ….
Is doom safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
126ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 225 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
finance & markets
used for
  • assess a product's obsolescence risk from llm platforms
  • get an assessment result
  • list recent assessments
  • record the actual outcome for a product
takes → gives
text, web pages, documents → data
tools
6 reads5 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 11 tools
11 never probed 0 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_assessments reads unknown 14h ago

    Recent assessments, filterable by verdict.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "default": 20
    },
    "verdict": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • supersede_calibration_case changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_key",
    "case_id",
    "reason"
  ],
  "properties": {
    "reason": {
      "type": "string"
    },
    "case_id": {
      "type": "string"
    },
    "operator_key": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • record_outcome changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_key",
    "actual_outcome",
    "expected_verdict"
  ],
  "properties": {
    "notes": {
      "type": "string"
    },
    "job_id": {
      "type": "string"
    },
    "product": {
      "type": "string"
    },
    "operator_key": {
      "type": "string"
    },
    "year_observed": {
      "type": "number"
    },
    "actual_outcome": {
      "enum": [
        "sherlocked",
        "survived",
        "thrived"
      ],
      "type": "string"
    },
    "expected_verdict": {
      "enum": [
        "roadkill",
        "squeezed",
        "defensible",
        "riding-the-wave"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 43 lines
  • list_kb_signals reads unknown never probed

    List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_key"
  ],
  "properties": {
    "operator_key": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • doom_prep reads unknown never probed

    Prep Gate. Validates config + confirms the roadmap-signals KB is within the staleness threshold. Fails closed if stale. Call before assess_product.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • review_signal_candidate changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_key",
    "candidate_id",
    "action"
  ],
  "properties": {
    "action": {
      "enum": [
        "approve",
        "reject"
      ],
      "type": "string"
    },
    "candidate_id": {
      "type": "string"
    },
    "operator_key": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • retire_signal changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_key",
    "signal_id",
    "reason"
  ],
  "properties": {
    "reason": {
      "type": "string"
    },
    "signal_id": {
      "type": "string"
    },
    "operator_key": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • get_assessment reads unknown 14h ago

    Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id"
  ],
  "properties": {
    "job_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • assess_product changes data unknown never probed

    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).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "url": {
      "type": "string"
    },
    "mode": {
      "enum": [
        "quick",
        "deep"
      ],
      "type": "string",
      "default": "deep"
    },
    "deck_text": {
      "type": "string"
    },
    "description": {
      "type": "string"
    },
    "requested_by": {
      "type": "string",
      "description": "Who is requesting this assessment (name/handle/agent id) — shown in the #doom-activity feed; defaults to anonymous."
    },
    "pitch_company_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • overview reads unknown never probed

    Inspectable State. No input. Counts, recent activity, roadmap-signal freshness, health, last calibration run.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_signal_candidates reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_key"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "default": 50
    },
    "status": {
      "enum": [
        "pending",
        "approved",
        "rejected",
        "signed"
      ],
      "type": "string"
    },
    "operator_key": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e01f0b0cb1d34693.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e01f0b0cb1d34693/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e01f0b0cb1d34693/badge.svg)](https://brick.blue/agent/e01f0b0cb1d34693?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.