Research MCP

Official registry Search and web

Cited research MCP (MCP+agent infra): brief, lookup. Fail=$0.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http research-mcp 'https://mcp.researchmcp.dev/mcp' --header 'Authorization: <Bearer API key from prepaid checkout>'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "research-mcp": {
            "type": "http",
            "url": "https://mcp.researchmcp.dev/mcp",
            "headers": {
                "Authorization": "<Bearer API key from prepaid checkout>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. research-mcp
  2. Marketing site (Cloudflare Pages)
  3. MCP URL (production)
  4. Auth
  5. Privacy (demand signals)
  6. Pricing (locked)
  7. When to call each tool
  8. Published contract
  9. Quickstart (local)
  10. Env (high-signal)
  11. Tests
  12. Layout
  13. Discovery
  14. Ops

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)

https://mcp.researchmcp.dev/mcp

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)

{
  "mcpServers": {
    "research-mcp": {
      "url": "https://mcp.researchmcp.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Auth

Every /mcp and /billing/credits request:

  • Authorization: Bearer <key> or
  • X-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)

PackCredits
$10 starter1000¢
$25 standard2500¢
$50 pro5000¢
Meter (billable success)Price
lite (source_lookup, research_brief depth=quick)$0.25
standard (research_brief depth=standard)$0.60
deep (preview only)$1.50 published meter; preview path always $0

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)
ToolCall whenDo not
research_briefYou need cited, query-tied excerpt packs on AI infra / MCP / security. depth=quick ($0.25) or depth=standard ($0.60).Do not use depth=deep (parked / sample only unless preview flag).
source_lookupYou have one URL or claim to fetch/verify. Lite $0.25.Do not use as open-web search or multi-source synthesis.

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)
Tool / pathBehavior
compare_optionsRegistered only with the flag. Always $0 / billable=false. No live path — prefer research_brief.
depth=deepAllowed only with the flag. Always $0. Soft-reserve never demands full deep SKU.

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

Quickstart (local)

cd /workspace/research-mcp
npm install && npm run build
API_KEYS=dev-key-1 npm start
# optional live brief path:
LIVE_RESEARCH=1 API_KEYS=dev-key-1 npm start
curl -s http://127.0.0.1:3000/health
curl -s -X POST http://127.0.0.1:3000/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Authorization: Bearer dev-key-1' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Env (high-signal)

VarNotes
API_KEYSBreak-glass keys (comma-separated)
LIVE_RESEARCH=1Live search→extract→synthesize→quote gate for quick/standard
ENABLE_PREVIEW_TOOLS=1Register compare + allow deep (always $0)
DATABASE_URLSQLite ledger for customer keys / credits
Stripe STRIPE_* / pack price IDsPrepaid Checkout (test until go-live)

Tests

npm run eval:all      # goldens + off-golden + pipeline
npm run test:billing  # ledger / webhook / credits meter

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_gate
  • docs/contract/ — published JSON Schema + examples
  • ARCHITECTURE.md — transport / auth / metering

Discovery

Homepage for listings: **https://researchmcp.dev**, not Smithery.

Ops

See RUNBOOK.md. License: MIT.

Frequently asked questions

What is Research MCP?

Cited research MCP (MCP+agent infra): brief, lookup. Fail=$0.

How do I install Research MCP?

It runs as a remote server. In Claude Code: claude mcp add --transport http research-mcp 'https://mcp.researchmcp.dev/mcp' --header 'Authorization: <Bearer API key from prepaid checkout>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Research MCP need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is Research MCP open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Research MCP?

It is published by research-mcp-hq. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.