One paste to connect
The server is the npm package @fonteum/mcp, started by npx. The default key pk_dx_sample is a free, read-only demo key — 100 requests/hour, no signup.
claude_desktop_config.json{
"mcpServers": {
"fonteum": {
"command": "npx",
"args": ["-y", "@fonteum/mcp"],
"env": { "FONTEUM_API_KEY": "pk_dx_sample" }
}
}
}claude mcp add fonteum -- npx -y @fonteum/mcpmcpServers)// ~/.cursor/mcp.json (global) or .cursor/mcp.json (project)
{
"mcpServers": {
"fonteum": {
"command": "npx",
"args": ["-y", "@fonteum/mcp"]
}
}
}# Clients that speak remote (streamable-HTTP) MCP can point
# straight at the hosted server — no local process:
https://fonteum.com/api/mcpDiscovery card: https://fonteum.com/.well-known/mcp.json. Then restart your client and ask it to look up a provider — e.g. “Look up NPI 1234567893 with Fonteum.”
Three core tools
Read-only by charter — the agent reads facts, it never writes them. Think of them as lookup a record, search records, and a re-checkable integrity signal.
fonteum_get_providerlookup a recordLook up one provider by NPI (10-digit, Luhn-checked) and get the reconciled record — every field carrying its 14-tuple provenance contract.
fonteum_search_providersearch recordsSearch providers by specialty + state (optional county), up to 100 per call. Each hit is dated to the source snapshot it came from.
fonteum_check_exclusionre-checkable integrity signalCheck an NPI against federal + state exclusion / sanction lists (OIG LEIE, SAM.gov, state Medicaid) — an exclusion & sanction-list monitoring signal for billing / program-integrity compliance. Re-confirm matches against the primary source.
Plus two more
fonteum_list_sourcesList the federal source families behind every field — authority, tier, refresh cadence, and official URL. Read-only.
fonteum_dataset_infoRead the methodology version and the fourteen-field provenance contract that ships with each dataset.
What it looks like in the loop
The agent calls a tool, gets a fact with its source and snapshot date, and cites the re-checkable attestation back — so its answer is auditable, not asserted.
Illustrative transcript · the cite-your-source loop
Every fact carries its source, snapshot date, and a re-checkable attestation id — so the agent’s answer is auditable, not asserted.
Re-check what your agent cites
Every attestation the tools reference lands at /verify/<id>. Paste a snapshot id to pull the signed envelope and re-derive the hash yourself — the same proof your agent hands its user.
Re-check it yourself
Every snapshot ships with a SHA-256 attestation. Look one up to get its source archive, published hash, and Ed25519 chain head — then re-hash the bytes yourself.
Or run the full flow at /verify · curl /verify/<id>