Evidence-backed decision briefs with citations — recommendation, confidence, risks, sources.
Run a structured QuReDec decision brief from inside Claude Code, Claude Desktop, Cursor, or any MCP-compatible client. Status: alpha (2026-04-30). Wired to the live QuReDec public API (, per-user Bearer-token auth). Set for | Submit a question; receive a structured, evidence-backed decision brief with citations | | Poll an in-progress brief by ID | | List the caller's recent briefs | The…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Run a structured QuReDec decision brief from inside Claude Code, Claude Desktop, Cursor, or any MCP-compatible client. Status: alpha (2026-04-30). Wired to the live QuReDec public API (, per-user Bearer-token auth). Set for | Submit a question; receive a structured, evidence-backed decision brief with citations | | Poll an in-progress brief by ID | | List the caller's recent briefs | The completed brief contains: , , (with + ), (with + ), Generate a QuReDec API key at → API keys. Each key is…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.