# chefcohen/corroborate-mcp [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/chefcohen/corroborate-mcp  
**GitHub Stars:** 1  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/chefcohen-corroborate-mcp

## Description
Tells AI agents how independently a claim is being reported: syndication-aware source counting (a wire story reprinted by 40 outlets counts as one origin), 0-1 confidence scores, and published error rates in-repo. Measures corroboration, not truth — no stance detection. Keyless, no accounts. Install: npx -y corroborate-mcp.

## Tools
Capabilities this server exposes over MCP:

- **corroborate_claim** — Given a factual/news claim, returns how INDEPENDENTLY it is being reported. Use before relying on a current-event claim. Output: verdict (CONFIRMED = 2+ independent origins | SINGLE_SOURCE | UNCORROBORATED), count of independent story origins (wire/syndication echoes collapse to one), per-source evidence (outlet, domain, url, date), confidence 0-1, coverage flag, honest caveats. Measures REPORTING corroboration, not truth — no stance detection, so a distorted claim about a real event may still show coverage; verify specifics against the returned sources. Keyless, read-only, deterministic; if all sources are unreachable it errors rather than returning a false negative.
- **find_sources** — Multi-engine news/source search (Google News, GDELT, Hacker News) for a query: a deduped list of {outlet, domain, url, date}. Use when you want raw coverage to judge yourself, not a scored verdict — the cheaper primitive under corroborate_claim. Keyless, read-only.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "corroborate-mcp": {
    "command": "npx",
    "args": ["-y","corroborate-mcp"]
  }
}
```

## Documentation

## What chefcohen/corroborate-mcp does

The chefcohen/corroborate-mcp MCP server measures reporting corroboration rather than truth. Give it a factual or news claim, and it searches multiple public sources to estimate how many independent story origins address that claim. Syndicated or near-identical reports are grouped so that many copies of one wire story do not appear to be many independent confirmations.

The main result uses three verdicts:

- `CONFIRMED`: at least two independent story origins were found.
- `SINGLE_SOURCE`: one independent origin was found.
- `UNCORROBORATED`: no qualifying origin was found.

Results include the independent-source count, confidence from 0 to 1, coverage status, source details, and notes about limitations such as syndication, relevance filtering, or engine outages. A confirmed result means that the topic has independent reporting; it is not a factual guarantee.

## How it works

The chefcohen/corroborate-mcp MCP server searches Google News RSS, GDELT, and Hacker News in parallel. It extracts keywords from the claim while preserving quoted phrases, then applies a relevance check to avoid counting articles that only loosely relate to the subject.

Relevant results are clustered by headline similarity. Domains carrying substantially the same story can therefore count as one origin, while distinct reporting may count separately. Wire-service origins are identified in the source evidence. Confidence increases with the number of origins and agreement between search engines, and can decrease when a single story is echoed widely.

The default recency window is seven days, and callers can request a different window up to 90 days. Because the process does not use an LLM, identical evidence produces deterministic judgments.

## Setup and configuration

Node.js 18 or newer is required. No API keys, accounts, or configuration values are needed. Start the server over stdio with:

```bash
npx -y corroborate-mcp
```

An MCP client can register `npx` as the command, with `-y` and `corroborate-mcp` as its arguments. The README provides configurations for Claude Desktop and Cursor, and also shows a Claude Code registration command. The package can be run without an MCP client for a basic stdio health check.

## Tools and capabilities

`corroborate_claim` accepts a claim plus optional `window_days` and `max_sources` values. It returns the verdict, independent-origin count, confidence, coverage state, per-source outlet and domain information, URLs, publication dates, wire indicators, and explanatory notes. If every search engine is unreachable, it returns an error instead of treating missing results as evidence that the claim is unsupported.

`find_sources` accepts a query with optional recency and source-count limits. It returns a deduplicated list of outlets, domains, URLs, and dates without assigning a verdict. Use it when an agent needs to inspect the available coverage directly or apply its own judgment.

## Limitations and notes

The chefcohen/corroborate-mcp MCP server does not perform stance detection. A distorted claim about an event that is genuinely being reported can still receive `CONFIRMED`, so returned sources must be checked for the exact details. It works at the English-language, headline level and does not fetch paywalled article bodies.

Results are constrained by the selected time window. An old claim may be labeled `UNCORROBORATED` simply because its coverage falls outside that window. Independent rewrites can occasionally be grouped incorrectly or counted separately, and search-engine outages can reduce coverage. The project reports published benchmark results and identifies these weaknesses rather than presenting corroboration as proof of truth.

## Getting started with this chefcohen/corroborate-mcp MCP server
Always refer to the official documentation for the most accurate and up-to-date information.

_Full upstream README: https://allmcps.com/mcp/chefcohen-corroborate-mcp/readme_