Claim-level verification

Verify a list of people, inside n8n

Give it names and employers. It gives you back one cited verdict per person — verified, partially verified, could not verify, or contradicted by the record — and for every finding it names the public register that produced it, prints the exact search run against it, and links the record with its date. The gaps come back too, each with the link that settles it by hand.

Download the workflow

Five minutes, from nothing

  1. Open MentionFox at https://mentionfox.com/mcp once and connect. That issues the token this workflow uses.
  2. In n8n, Workflows → Import from File, and pick the file above.
  3. Open the Check them node. Under Credentials, create a Header Auth credential: name Authorization, value Bearer YOUR_TOKEN.
  4. Open the Your list node and replace the two example people with yours.
  5. Press Execute. One row comes back per person.

What a row looks like

{
  "subject": "Brian Armstrong",
  "employer": "Coinbase",
  "verdict": "partially_verified",
  "findings": [
    {
      "register": "SEC EDGAR company filings",
      "outcome": "confirmed",
      "confidence": "inferred",
      "search_performed": "Searched SEC EDGAR for insider filings (Forms 3, 4 and 5) naming
                           \"Brian Armstrong\" as an officer, director or major holder of Coinbase.",
      "record": "127 such filings; most recent Form 4 filed 2025-06-27.",
      "record_url": "https://www.sec.gov/cgi-bin/browse-edgar?..."
    }
  ],
  "not_checked": [
    { "source": "Identity documents", "why": "We did not see or verify any identity document.",
      "do_it_yourself": null }
  ]
}

If you prefer the MCP node

n8n's MCP Client Tool works too. Point it at https://mentionfox.com/mcp and use Bearer authentication. If your n8n version offers a transport dropdown, either setting connects: the endpoint answers a streaming open on GET and JSON-RPC on POST.

What it costs, and what it will not do

A check costs credits, and the tool tells you the cost before it runs. If the balance will not cover it, nothing is searched, nothing is charged, and the refusal says both numbers. See pricing.

It never concludes that somebody is fake. No public register holds identity itself, so the strongest honest verdict is partially verified: a named register lists somebody matching the claim. “Could not verify” means one search, on one day, in one register, came back empty — and most people are absent from most registers.

MentionFox · What this is · Pricing