
Research MCP
io.github.research-mcp-hq由 GitHub 帳號 research-mcp-hq 發布v0.1.2更新於 Oct 24, 2026
Cited research MCP (MCP+agent infra): brief, lookup. Fail=$0.
概覽
付費遠端 MCP 伺服器,讓助理取得附引用的研究簡報與單一來源查核,聚焦 AI 基礎設施、MCP 與安全主題。
- 可以做什麼
- 針對 AI 基礎設施、MCP 與安全主題產生附引用、與查詢綁定的摘錄包,可選快速或標準深度,回傳摘要、正文、信心度、來源、缺口與截止日期。抓取並驗證單一 URL 或論述,回傳相同結構並附上論述與摘錄。當引文無法在來源 URL 上通過驗證時拒絕該次執行,且不計費。透過計費額度端點查詢預付餘額與公開價目表。
- 適用情境
- 當助理需要關於 AI 基礎設施、MCP 或安全的可引用、有出處的調研,或需要驗證單一 URL 或論述,且使用者願意依成功呼叫從預付餘額付費時使用。
- 執行需求
- 遠端 streamable HTTP 端點,無需本機安裝。需要預付結帳取得的 bearer API 金鑰,放在 Authorization 標頭中(也接受 X-API-Key 標頭)。需要能連線至託管端點的網路。額度須事先購買。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Research MCP,將其新增到工作區。
- 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.research-mcp-hq%2Fresearch-mcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"research": {
"type": "http",
"url": "https://mcp.researchmcp.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
research-mcp
Paid cited research remote MCP for coding / research agents (API key auth, not OAuth).
Why pay: query-tied excerpt packs from allowlisted primaries; refuse uncited — that call is $0. Prepaid packs; meters only on billable successes.
Repo may be private; treat this README as the agent-facing contract. Live Fly host is unchanged.
Marketing site (Cloudflare Pages)
Source of truth: research-mcp-hq/www (public/). Live site: https://researchmcp.dev.
The www/ tree in this repo is a stub / mirror note only — do not point Cloudflare Pages here. MCP API origin remains on Fly; branded install URL is https://mcp.researchmcp.dev/mcp.
MCP URL (production)
Health: https://mcp.researchmcp.dev/health
Server card: https://mcp.researchmcp.dev/.well-known/mcp/server-card.json
Credits meter: GET https://mcp.researchmcp.dev/billing/credits (auth’d)
Auth
Every /mcp and /billing/credits request:
Authorization: Bearer <key>orX-API-Key: <key>
Keys: prepaid customer key (from Checkout success page) or break-glass API_KEYS (ops; no ledger debit).
Privacy (demand signals)
We log category mix (tool, topic bucket, host, billable vs fail=$0) — not your questions. Opt-in via DEMAND_LOG=1 on the server; default off.
Pricing (locked)
fail = $0: sample/demo, quote-gate fail, density fail, COGS abort, cancel, depth-mismatched golden, preview/parked paths (meta.billable=false, charge_usd=0).
Inspect balance + tables: GET /billing/credits → balance_cents, packs, meters_usd, fail_usd: 0. Break-glass returns { break_glass: true, balance_cents: null } (no fake balance).
When to call each tool
Live (default paid surface)
Both return the shared envelope: tldr, body, confidence, sources, gaps, as_of, plus schema_version (2026-09-14). Optional fail_gate: { reason, retryable }, claims / excerpts, retrieved_at. If quotes fail verification on source_url, the run is refused and not billed.
Preview / parked (ENABLE_PREVIEW_TOOLS=1)
Without the flag: compare_options is not registered; depth=deep is rejected (preview_required). Directory card still says do-not-call for compare/deep.
No stub billing. No 25-tool kitchen sink — two live tools by default.
Published contract
- Schema:
docs/contract/schema.json - Examples:
docs/contract/examples/happy-research-brief.json,fail-gate.json - HTTP header on responses:
X-Research-MCP-Schema-Version: 2026-09-14 - Tool notes:
docs/TOOLS.md
Quickstart (local)
Env (high-signal)
Tests
Layout
src/server.ts— tool registration (finish-or-hide)src/billing/credits.ts—GET /billing/credits(T10 visible meter)src/contract.ts—schema_version+fail_gatedocs/contract/— published JSON Schema + examplesARCHITECTURE.md— transport / auth / metering
Discovery
Homepage for listings: https://researchmcp.dev, not Smithery.
Ops
See RUNBOOK.md. License: MIT.
來源:README.md,提交 15ce435
工具
0版本歷史
1- v0.1.2最新Sep 16, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分