Skip to content
FonteumPublic-records evidence

AGENT CONNECTION CARD

One public-records interface for your agent.

Fonteum brings dated public records across healthcare, federal procurement, sanctions and watchlists, federal enforcement, and global company registers into one read-only MCP interface. Every response carries the same source-context keys; unavailable file, date, or digest values stay null.

Hosted MCP 1.1.0 · stdio package 0.5.0 pending publication · npm currently 0.4.0

01 · CONNECT

Use the live hosted endpoint.

Remote clients can use hosted MCP 1.1.0 directly. The matching @fonteum/mcp@0.5.0 stdio source is not published yet; it is pending operator publication. npm currently serves 0.4.0. The local configuration below is for use only after operator publication. Hosted access is anonymous and rate-limited. The future package uses a Bearer credential for its protected REST bridges.

HOSTED MCP

# Streamable-HTTP MCP endpoint
https://fonteum.com/api/mcp

LOCAL PACKAGE

{
  "_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}" }
    }
  }
}

Machine-readable discovery: https://fonteum.com/.well-known/mcp.json.

02 · NINE READ-ONLY TOOLS

The same tool set across both contracts.

These are the live hosted tools and the matching future stdio package contract. They return public-record context only; no tool mutates a record. Use only the source and as-of values the response supplies, preserve null values, and read the listed limitations before reuse. Every registration carries readOnlyHint: true.

fonteum_lookup_npi

Look up an NPI

Look 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_contractor

Look up a contractor

Look 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_providers

Search providers

Search 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_exclusion

Check an exclusion

Check 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_sanctions

Search sanctions

Search 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_history

Read contractor history

Look 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_snapshot

Re-check a snapshot

Recheck 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_sources

List sources

List 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_info

Read dataset metadata

Get 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.

03 · UNIFORM OUTPUT

Four citation fields on every response.

Successes and errors include JSON text plus matching MCP structured content. The top-level fields are source_file, as_of_date, snapshot_digest, and verifiable_url. The first three stay null when one source file, date, or retained snapshot does not honestly represent the result.

04 · SOURCE CONTEXT

Use registry status as context, not as a coverage claim.

The active production source registry is not a statement that every family has loaded, complete, fresh, or displayable records. The relevant response, dataset metadata, and methodology describe the available source, observation date, coverage, and limitations for a specific use.

curl https://fonteum.com/.well-known/mcp.json

What’s on file, by the numbers

Platform snapshot · 2026-07-25

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
79fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access