CF Exclusion Check

Is this person or business excluded from federal healthcare or government programs?

What this answers

Screens a name or identifier against two federal sources: the HHS-OIG List of Excluded Individuals and Entities (LEIE) and the SAM.gov exclusions list. Match by name, NPI, UEI or CAGE. Every result states a confidence level and the exact basis it matched on — an NPI hit, a full-name hit, or a weaker surname-plus-initial hit — and, when a subject was later reinstated, says so instead of just reporting "no match."

Example

curl "https://exclusions.cfsoft.us/v1/check?name=Smith,%20John&state=TX"
{
  "verdict": "excluded",
  "confidence": "match",
  "match_count": 1,
  "subject_count": 1,
  "matches": [{
    "confidence": "match",
    "basis": "full_name",
    "record": {
      "source": "leie", "last_name": "SMITH", "first_name": "JOHN",
      "state": "TX", "exclusion_type": "1128a1",
      "exclusion_date": "20180501", "currently_excluded": true
    }
  }],
  "coverage": { "complete": true }
}

Pricing

EndpointPriceNotes
/v1/check$0.05verdict, confidence, basis, reason per match
/v1/report$0.50every match with full source fields
/v1/batch$0.30 / $1.00 / $3.002-200 items in one call, tiered by count
/v1/health, /.well-known/x402freerow counts, load dates, payment terms
MCP exclusion_check$0.05per call
MCP exclusion_batch_checktieredsame tiers as /v1/batch
MCP exclusion_sourcesfree 

Paid in USDC over x402 on Base mainnet. See /v1/health for current row counts and load freshness.

Batch screening

Screen 2-200 people or businesses in one paid call — a clinic's 80-person staff roster is one call, not 80. Each item takes the same fields as /v1/check, plus an optional ref that comes back unchanged so you can join results to your own records. An invalid item is returned as an error in its place, not a failed batch; only a batch where every item is invalid is refused, and only then with no charge.

curl -X POST "https://exclusions.cfsoft.us/v1/batch" -H 'content-type: application/json' -d '{
  "items": [
    {"ref": "staff-1", "name": "Smith, John", "state": "TX"},
    {"ref": "staff-2", "npi": "1477537496"}
  ]
}'
ItemsPrice
2-10$0.30
11-50$1.00
51-200$3.00

Charged once per call, by item count, resolved from the real request at the time of payment — the payment-required header on an unpaid call always carries the exact amount for what you sent, not a rounded-up estimate.

v2 envelope

Add ?v=2 to /v1/check, /v1/report, or /v1/batch for the CF Soft envelope: the same top-level shape (service, verdict, confidence, basis, counts, records, sources, limits, as_of) every CF Soft booth returns, so integrating one booth is most of the way to integrating all of them. Without ?v=2, every response stays exactly what it always was. Full shape in docs/ENVELOPE.md.

curl "https://exclusions.cfsoft.us/v1/check?name=Smith,%20John&state=TX&v=2"

Try it free — 3 calls a day

Add ?trial=1 to a GET /v1/check request (or send header X-Trial: 1). The first 3 calls per day from your IP return a real result with no payment challenge; the response carries X-Trial-Remaining. The 4th call that day gets the normal 402.

curl "https://exclusions.cfsoft.us/v1/check?name=Smith,%20John&state=TX&trial=1"

curl (paid)

curl -i "https://exclusions.cfsoft.us/v1/check?name=Smith,%20John&state=TX"
# -> 402 Payment Required; the payment-required header carries the exact terms.
# An x402-aware HTTP client retries the same request with a signed payment header.

MCP

Claude Desktop validates only local (stdio) servers in its config, so a remote server goes through the mcp-remote bridge:

{
  "mcpServers": {
    "cf-exclusion-check": {
      "command": "npx",
      "args": ["mcp-remote", "https://exclusions.cfsoft.us/mcp"]
    }
  }
}

Claude Code, and other clients that speak remote HTTP directly (a bare URL, no bridge process):

{
  "mcpServers": {
    "cf-exclusion-check": {
      "type": "http",
      "url": "https://exclusions.cfsoft.us/mcp"
    }
  }
}

initialize and tools/list are free, so an agent can see both paid tools — exclusion_check and exclusion_batch_check — and their price before paying. Try it: exclusion_sources is a free tool.

x402 client (pay per call)

Any x402-aware HTTP client works. The repo's own verification client:

git clone https://github.com/cfgenius145-sketch/cf-exclusion-check
cd cf-exclusion-check && npm install
node scripts/x402-client.mjs                    # pays $0.05 for /v1/check
node scripts/x402-client.mjs /v1/report "Name"  # pays $0.50
BODY_JSON='{"items":[{"name":"Smith, John"},{"npi":"1477537496"}]}'   node scripts/x402-client.mjs /v1/batch        # pays the tiered price for /v1/batch

Data sources and refresh

Limits and disclaimer