Analytics
doomscore.vc
Assesses and monitors product obsolescence risk through prep, assessment, and polling.
ENDPOINT 1
https://mcp.doomscore.vc
MCP server metadata
- Name
- doom
- Version
- 0.1.0
Known tools 11
list_kb_signalsList the active (signed, grounding) roadmap signals with their ids — use to find a signal_id to retire.
Inferred read-onlysupersede_calibration_caseUNLEARN a calibration case whose label turned out wrong or obsolete — retires it (active=false) so the recalibration gate stops scoring it.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.doom]
url = "https://mcp.doomscore.vc"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"doom": {
"type": "http",
"url": "https://mcp.doomscore.vc"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: doom
Remote MCP URL: https://mcp.doomscore.vc
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"doom": {
"url": "https://mcp.doomscore.vc"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"doom": {
"type": "http",
"url": "https://mcp.doomscore.vc"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "doom",
"transport": "streamable-http",
"url": "https://mcp.doomscore.vc"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for doomscore.vc was fetched 2026-07-26T21:08:43.487Z and is being refreshed.
doomscore.vc is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.