Quorum MCP server
2026년 11월 12일 커밋공공 아카이브 및 규제 기관의 영구 저장 기록을 통해 주장을 검증 가능한 시장 증거와 소비자 인사이트로 변환합니다.
다른 이름 Godzilla-lab/Quorum-API, quorum-api
- 스타
- 0
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.1.0
- 마지막 커밋
- 2026년 11월 12일
- 라이선스
- Apache-2.0
Quorum MCP란?
공공 아카이브 및 규제 기관의 영구 저장 기록을 통해 주장을 검증 가능한 시장 증거와 소비자 인사이트로 변환합니다.
프로젝트 README에서 생성된 요약
Quorum MCP server 정보
Quorum은 주장을 공공 아카이브 및 규제 기관의 영구 저장 기록과 연결하여 검증 가능한 시장 증거를 제공합니다. 이 시스템은 단순한 요약을 넘어 감사 가능한 데이터가 필요한 개발자와 연구자를 위해 설계되었습니다. 모든 주장에는 고유한 receipt 시스템이 적용되어 안정적인 ID가 함께 제공되며, GET /v1/evidence/{id} 엔드포인트를 통해 원본 소스, 점수 및 영구 링크를 확인할 수 있습니다.
사용자는 CLI, JavaScript 또는 Python SDK, 또는 MCP server를 통해 서비스를 이용할 수 있습니다. 호스팅된 API는 특정 모드에서 API key가 필요한 무료 티어를 제공하며, 셀프 호스팅을 통해 open mode, 키별 인증 및 사용자 정의 할당량을 설정할 수 있습니다. 이 도구는 Reddit, Hacker News 및 다양한 정부 안전 규제 기관을 포함한 10개의 서로 다른 소스를 통합합니다. 많은 소스가 무료이며 키 없이 사용할 수 있지만, Amazon 리뷰나 Meta 광고 라이브러리 액세스를 추가하려면 Apify token이 필요하며, YouTube 데이터는 YouTube Data API v3 key가 필요합니다.
활용 사례
- 1감사 가능한 에이전트 리서치AI 에이전트가 제공된 receipt ID를 확인하여 자신이 내세우는 모든 시장 주장을 독립적으로 검증할 수 있습니다.
- 2제품 불만 사항 분석보고된 모든 결과의 근거가 되는 실제 댓글을 확인하여 구체적인 소비자 페인 포인트를 식별합니다.
- 3경쟁 광고 리서치실제 캠페인 운영 기간을 바탕으로 동영상 광고와 정적 광고의 효과를 비교합니다.
- 4규제 모니터링기업이 정부 안전 규제 기관에 제출한 공식 성명 및 신고 내용을 추적합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Quorum MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Quorum MCP 설치
$ claude mcp add --transport http quorum-api https://quorum-api-j15n.onrender.com/mcpCursor에 Quorum MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"quorum-api": {
"url": "https://quorum-api-j15n.onrender.com/mcp"
}
}
}VS Code에 Quorum MCP 설치
.vscode/mcp.json
{
"servers": {
"quorum-api": {
"type": "http",
"url": "https://quorum-api-j15n.onrender.com/mcp"
}
}
}VS Code CLI에 Quorum MCP 설치
$ code --add-mcp '{"name":"quorum-api","type":"http","url":"https://quorum-api-j15n.onrender.com/mcp"}'Codex에 Quorum MCP 설치
$ codex mcp add quorum-api --url https://quorum-api-j15n.onrender.com/mcpCodex config.toml에 Quorum MCP 설치
~/.codex/config.toml
[mcp_servers.quorum-api] url = "https://quorum-api-j15n.onrender.com/mcp"
Gemini CLI에 Quorum MCP 설치
$ gemini mcp add -s user --transport http quorum-api https://quorum-api-j15n.onrender.com/mcpGemini settings.json에 Quorum MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"quorum-api": {
"url": "https://quorum-api-j15n.onrender.com/mcp",
"type": "http"
}
}
}구성
QUORUM_API_KEYSQUORUM_CORPUSQUORUM_PG_CAQUORUM_PG_URLQUORUM_WEBHOOK_SECRET
| 이름 | 설명 | 유형 |
|---|---|---|
| QUORUM_API_KEYS | — | |
| QUORUM_CORPUS | — | |
| QUORUM_PG_CA | — | |
| QUORUM_PG_URL | — | |
| QUORUM_WEBHOOK_SECRET | — |
자동 검사
2026년 11월 15일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능godzilla-lab/quorum-api is public and reachablegithub.com/godzilla-lab/quorum-api ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-12github.com/godzilla-lab/quorum-api ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답initialize answered with protocol 2025-06-18 in 199 ms통과
README
GitHub에서 보기Quorum
Market evidence with receipts.
Give it a subject, get back what a market actually says. Every claim carries receipt ids, and every receipt id resolves to a real stored record you can fetch back. Fabricated citations are structurally impossible, and a test proves it rather than a README asserting it.
[!TIP] The interesting part is not that it finds evidence. It is that you can check it. Every id in every answer resolves through
GET /v1/evidence/{id}, andPOST /v1/verifywill re-resolve a set of claims against the corpus, ours or anybody else's. An id that does not resolve is a claim that was never real.
{
"finding": "Sizing runs small, and buyers only discover it after delivery",
"corroboration": { "records": 31, "channels": 5 },
"receipts": ["rc_8f2a1", "rc_44b0e", "rc_91c37"],
"confidence": "finding"
}
GET /v1/evidence/rc_8f2a1 returns the actual comment, its score, where it was
posted, when, and its permalink. A customer of your customer can click a claim
and read the human who said it.
The hosted API lives at https://quorum-api-j15n.onrender.com, on a free tier instance that sleeps when idle, so the first request after a quiet spell waits a few seconds for it to wake.
The hosted instance is keyed while the API is early. The API root says how to request a key, and always says which mode the instance you are talking to is in. The health endpoint needs no key, so you can check it is alive right now:
curl https://quorum-api-j15n.onrender.com/v1/healthz
Self hosting supports open mode or per key auth, quotas, tenancy and webhook
secrets, all self served from GET /v1/usage.
[!NOTE] On Windows, the curl bundled with Git Bash uses the Schannel TLS stack, which refuses any HTTPS connection when it cannot reach the certificate revocation servers (
CRYPT_E_REVOCATION_OFFLINE, common behind corporate proxies and VPNs). That is the network, not this API. Add--ssl-revoke-best-effortto the curl command, or call from WSL or PowerShell instead.
Contents
- What it does
- Use cases
- Status
- Requirements
- Quick start
- Usage
- What the API does
- Why this is different
- Documentation
- Contributing
- License
- Acknowledgements
What it does
Voice of customer from public archives, competitor ads ranked by how long they have actually been running, and a video versus static verdict computed as arithmetic rather than opinion. It keeps everything it reads, so the second question about a market is nearly free and the archive can be asked about the past.
Key capabilities
- Receipts, not links. A stable id into a retained corpus, which resolves identically forever, including after the source deletes the original.
- Corroboration as arithmetic. A claim needs at least three independent records before it prints as a finding, and the count travels with it.
- Ten sources behind one interface, from a volunteer Reddit archive and GitHub issue search to four government safety regulators, each degrading rather than failing when unconfigured.
- A corpus that compounds. Cold retrieval measured 596 seconds and about 500 throttled requests. The same category answers in half a second once warm.
- Offline mode that touches no network and costs nothing.
- Fifteen HTTP operations, a typed SDK, an MCP server and a CLI, all the same pipeline.
What it looks like
Real output, excerpted from a cold npx quorum "espresso machine" run on
2026-08-24: 401 records in 227 seconds for $0.00.
EVIDENCE a claim needs 3 independent receipts to be stated as a finding
the percentage is share of all 401 records held for this category
quality 88 receipts / 64 channels 21.9% A0 B3 C85 D0 [finding]
"I often hear the priority list being 1. Quality of beans 2. Quality
of the grinder 3. Quality of the espresso machine..."
hackernews Why a spritz of water before grinding coffee yields
better results rc_4d6d444821b0044f
ATTESTED 7 records from 6 named parties [finding]
A named party stated this to a regulator, on the record, with consequences
for lying. Two of these are a finding on their own.
"CPSC And Krups Announce Action On Espresso Makers..."
cpsc Krups rc_a4883bfb1b04d1c1
RECEIPTS 195 cited, 195 resolved back to real records
COST $0.0000 in 227.3s
Every id in that output is fetchable from the corpus that run wrote. If an id does not resolve, the run exits non zero and says which one.
Use cases
- Product and brand research. What buyers actually complain about, with the comment behind every claim, rather than a summary you have to trust.
- Competitive teardown. One full retrieval per rival, so shares are compared instead of counts, and co-occurrence is never mistaken for a signal.
- Ad creative decisions. Video versus static judged by how long real campaigns ran, from dated observations rather than from a platform's own label.
- Agent tooling that can be audited. An MCP server whose every claim the calling model can independently resolve, which is the one thing a research tool cannot fake.
- Diligence and monitoring. Attested records a named party filed with a regulator, and a diff against the last report for the same subject.
Status
| Engine | Working. 1,330 tests, offline and keyless |
| CLI | Working, every flag |
| MCP server | Working, five tools over stdio, four of them also remote at /mcp |
| JavaScript SDK | Working, 11 methods |
| Python SDK | Published: pip install quorum-api. 14 methods, standard library only |
| Webhooks | Working. Signed to Standard Webhooks, durable, retried for about 75 hours |
| Hosted API | Deployed and live at https://quorum-api-j15n.onrender.com, on PostgreSQL, verified against the running instance |
| npm | Published: npx quorum-api "running shoes". Five packages, zero external dependencies |
| Corpus | Young. 22 consumer and developer categories warmed on the hosted instance as of 2026-08-25; everything else is a cold run away |
[!NOTE] Do not depend on the API shape yet. It is stable enough to build against and not yet frozen.
Named rather than left as a surprise: request quotas are held in memory, so the per minute lookup counter resets on restart and none of the counters would hold across two instances. The hourly report counter is the exception: it is re-seeded from persisted reports at boot, so a restart is not a refill. And
evals/holds only its first layer, a labelled relevance set scored in CI; the paid, scored report evals described in the project docs do not exist yet.
Requirements
Node 22.18 or newer. The engine has one runtime dependency, pg, and
only in the hosted server: no framework, no ORM, no HTTP client, no test runner,
and nothing at all in the CLI or the corpus. That is a deliberate constraint
rather than a boast, because every dependency in a tool that fetches untrusted
text from the public internet is another thing that can reach the network on
your behalf. pg earned its place by being a connection pool that survives a
database restart, which is not a thing worth hand writing.
No key is required for anything. Reddit through a public archive, Hacker News, the App Store, the CFPB consumer complaint database and four government safety archives are all free and keyless. Keys only ever ADD sources (YouTube comments with a free API key, Amazon reviews and the Meta ad library through Apify), and a missing one degrades a run rather than failing it.
QUORUM_YOUTUBE_API_KEY |
A free YouTube Data API v3 key. Comments under review videos join the voice tier; absent, the source reports itself unconfigured and the run proceeds without it. Costs nothing: the free daily quota covers dozens of runs. |
QUORUM_CONTACT_EMAIL |
Not a key. The SEC requires a User-Agent naming who is calling and returns 403 without one, so sec-edgar reports itself unconfigured until this is set. A role address outlives whoever set it up. |
OPENROUTER_API_KEY |
Subject expansion, --synthesise and --read-images. All three are off by default, and the counts never come from a model, so the deterministic report is identical without it. |
APIFY_TOKEN |
The two metered legs: the Meta ad library and Amazon reviews, both through the same Apify account. Every call charges the cost meter and lands on the report's bill. Absent, both legs are skipped, exactly as --no-ads does for ads. |
QUORUM_CORPUS |
SQLite corpus path, read by the server and the MCP server. Default ./quorum.db. The CLI does not read it: pass --corpus instead. |
QUORUM_PG_URL |
Postgres, for the hosted corpus. Paste the provider uri whole: it is parsed rather than split, so sslmode is honoured and a password containing @ survives. |
QUORUM_PG_CA |
Path to the provider CA. Worth setting, because sslmode=require means encrypt and not verify. |
QUORUM_PG_CA_PEM |
The same CA as an inline PEM, for hosts that supply secrets as values rather than files. |
QUORUM_API_KEYS |
Comma separated bearer keys for the server. Absent means the instance is open, which the server says out loud on boot. |
QUORUM_WEBHOOK_SECRET |
Signing secret for webhook delivery, 24 characters or more. Absent means webhooks are accepted and never delivered, which the server also says on boot. |
QUORUM_CONCURRENCY |
Concurrent report runs, default 2. Not a throughput dial: every concurrent run is concurrent pressure on the same volunteer archives. |
PORT |
Default 8787. A host normally sets this. |
QUORUM_REPORTS_PER_MINUTE |
Reports one key may start per minute. Default 20. |
QUORUM_LOOKUPS_PER_MINUTE |
Everything else, per key per minute. Default 600, which is 10 a second. |
QUORUM_MAX_CAP_USD |
Ceiling on any one report. A caller's own capUsd can only lower it. Default 0. |
QUORUM_SPEND_PER_KEY_USD |
What one key may spend on metered sources per day. Default 0. |
QUORUM_SPEND_TOTAL_USD |
What every key together may spend per day. Default 0. |
Quick start
Requires Node 22.18 or newer, and nothing else.
npx quorum-api "running shoes"
That is the whole install. Five packages come down from npm, about 240 KB with zero external dependencies, and the first report starts.
Working on Quorum itself is the clone path:
git clone https://github.com/Godzilla-lab/Quorum-API && cd Quorum-API
npm install
npm run build
npm test # 1,330 tests, offline, no keys
Then research something. The input is a subject, not a URL. Plain text works, a product URL works, and a product URL the store refuses still works, which matters because four of four real store pages blocked a server side fetch when this was measured.
npx quorum "running shoes" --offline # corpus only, no network, no cost
npx quorum "running shoes" --offline --corpus ./mine.db # somewhere else
[!NOTE] Nothing above needs a key, and
--offlinenever touches the network at all. Start with none of them and add one when a report tells you what it could not reach.
Usage
CLI
The whole engine on your machine, against a corpus you own.
# A subject in plain words
npx quorum "running shoes" --communities running,runningshoegeeks
# A product url, including one a store refuses to serve to a server
npx quorum "https://allbirds.com/products/mens-wool-runners"
# Corpus only. No network, no cost, and it says so
npx quorum "running shoes" --offline
# Machine readable. Progress goes to stderr, so this pipes cleanly
npx quorum "running shoes" --json | jq '.findings[].term'
# Versus what: one full retrieval per rival
npx quorum "wool runner" --compare "brooks ghost"
# Skip the one metered source explicitly
npx quorum "running shoes" --no-ads
--compare is one full retrieval per rival, and it has to be. Counting records
in one corpus that happen to mention a rival measures co-occurrence: a comment
saying "these run smaller than my Brooks" names a rival and a complaint and
attributes the complaint to neither. So every side is a corpus of its own,
shares are compared rather than counts, and a gap inside the sampling noise for
those corpus sizes is reported as no difference rather than as a result.
Every claim it prints is either a finding, meaning at least three independent receipts stand behind it, or a weak signal, which is shown so it can be chased and is never stated as a market pattern. Before anything is printed, every cited receipt is fetched back out of the corpus, and the run exits non zero if one of them does not resolve.
quorum --help lists the flags. Every command above works through
npx quorum-api with nothing cloned, or through the quorum bin inside a
checkout; they are the same binary.
HTTP API
Start a report, poll it, then resolve the ids it cites.
# Start one. Returns 202 immediately with an id
curl -sX POST http://localhost:8787/v1/reports \
-H "authorization: Bearer $KEY" \
-H 'content-type: application/json' \
-d '{"subject":"wool runner","terms":["sizing","durability"]}'
{ "id": "rep_3568995af829290a", "status": "running", "coalesced": false,
"category": "wool runner", "queuePosition": 1, "estimatedSeconds": 60 }
# Poll it. Honours Retry-After while running, and ETags so polling costs nothing
curl -s http://localhost:8787/v1/reports/rep_3568995af829290a \
-H "authorization: Bearer $KEY" -H 'if-none-match: "rep_3568995af829290a-7"'
# Watch it instead of polling
curl -N http://localhost:8787/v1/reports/rep_3568995af829290a/stream \
-H "authorization: Bearer $KEY"
# Resolve one receipt. This is the endpoint everything else rests on
curl -s http://localhost:8787/v1/evidence/rc_a8697befab91e873 \
-H "authorization: Bearer $KEY"
# Resolve up to 200 at once, because a report cites more than one
curl -sX POST http://localhost:8787/v1/evidence/batch \
-H "authorization: Bearer $KEY" -H 'content-type: application/json' \
-d '{"receiptIds":["rc_8f2a1","rc_44b0e","rc_91c37"]}'
# Is this category warm? Free, and worth asking before paying for a cold report
curl -s http://localhost:8787/v1/categories/running%20shoes \
-H "authorization: Bearer $KEY"
# Check somebody's claims, ours or a competitor's
curl -sX POST http://localhost:8787/v1/verify \
-H "authorization: Bearer $KEY" -H 'content-type: application/json' \
-d '{"claims":[{"text":"sizing runs small","receipts":["rc_8f2a1"]}]}'
JavaScript SDK
Typed, zero dependency, written against spec/openapi.yaml.
Every method is one operationId from that file.
import { createClient } from '@quorum/sdk-js';
const quorum = createClient({ baseUrl: 'https://quorum-api-j15n.onrender.com', apiKey: process.env.QUORUM_KEY });
const found = await quorum.searchEvidence({ query: 'sizing', category: 'running shoes' });
if (!found.ok) throw new Error(found.error.message);
for (const record of found.data.records) console.log(record.receiptId, record.text);
Errors are values, never thrown, the same rule the engine follows anywhere a
vendor can be down. A caller gets { ok: false, error } carrying the server's
type, its requestId and any retryAfterSeconds, because a 429, a 503 and a
report that is simply not finished yet are all normal and none of them is
exceptional.
It honours the server's pacing. waitForReport polls to completion using
Retry-After when the server sends one, and treats a 503 as the load shedder
rather than a failure. A client that gives up on the first refusal reports a busy
service as a broken one, which is exactly what the shedder exists to prevent.
const started = await quorum.createReport({ subject: 'wool runner', offline: true });
if (started.ok) {
const report = await quorum.waitForReport(started.data.id, {
onPoll: (r) => console.log(r.status),
});
}
streamReport returns the same run as an async iterable of server sent events,
parsed by hand because there is no EventSource in Node that accepts an
Authorization header.
Python SDK
The same client in Python, in packages/sdk-py, written
against the same spec with the same two decisions: errors are values, never
raised, and wait_for_report honours Retry-After so a busy service is not
reported as a broken one. Standard library only, no dependencies, and the
transport is injectable so its tests run with no network.
pip install quorum-api
from quorum_api import QuorumClient
quorum = QuorumClient("https://quorum-api-j15n.onrender.com", api_key="qk_...")
started = quorum.create_report("wool runner", offline=True)
if started.ok:
report = quorum.wait_for_report(started.data["id"])
MCP server
Five tools spoken as JSON-RPC with no dependency, over two transports.
Remote, for connector forms that want a URL. The hosted instance answers Streamable HTTP at:
https://quorum-api-j15n.onrender.com/mcp
Open without a key: the read tools spend nothing and serve public data, and
anonymous callers share one rate allowance so they cannot crowd out keyed
customers. On a subject nothing is held for, research_product starts a
harvest and returns at once; records are searchable as they land, so
search_evidence and category_warmth answer while the run continues and say
so. The public door runs one harvest at a time and at most three an hour; a
key gets the ordinary report allowance. Ads and synthesis never run from it.
Local, over stdio, for clients that launch a command:
QUORUM_CORPUS=./quorum.db node packages/mcp/src/bin.ts
{
"mcpServers": {
"quorum": {
"command": "node",
"args": ["packages/mcp/src/bin.ts"],
"env": { "QUORUM_CORPUS": "./quorum.db" }
}
}
}
| tool | answers |
|---|---|
search_evidence |
How many independent records exist, across how many channels, whether that clears the threshold, and the loudest few quotes |
get_receipt |
Resolves ids to the real records. This is how an agent checks us |
category_warmth |
Whether asking is instant and free, or minutes and expensive |
compare_formats |
Video versus static, from how long real ads ran |
research_product |
Remote: starts a harvest and returns at once. Local: a full report, off unless QUORUM_MCP_RESEARCH=1 |
Three decisions worth knowing, because the tool schema is the expensive part to change later:
Five tools, not one per endpoint. A tool definition costs 100 to 500 tokens on every turn, so a server mirroring ten routes spends the context window before the model has done anything.
Aggregated, never a row dump. search_evidence returns counts and a handful
of quotes. A research tool that streams a corpus into a context window has spent
the budget it was meant to save.
Markdown, not JSON, at roughly 60% of the tokens for the same content.
research_product is off by default because a report is minutes of throttled
retrieval against volunteer archives, and an agent should not be able to start
one by accident. The other four answer from what is already held and touch no
network.
The payoff is a thing no other research server can offer: the calling agent can
independently verify every claim. search_evidence cites ids and get_receipt
resolves them, so an id that does not resolve is a claim that was never real, and
it is the loudest line in the response when it happens.
Quorum MCP 질문
Quorum MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http quorum-api https://quorum-api-j15n.onrender.com/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Quorum MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
도구가 제시하는 주장을 어떻게 검증할 수 있나요?
모든 주장에는 GET /v1/evidence/{id} 엔드포인트를 통해 확인할 수 있는 receipt ID가 포함되어 있으며, POST /v1/verify를 사용하여 코퍼스를 대상으로 주장을 다시 검증할 수 있습니다.
도구 사용을 위해 API key가 필요한가요?
아니요, Reddit, Hacker News, 정부 안전 아카이브와 같은 많은 소스는 무료이며 키가 필요하지 않습니다. YouTube, Amazon, Meta와 같은 특정 소스를 추가할 때만 키가 필요합니다.