https://exclusions.cfsoft.us/mcp ↗
Pay-per-call screening against HHS-OIG LEIE and SAM.gov exclusions.
io.github.cfgenius145-sketch/cf-exclusion-check is a remote MCP server published at exclusions.cfsoft.us. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 438 ms, placing it among the faster endpoints. It offers a narrow, focused set of 3 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
exclusion_check — Parameters lack required/optional clarity; all are marked as optional.exclusion_batch_check — Description does not specify item structure in the 'items' array.exclusion_sources — Description lacks details on returned data format (e.g., row counts, load dates).tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
exclusion_checkScreen a person or business against the HHS-OIG List of Excluded Individuals and Entities (LEIE) AND the SAM.gov exclusions list. Costs $0.05 per call via x402. Returns a verdict, a confidence level, the basis of each match, and the reason it matched. A match is a name match unless it was made on an identifier (npi, uei, cage); it is not an identity determination.
namestringnpistringdobstringstatestringueistringcagestringexclusion_batch_checkScreen 2-200 people/businesses against the same sources as exclusion_check in one call. Tiered price by item count: $0.30 (2-10), $1.00 (11-50), $3.00 (51-200), charged once via x402. An invalid item is reported in place, not a failure; all-invalid is refused before charging.
itemsarrayrequiredexclusion_sourcesList the loaded exclusion sources (OIG LEIE and SAM.gov), their row counts, load dates, load completeness and whether a bulk reseed is due. Free. Screening itself is paid: exclusion_check per name, or exclusion_batch_check for 2-200 at once ($0.30/$1.00/$3.00 by size).
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/io-github-cfgenius145-sketch-cf-exclusion-check)<a href="https://mcpmetrics.io/servers/io-github-cfgenius145-sketch-cf-exclusion-check"><img src="https://mcpmetrics.io/badge/io.github.cfgenius145-sketch/cf-exclusion-check/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
22 AI microservices with x402 micropayments: summarize, translate, code-review. USDC on Base.
Abandonment checks for WordPress, npm and PyPI packages, priced per call.
Summarize YouTube videos or fetch transcripts. Pay-per-call via x402 (USDC on Base), no account.
Agentic Finance: 500+ agent tools, multi-chain USDC over x402 or MPP, free via PoW or card credits
Pay-per-call APIs for AI agents: queries, storage, ads. Billed in USDC via x402.
x402 pay-per-call data tools for Base agents. Flagship get_intent ABSTAINS instead of guessing.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 01:33:33 | Legacy | 200 | 851 | 200 | 849 | 2025-06-18 |
| 2026-09-12 23:31:36 | Legacy | 200 | 417 | 200 | 417 | 2025-06-18 |
| 2026-09-12 21:29:15 | Legacy | 200 | 371 | 200 | 415 | 2025-06-18 |
| 2026-09-12 19:27:29 | Legacy | 200 | 528 | 200 | 489 | 2025-06-18 |
| 2026-09-12 17:24:09 | Legacy | 200 | 436 | 200 | 438 | 2025-06-18 |
| 2026-09-12 15:21:42 | Legacy | 200 | 378 | 200 | 544 | 2025-06-18 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.