vulns.co
/
GKData.io MCP
RE / Research

Skeptical review

Stress-test a lead against benign explanations and missing proof before time or impact claims grow around it.

Guide 20 / 223 review notesUpdated 2026-10-12

The review

What to look for

Defensive study and review of artifacts supplied by their owner. Record missing evidence as an open question.

  1. Retrieve the evidence trail

    Use search_hunt_records to collect the lead, linked checks, asset provenance, and evidence references before interpreting the result.

  2. Test the inference

    List the strongest alternative explanation and the specific evidence it would predict. Use upsert_lead to preserve missing proof and uncertainty without rewriting observations.

  3. Choose the smallest next test

    Record an authorized discriminator with record_check, or use next_actions to compare it with other evidence gaps. Hosted research may supply public context only; private artifacts stay local.

What to produce

  • Evidence trail and alternative explanation
  • Preserved uncertainty
  • Minimal discriminating next action

Common mistakes

  • Confusing correlation with a boundary failure
  • Discarding failed or blocked checks
  • Sending private artifacts to the hosted MCP

Use with MCP

Take this into the workbench.

The hosted MCP reads public research. The separate local Hunt Workbench saves private project records in your chosen directory.

Public context

get_research_context search_research get_research_record

Local record tools

search_hunt_records upsert_lead record_check next_actions

Connection and local install guide ↗

Continue the study

Reading & source context

Editorial notes above connect these references. Open each record for its original source and review date.

Visual models

Connected disclosures

From the field toolkit

Guide by GK Data · Research snapshot 2026-10-04.
Sources and review dates are preserved in the library provenance.

Next skillFinding reporting →