Is the Doomscore Doom MCP server down?

mcp-registry/vc.doomscore/doom · v0.1.0

As of 2026-10-26 09:29 UTC, the Doomscore Doom MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

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

claude mcp add --transport http doomscore-doom-mcp-server https://mcp.doomscore.vc

{
  "mcpServers": {
    "doomscore-doom-mcp-server": {
      "type": "http",
      "url": "https://mcp.doomscore.vc"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (69/100)

What to fix (4)

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 9 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fvc.doomscore%2Fdoom/fixes

{
  "name": "get_assessment",
  "description": "Poll an assessment job_id. Returns status + the typed assessment when complete. Hard timeout — never hangs on pending.",
  "inputSchema": {
    "type": "object",
    "required": [
      "job_id"
    ],
    "properties": {
      "job_id": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "list_assessments",
  "description": "Recent assessments, filterable by verdict.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "number",
        "default": 20
      },
      "verdict": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "list_kb_signals",
  "description": "List the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire. Operator-only.",
  "inputSchema": {
    "type": "object",
    "required": [
      "operator_key"
    ],
    "properties": {
      "operator_key": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/vc.doomscore/doom"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/vc.doomscore/doom"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~1,360 tokens).
• Tool names are unique and portable across clients.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• record_outcome ~228 tokens
• assess_product ~203 tokens
• review_signal_candidate ~147 tokens
• retire_signal ~143 tokens
• list_signal_candidates ~141 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fvc.doomscore%2Fdoom.svg)](https://glimind.com/server/mcp-registry%2Fvc.doomscore%2Fdoom?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fvc.doomscore%2Fdoom?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fvc.doomscore%2Fdoom.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fvc.doomscore%2Fdoom.svg
   :target: https://glimind.com/server/mcp-registry%2Fvc.doomscore%2Fdoom?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:bea7636bfa9a54d8…, first seen 2026-10-17, included at leaf 13276 of 71,944. Version history · verify what your client received.

Tools (11)

• assess_product
• doom_prep
• get_assessment
• list_assessments
• list_kb_signals
• list_signal_candidates
• overview
• record_outcome
• retire_signal
• review_signal_candidate
• supersede_calibration_case

Compare: most reliable ml servers · most reliable other servers · most reliable data servers · most reliable knowledge servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Doomscore Doom MCP server down right now?

As of 2026-10-26 09:29 UTC, the Doomscore Doom MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Doomscore Doom MCP server provide?

Doomscore Doom MCP server advertises 11 tools, including assess_product, doom_prep, get_assessment, list_assessments, list_kb_signals.

How do I install Doomscore Doom MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.doomscore.vc

Is the Doomscore Doom MCP server safe to connect to an AI agent?

Glimind scanned all 11 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Doomscore Doom MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.