EveryInfra Research — Multi-source fact checking with explicit evidence gaps

简体中文 · Setup · Workflow · Prompts · Capability reference · API documentation

EveryInfra Research is a standalone agent skill for multi-source fact checking using EverySearch MCP. It scopes a current claim, compares original sources and dates, and produces a cited conclusion with contradictions and evidence gaps made explicit.

A credible research answer needs more than several links. EveryInfra Research frames one concrete claim, keeps dates and jurisdiction attached, compares original sources and separates agreement from contradictions or missing evidence before writing the conclusion.

Use it when the deliverable is a defensible answer to a current question, not merely a search-result list. This standalone skill calls EverySearch directly; a separate EverySearch plugin is not required.

What you can do

• Check whether a product or policy claim is true for a specified date and version.
• Compare primary sources that disagree and explain the unresolved boundary.
• Produce a source-linked answer with a confidence level justified by the retrieved evidence.

Quick start

This is a standalone, one-skill MCP workflow package, not a new API service. It requires a compatible agent host and the configured access described in setup. Local package validation does not establish live API availability.

Install the source repository in Codex after reviewing its contents. These commands add a GitHub-backed repository catalog, not an official marketplace endorsement:

codex plugin marketplace add everyinfra/everyinfra-research-plugin
codex plugin add everyinfra-research@everyinfra-research-plugin

For a local checkout, replace the first command's source with .. Setup also covers Claude Code and the separate service connection.

Configure access once, then ask:

Verify this current product claim as of the date I provide. Prefer original documentation and separate confirmed facts from gaps.

This initial prompt is scoped to inspection or preparation. Review any paid operation or external side effect before proceeding. Claude Code instructions and Cursor packaging boundaries are in setup.

How the workflow works

1. Write the concrete claim or decision question, preserving date, jurisdiction, version and site scope.
2. Discover everyinfra_search and the live crosscheck schema.
3. Keep retrieval mechanisms distinct. Do not count duplicated keyword searches as independent corroboration.
4. Inspect original URLs and source dates; distinguish publication date from event date when relevant.
5. Report agreement, contradictions and gaps, then state a conclusion no stronger than the evidence allows.

What a useful result contains

A concise claim, scoped conclusion, supporting original links, relevant dates and an explicit uncertainty section. The workflow should make it possible for a reader to inspect why the conclusion follows.

When to use this skill

EverySearch retrieves material. Research adds claim definition, source comparison and evidence-calibrated conclusions. It does not replace professional judgment in high-stakes decisions.

Limits and safety

• An unavailable or empty retrieval path is uncertainty, not proof that a claim is false.
• Independent mechanisms do not automatically mean independent publishers or underlying evidence.
• No guarantee that every current claim can be resolved, and no invented confidence percentage.

The package contains one skill and does not grant permissions or register a duplicate MCP connection. Never put credentials in prompts, checked-in files, screenshots or shared logs. Discovery, API execution, billing and a final external result are separate states. See security.

Frequently asked questions

Why is this separate from search?

The output is different: a judged, cited conclusion with contradictions and gaps, rather than retrieved pages alone.

Do three links count as three independent sources?

Not necessarily. Several pages may repeat one announcement. Inspect the original evidence and distinguish retrieval diversity from source independence.

What if crosscheck is unavailable?

Disclose the limitation. A narrower available search may still help, but it must not be presented as an equivalent cross-check.

Validate and contribute

python3 scripts/validate.py

This offline check validates packaging, local documentation links, the single-skill boundary, metadata and fixtures. It does not send messages, allocate resources or verify a production account. Contribution guidance and the release checklist describe the remaining checks.

Source publication, tagged releases, official marketplace acceptance and live service verification are separate milestones. Maintained by EveryInfra. Licensed under Apache-2.0.