Connection options
Hosted MCP 1.1.0 is live at the streamable-HTTP endpoint. The matching @fonteum/mcp@0.5.0 stdio source is pending operator publication; npm currently serves 0.4.0. The three stdio snippets are future configurations for use after operator publication. Hosted access is anonymous and rate-limited.
{
"_status": "Future stdio config — @fonteum/mcp@0.5.0 is pending operator publication; npm currently serves 0.4.0",
"mcpServers": {
"fonteum": {
"command": "npx",
"args": ["-y", "@fonteum/mcp@0.5.0"],
"env": { "FONTEUM_API_KEY": "${FONTEUM_API_KEY}" }
}
}
}# Future stdio command — use only after @fonteum/mcp@0.5.0 is published.
# Set FONTEUM_API_KEY in the MCP client environment, then run:
claude mcp add fonteum -- npx -y @fonteum/mcp@0.5.0// Future config: @fonteum/mcp@0.5.0 is pending operator publication.
// npm currently serves @fonteum/mcp@0.4.0.
// ~/.cursor/mcp.json (global) or .cursor/mcp.json (project)
{
"mcpServers": {
"fonteum": {
"command": "npx",
"args": ["-y", "@fonteum/mcp@0.5.0"],
"env": { "FONTEUM_API_KEY": "${FONTEUM_API_KEY}" }
}
}
}# Hosted MCP contract 1.1.0 (streamable HTTP).
# Anonymous access is rate-limited; no REST Bearer credential is required.
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.”
Nine read-only tools
The live hosted endpoint and the pending 0.5 stdio source use the same canonical set and readOnlyHint: true. The agent reads source-traced facts; it never writes public records.
fonteum_lookup_npilook up an NPILook up a US healthcare provider by 10-digit NPI in CMS NPPES and return the available provider record plus exclusion and program-integrity context. Returns dated source context; source_file and snapshot_digest are nullable when no single retained snapshot represents the response. Use for NPI lookup, provider identity, taxonomy, practice-location, or provider due-diligence questions.
fonteum_lookup_contractorlook up a contractorLook up a US federal contractor by UEI or CAGE in available SAM.gov, USASpending, FAPIIS, and FAR 4.18 records. Returns dated source context; source_file and snapshot_digest are nullable when no single retained snapshot represents the response. Use for contractor identity, registration, award, responsibility, or ownership due diligence.
fonteum_search_providerssearch providersSearch US healthcare providers in loaded CMS NPPES specialty caches by vertical and state, with optional county context. Returns dated source context and up to 100 records; source_file and snapshot_digest may be null. Use for provider discovery by specialty and geography.
fonteum_check_exclusioncheck exclusionsCheck whether a US healthcare provider by NPI appears in available exclusion or integrity sources: OIG LEIE, SAM.gov exclusions, available state Medicaid lists, OIG Corporate Integrity Agreements, and CMS Civil Money Penalties. Returns dated source context and fail-closed coverage; source_file and snapshot_digest may be null for the multi-source result. Use for exclusion screening, provider or vendor due diligence, or any ‘is this NPI excluded?’ question.
fonteum_search_sanctionssearch sanctionsSearch a person or organization name across available sanctions and watchlist data from OFAC, the EU, the UK, and the UN, plus named exclusion sources held by Fonteum. Returns dated matches with source context; source_file and snapshot_digest may be null for the multi-source result. Use for sanctions screening, entity due diligence, or any ‘is this entity sanctioned?’ question.
fonteum_lookup_contractor_historyread contractor historyLook up a US federal contractor record as of a requested date using UEI or CAGE. Retained history is currently limited to USASpending award rows; other fields may be current, absent, or nullable. Returns dated source context. Use for historical award research or contractor change questions.
fonteum_recheck_snapshotre-check a snapshotRecheck a Fonteum snapshot by snapshot id and return its as_of_date, snapshot_digest, public verifiable_url, and source_file only when explicit retained-artifact metadata is available. Without an id, returns chain status without treating the chain head as a snapshot digest. Use for snapshot integrity checks, citation support, or reproducing a retained source file.
fonteum_list_sourceslist sourcesList Fonteum’s public-record source catalog with available authority, vertical, cadence, official URL, and separately dated platform coverage. Catalog presence does not prove loaded, fresh, or complete coverage. Use for source discovery, coverage questions, or choosing a dataset before a lookup.
fonteum_get_dataset_inforead dataset metadataGet Fonteum API and MCP methodology, provenance-field definitions, generated source catalog, and separately dated platform coverage. Field population varies by source and response. Use for interpreting Fonteum outputs, citation fields, dataset limitations, or integration planning.
One output contract for every tool
Successes and errors carry JSON text plus matching MCP structured content. The top-level keys source_file, as_of_date, snapshot_digest, and verifiable_url are always present. File, date, and digest values stay null when one retained snapshot does not honestly represent the response.
What it looks like in the loop
The agent calls a narrow tool, inspects the returned source fields, and cites only values that are populated. A snapshot digest covers the identified snapshot object, not each fact in a composite result.
Illustrative transcript · the cite-your-source loop
The four top-level source-context keys are always present. File, date, and digest values can be null; re-check the named issuing source before relying on the answer.
Re-check what your agent cites
When fonteum_recheck_snapshot returns a concrete verifiable_url, open it to inspect the retained snapshot object and its digest. Responses without one identified snapshot keep snapshot_digest null.
Re-check it yourself
Look up a snapshot id to see the source, date, digest, and chain fields that record actually returns. Digest comparison checks archive bytes; signature status is shown separately. No account needed.
Or run the full flow at /verify · curl /verify/<id>