
QuReDec
io.github.Advanced-Binary-OperationsPublished by GitHub account Advanced-Binary-Operationsv0.1.1Updated Oct 24, 2026
Evidence-backed decision briefs with citations — recommendation, confidence, risks, sources.
Overview
Lets an assistant submit a question to QuReDec and retrieve a structured, evidence-backed decision brief with citations, confidence, risks, and actions.
- What you can do
- Exposes three tools: decision_brief submits a question and returns a structured brief; get_brief_status polls an in-progress brief by ID; list_recent_briefs lists the caller's recent briefs. A completed brief includes an executive summary, a recommendation, a confidence score, key facts with citation IDs, implications, actions with effort and impact, risks with severity and citations, and a citation list with titles, URLs, and source types. Briefs typically take two to five minutes, and the tool blocks and polls by default.
- When to use it
- Useful when you want an assistant to produce a cited recommendation on a decision question rather than an unsourced answer, and to keep a history of past briefs. It fits research and evaluation questions where a confidence score, risks, and source citations matter.
- Requirements
- A local Python environment with the quredec-mcp package installed, plus a QuReDec API key supplied as the QUREDEC_API_KEY environment variable. Network access to the QuReDec API is needed unless QUREDEC_MOCK=1 is set for offline development. QUREDEC_BASE_URL can override the API host.
Installation
In SourceWeft
- Open QuReDec in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
QuReDec MCP Server
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 (
/api/v1/brief*, per-user Bearer-token auth). SetQUREDEC_MOCK=1for offline development.
What this does
The completed brief contains: executive_summary, recommendation,
confidence (0–1), key_facts[].citation_ids, implications[], actions[]
(with effort + impact), risks[] (with severity + citation_ids),
and citations[] (with citation_id, title, url, source_type).
Install
Or from source:
Configure
Generate a QuReDec API key at https://quredec.com/account → API keys. Each key is shown to you exactly once at creation; copy it into a password manager immediately.
Add to your MCP client config (Claude Desktop example):
Optional env vars:
QUREDEC_BASE_URL— defaults tohttps://quredec.com.QUREDEC_MOCK=1— run against an in-process mock for development.
Usage example
In Claude Code or Claude Desktop:
Use the
decision_brieftool to evaluate "Should I migrate from Stripe to LemonSqueezy?"
The brief comes back with: recommendation, confidence score, key facts with inline citation ids, risks, recommended actions, and a public share URL. Briefs typically take 2–5 minutes; the tool blocks and polls by default (timeout 600 s) and falls back to a synthetic running status with a poll hint if the timeout fires.
Pricing
The MCP server is free. Briefs consume credits from your QuReDec account:
- Starter $4.99 — 3 briefs (one-time)
- Pro $49/mo — 30 briefs/mo
See https://quredec.com/pricing.
Development
Unit tests run against the in-process mock (no network, no key required):
Run the server locally against the mock:
Live integration test
scripts/integration_test.py exercises the full path against quredec.com:
submit → poll → assert brief schema → list. It consumes 1 credit from the
account whose key you pass in, so run it sparingly.
Optional env vars:
QUREDEC_BASE_URL— defaults tohttps://quredec.com.QUREDEC_QUESTION— override the default seed question.QUREDEC_TIMEOUT— poll timeout in seconds (default 600).
Exit code 0 on full pass, 1 on the first failed assertion.
License
MIT — see LICENSE.
Maintainer
Advanced Binary Operations LLC · [email protected]
Source: README.md at commit 62c8a2d
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts