Healthcare Provider Intelligence

io.github.JoinwarePublished by GitHub account Joinwarev0.1.3Updated Oct 24, 2026

Provider intelligence API joining NPPES, CMS Open Payments, and OIG LEIE with source provenance.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryData & Analytics

Overview

AI-generated overview

Lets an assistant query a hosted healthcare provider intelligence API that joins NPPES, CMS Open Payments, and OIG LEIE data with source provenance.

What you can do
This remote MCP server exposes a provider intelligence API that combines the NPPES provider registry, CMS Open Payments, and OIG LEIE exclusion data, and reports source provenance for the results. The manifest does not list individual tools, but the provider describes two usage tiers: provider search, which is free up to 100 requests per day, and detailed lookups, which consume prepaid credits.
When to use it
Use it when an assistant needs to look up or cross-reference U.S. healthcare provider information across registry, payment, and exclusion datasets, for example during compliance, credentialing, or research checks. It is less suitable if you only need a single dataset or cannot supply an API key. It is not a general-purpose search or scraping tool.
Requirements
A remote streamable HTTP endpoint at with network access. Authentication is required: an API key supplied in the X-API-Key header. The provider says a free key can be obtained from its signup page. No packages or environment variables are declared.
Before you install
Requires an API key sent in the X-API-Key header; treat it as a secret and do not share it. The provider states that provider search is free up to 100 requests per day while detailed lookups consume prepaid credits, so paid usage can accrue. Queries are sent to a third-party remote endpoint, and the joined datasets include public healthcare provider and payment records.

Installation

In SourceWeft

  1. Open Healthcare Provider Intelligence in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Joinware%2Fhealthcare-provider-intelligence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "healthcare-provider-intelligence": {
      "type": "http",
      "url": "https://healthcare-provider-intelligence-85cj.onrender.com/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

3
  1. v0.1.3LatestOct 15, 2026
  2. v0.1.2Sep 25, 2026
  3. v0.1.1Sep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.