fonteum_resolve_entityLABSCO SUMMARY
Every answer carries where it came from and when it was last checked.
The provenance block is the point of this: source, source URL, dataset id, the stored snapshot, the method version, the last-checked time and the coverage period the publisher claims. That is what lets a material match be taken to the issuing authority instead of taken on trust — which is exactly what the publisher asks you to do, since an exclusion or sanctions hit needs issuer confirmation before anyone acts on it. Two boundaries are stated plainly and worth repeating: there are no scores, labels or verdicts anywhere in the output, and an empty result means nothing came back for that request, not that the record does not exist.
What it is
A hosted, read-only MCP server over Fonteum's public-records platform, spanning healthcare, federal procurement, sanctions and watchlists, federal enforcement, intellectual property, securities filings and company registers from the United States and supported global open-data sources. It returns the records available for a request together with whatever source and timing information exists for that result. It reports facts and issues no clearances, risk scores, labels or verdicts.
What you get
- fonteum_resolve_entity takes one NPI, UEI or CAGE identifier and returns the provider or federal-contractor records tied to it, with the source context behind each fact
- fonteum_search_records finds healthcare provider records by provider type and state — that specific search, not a general one across every subject area
- fonteum_check_exclusions_and_sanctions reports whether an NPI or a name appears in the supported exclusion, debarment or sanctions records, naming the issuing authority and the timing available
- fonteum_get_record_as_of returns the federal-contractor records available for a given past date, with historical depth depending on the underlying source
- fonteum_recheck returns a current re-check link, or the details of one supplied snapshot, so the stored verification record can be inspected independently
- fonteum_list_sources returns the catalog with publishers, source links, update notes and reuse terms, and fonteum_dataset_info explains the current method and what the service can cover
- Answers are structured around their own context: data, provenance carrying source, source URL, dataset id, snapshot, methodology, last-checked time, coverage period and licence, plus freshness and an attestation record
- An empty answer means Fonteum returned nothing for that request — it does not establish that the item does not exist elsewhere
Requirements
A hosted server at https://fonteum.com/api/mcp over Streamable HTTP — add it with claude mcp add --transport http fonteum https://fonteum.com/api/mcp, or the equivalent config block in another client. Anonymous access is permitted and rate-limited; if Fonteum issues a hosted transport key, send it as x-fonteum-mcp-key rather than putting it in a public configuration file. MIT.
Setup effort
One command — claude mcp add --transport http fonteum https://fonteum.com/api/mcp
USE CASES
Checking one identifier against the public record
Resolve an NPI, UEI or CAGE into the records tied to it, with the publisher and timing behind each fact rather than a bare answer.
Screening a name before onboarding
Check the supported exclusion, debarment and sanctions records, then take any match to the authority that issued it before acting.
Finding providers of a given type in a state
The healthcare provider search, with the regulatory records for anyone worth a closer look pulled straight afterwards.
Reconstructing what a contractor's record said at the time
Ask for the federal-contractor record as of a specific date, and read the coverage notes that say how far back the source actually goes.
Knowing what is behind an answer before you cite it
List the sources in the catalog with their publishers, links and reuse terms, and inspect the stored snapshot the answer was assembled from.
7 tools
Listed in project docs. Your client may show a different list.
fonteum_search_recordsfonteum_check_exclusions_and_sanctionsfonteum_get_record_as_offonteum_recheckfonteum_list_sourcesfonteum_dataset_infoBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
All 3 documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
claude mcp add
Claude Code
claude mcp add --transport http fonteum https://fonteum.com/api/mcpHosted endpoint
https://fonteum.com/api/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Cursor
{
"mcpServers": {
"fonteum": {
"type": "http",
"url": "https://fonteum.com/api/mcp"
}
}
}Windsurf
{
"mcpServers": {
"fonteum": {
"type": "http",
"serverUrl": "https://fonteum.com/api/mcp"
}
}
}