Fonteum — Healthcare Provider Data
Source-provenanced US federal healthcare provider data over MCP. Resolve any NPI or CCN across NPPES, OIG LEIE, SAM.gov, state Medicaid exclusions, CMS PECOS, Care Compare, and Open Payments — every field carries a 14-field provenance contract, and an "excluded or compromised anywhere" check runs on every lookup.
README
Fonteum MCP Server
Hosted Model Context Protocol server for the source-provenanced US federal healthcare provider data graph.
Fonteum joins the federal healthcare datasets — NPPES, OIG LEIE, CMS PECOS, CMS Care Compare, CMS Open Payments, HRSA, and more (23 source families) — into one provider graph keyed on the National Provider Identifier (NPI). This MCP server lets an LLM or agent search the graph, resolve a provider, check exclusion status, read dataset methodology, and list the underlying sources, with every returned field tied back to its upstream source, snapshot date, and license through a fourteen-field provenance contract. No trust badges, no opaque scores — radical source transparency.
- Hosted MCP endpoint:
https://mcp.fonteum.com/api/mcp(also served from the apex athttps://fonteum.com/api/mcp— same deployment) - Discovery document:
https://fonteum.com/.well-known/mcp.json - Transport: Streamable HTTP (JSON-RPC 2.0, stateless)
- Auth: none required. Anonymous access is rate-limited per IP (30 requests /
minute). An optional
x-fonteum-mcp-keyheader lifts the limit. - Scope: healthcare-only. Read-only — no mutation tools.
- REST + FHIR + OpenAPI: the same graph is exposed as a FHIR R4 API
(
/api/fhir), a JSON REST API (/api/v1), and an OpenAPI 3.1 spec athttps://fonteum.com/openapi.json.
Quickstart
Claude Code
claude mcp add --transport http fonteum https://mcp.fonteum.com/api/mcp
Claude Desktop / Cursor / Windsurf (remote MCP)
Add the streamable-HTTP server to your client's MCP config:
{
"mcpServers": {
"fonteum": {
"type": "http",
"url": "https://mcp.fonteum.com/api/mcp"
}
}
}
Restart the client, then ask: List the federal healthcare data sources Fonteum reconciles, then look up NPI 1003000118.
Local stdio alternative
A self-contained local server that wraps the same public graph over stdio ships
as the @fonteum/mcp npm package:
claude mcp add fonteum -- npx -y @fonteum/mcp
The hosted server (this repo) and the npm package expose the same five tools, read the same federal graph, and return the same provenance contract — enforced by a CI parity gate so the two surfaces cannot drift. The hosted server is the zero-install path; the npm package is the offline/self-hosted path.
Tools
Every tool result is a JSON envelope { "data": …, "provenance": { …14 keys… } }.
All five tools are read-only.
fonteum_search_provider
Search healthcare providers by vertical + state (with an optional county filter), name, or specialty/taxonomy. Returns up to 100 records (default 25).
- Input:
{ "vertical": "dermatologists", "state": "TX", "limit": 5 }
// fonteum_search_provider { "vertical": "dermatologists", "state": "TX", "limit": 5 } →
{
"data": { "vertical": "dermatologists", "state": "TX", "total_in_state": 42, "returned": 5, "hits": [ { "npi": "…", "city": "…", "taxonomy_primary": "…" }, … ] },
"provenance": { "_source": "CMS NPPES NPI Registry", … }
}
fonteum_get_provider
Resolve a single healthcare provider by NPI (10-digit, Luhn-checked) across all federal sources. Returns the joined record — specialty, taxonomy, location — with per-field provenance.
- Input:
{ "npi": "1003000118" }
// fonteum_get_provider { "npi": "1003000118" } →
{
"data": { "npi": "1003000118", "specialty_display": "Dermatologists", "state": "CA", "city": "…", "snapshot_date": "2026-06-12" },
"provenance": { "_source": "CMS NPPES NPI Registry", "_source_url": "https://npiregistry.cms.hhs.gov/", "_confidence": 1.0, … }
}
fonteum_check_exclusion
Unified "excluded anywhere" check by NPI across the federal OIG List of Excluded Individuals/Entities (LEIE) and state Medicaid exclusion lists. Returns the exclusion flag and any matched exclusion records with provenance.
- Input:
{ "npi": "1003000118" }
// fonteum_check_exclusion { "npi": "1003000118" } →
{
"data": { "npi": "1003000118", "is_excluded": false, "matches": [] },
"provenance": { "_source": "OIG LEIE + state Medicaid exclusion lists", "_source_url": "https://oig.hhs.gov/exclusions/exclusions_list.asp", … }
}
fonteum_dataset_info
Return the published methodology and metadata for a federal source family
(nppes, oig-leie, cms-pecos, cms-open-payments, cms-care-compare, …),
including the methodology version, canonical URL, and provenance-contract spec.
- Input:
{ "dataset": "nppes" }
// fonteum_dataset_info { "dataset": "nppes" } →
{
"data": { "dataset": "nppes", "methodology_version": "v2026.05.0", "methodology_url": "https://fonteum.com/methodology", "refresh_cadence": "weekly" },
"provenance": { … }
}
fonteum_list_sources
List the federal source families Fonteum reconciles every healthcare-provider field against (NPPES, OIG LEIE, CMS PECOS, CMS Care Compare, CMS Open Payments, HRSA HPSA, and more), each with its authority, tier, refresh cadence, and the official source URL.
- Input: none.
// fonteum_list_sources →
{
"data": { "sources": [ { "slug": "nppes", "authority": "CMS", "tier": 1, "refresh_cadence": "weekly", "official_url": "https://npiregistry.cms.hhs.gov/" }, … ], "total": 23 },
"provenance": { "_source": "Fonteum source registry", "_methodology": "v2026.05.0", … }
}
The fourteen-field provenance contract
Every tool response carries all fourteen keys, so any fact an agent reads can be traced to its source, snapshot, methodology, license, coverage window, and signed build attestation:
_source _source_url _dataset_id _snapshot
_methodology _last_checked _confidence _data_availability
_pipeline_version _doi _license _coverage_period_start
_coverage_period_end _slsa_provenance_url
Field naming matches the Fonteum REST audit-pack endpoint, so tooling that already consumes the REST API reads MCP responses without translation. The contract is additive-only — keys are never stripped.
Healthcare scope
This server is healthcare-only by doctrine. The verticals it resolves are:
chiropractors, dermatologists, plastic-surgeons, med-spas, weight-loss clinics,
rehab centers, hair-transplant clinics, fertility clinics, TRT clinics, and
ketamine clinics. Federal source data is US-Government-Works (public domain);
Fonteum composite terms apply to joined records (see the _license field on each
response).
License
MIT. See LICENSE.
Author & contact
Authored by Dr. Jennifer Montecillo, MD, medical reviewer, Fonteum.
Contact: mcp@fonteum.com · fonteum.com
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。