Corroborate MCP vs Agent Search 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.

free_search

Quick public-web search for current facts and discovery. Use free_search_advanced for verification or domain filters. Use free_extract for one selected URL. Returns compact multi-source evidence with confidence, relevance, source_count, stop_reason, evidence_budget, and partialFailures. Provider families are counted once even when several adapters use the same upstream. Optional API providers run only when credentials and policy allow. @readOnly true @idempotent true — makes outbound HTTP requests to configured search engines. Injection detection and SSRF protection active.