Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fonteum — Healthcare Provider Data

NPM · @FONTEUM/MCP · SCANNED SEP 21

Source-provenanced US federal healthcare provider data over MCP, with 14-tuple provenance.

Available components

0 this week 85 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 68 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 439 tokens (~87/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Fonteum — Healthcare Provider Data MCP server?

Fonteum — Healthcare Provider Data runs locally as an npm package, launched with npx -y @fonteum/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @fonteum/mcp

# add to Claude Code
claude mcp add fonteum-mcp-server -- npx -y @fonteum/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "fonteum-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@fonteum/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fonteum-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@fonteum/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add fonteum-mcp-server -- npx -y @fonteum/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fonteum-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@fonteum/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fonteum-mcp-server --command npx --arg -y --arg @fonteum/mcp
# ~/.hermes/config.yaml
mcp_servers:
  fonteum-mcp-server:
    command: "npx"
    args: ["-y", "@fonteum/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fonteum-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@fonteum/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add fonteum-mcp-server -t stdio -c npx -a -y @fonteum/mcp
// mcp.json
{
  "mcpServers": {
    "fonteum-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@fonteum/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.83 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/@fonteum/mcp@0.2.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~439 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fonteum_check_exclusion ~103

Unified 'excluded anywhere' check for a provider by NPI across the federal OIG LEIE and the state Medicaid exclusion lists (NY/OH/GA now, more as the ring expands). Returns the exclusion flag and any matched records, each with its own provenance. Screening aid — re-confirm any match against the primary source list before acting; absence of a match is not a guarantee.

NameTypeReqDescription
npistringyes10-digit National Provider Identifier

No output schema declared.

No examples provided.

fonteum_dataset_info ~103

Read the published methodology + metadata for one of Fonteum's federal source families (e.g. nppes, oig-leie, cms-pecos, cms-open-payments, cms-care-compare). Returns the dataset's methodology version, refresh cadence, license, and coverage window.

NameTypeReqDescription
datasetstringyesDataset slug, e.g. nppes | oig-leie | cms-pecos | cms-open-payments | cms-care-compare

No output schema declared.

No examples provided.

fonteum_get_provider ~88

Resolve a US healthcare provider by 10-digit NPI across NPPES, OIG LEIE, CMS PECOS, Care Compare, and Open Payments in one call. Returns the full joined record; each source block carries its own 14-tuple provenance and the response envelope carries a composite 14-tuple.

NameTypeReqDescription
npistringyes10-digit National Provider Identifier

No output schema declared.

No examples provided.

fonteum_list_sources ~43

List the federal public-record source families Fonteum reconciles every healthcare-provider field against. Each entry carries authority, tier, status, refresh cadence, and official URL.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fonteum_search_provider ~102

Search US healthcare providers by NPI, name, specialty/taxonomy, or location. Returns matching records with source-provenance.

NameTypeReqDescription
limitintegerMax results (1-25, default 10)
querystringyesFree-text query: NPI, provider name, specialty, or location
specialtystringOptional taxonomy/specialty filter
statestringOptional 2-letter US state filter

No output schema declared.

No examples provided.

Common questions

What is the Fonteum — Healthcare Provider Data MCP server?

Fonteum — Healthcare Provider Data is an MCP server listed in the public MCP registry as io.github.Fonteum/mcp-server. Source-provenanced US federal healthcare provider data over MCP, with 14-tuple provenance. This page covers its npm package (@fonteum/mcp).

Is the Fonteum — Healthcare Provider Data MCP server safe to use?

Fonteum — Healthcare Provider Data scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Fonteum — Healthcare Provider Data MCP server expose?

Fonteum — Healthcare Provider Data exposes 5 tools: fonteum_search_provider, fonteum_get_provider, fonteum_check_exclusion, fonteum_dataset_info, fonteum_list_sources. Their descriptions and schemas cost roughly 439 tokens of context every time the server is loaded.

Is the Fonteum — Healthcare Provider Data MCP server still maintained?

Fonteum — Healthcare Provider Data is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Fonteum — Healthcare Provider Data MCP server under?

Fonteum — Healthcare Provider Data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.