_ registry / mcp http-sse

npi-providers-mcp-server

https://npi-providers.caseyjhand.com

Registry code: 53fbf447ae284d17

api record

US healthcare provider directory over the live, keyless NPPES NPI Registry, plus a bundled NUCC taxonomy code set for offline specialty resolution. Public professional practice data only (name, practice address, specialty, credential, NPI) — no personal or home data. Typical flow: npi_search_providers (resolve a name/specialty/place to candidate NPIs) → npi_get_provider (decode one or more NPIs to full records). Ground plain-language specialties with npi_lookup_taxonomy before searching. The registry never reports a true match total and only the first 1200 matches are reachable, so narrow…

endpoint
https://npi-providers.caseyjhand.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 3 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • npi_search_providers unknown never probed

    Search the NPPES NPI registry for individual practitioners and healthcare organizations by name, organization name, location, provider type, and specialty. Plain-language specialty terms (e.g. "cardiologist", "pediatric cardiologist") resolve through the bundled NUCC taxonomy; the top match's specialization or classification becomes taxonomy_description, and all resolved candidates are returned in metadata. Location belongs in the dedicated city/state/postal_code inputs, not inside specialty. Each provider row includes the NPI, name, primary specialty, city/state/ZIP, type, and active/deactivated status; the NPI is the input for npi_get_provider when the full record is needed. At least one search criterion is required, and the registry rejects state-only searches. For specialty searches, returned providers are limited to the requested city/state/postal_code even when the registry includes providers outside that location. The registry never reports a true match total and only the first 1200 matches are reachable, so broad queries are capped.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "city": {
      "type": "string",
      "description": "Practice-location city."
    },
    "skip": {
      "type": "integer",
      "default": 0,
      "maximum": 1000,
      "minimum": 0,
      "description": "Results to skip for pagination (0–1000). Only the first 1200 matches are reachable; skip beyond 1000 silently returns the same window — narrow the query instead of paging further."
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 200,
      "minimum": 1,
      "description": "Maximum providers to return (1–200; the registry caps at 200)."
    },
    "state": {
      "anyOf": [
        {
          "type": "string",
          "const": ""
        },
        {
          "type": "string",
          "pattern": "^[A-Z]{2}$",
          "description": "2-letter state code (e.g. \"WA\")."
        }
      ],
      "description": "2-letter state code (e.g. \"WA\"). The registry rejects state-only searches, so another criterion is required. A blank value is treated as omitted."
    },
    "last_name": {
      "type": "string",
      "description": "Individual last name. Trailing wildcard \"*\" allowed with at least 2 leading characters."
    },
    "specialty": {
      "type": "string",
      "description": "Plain-language specialty (e.g. \"pediatric cardiologist\"), resolved through the bundled NUCC taxonomy to exact descriptions before searching. The matched taxonomy is echoed in the result. Mutually exclusive with taxonomy_description."
    },
    "first_name": {
      "type": "string",
      "description": "Individual first name. Trailing wildcard \"*\" allowed with at least 2 leading characters."
    },
    "name_search": {
      "type": "string",
      "description": "One person's name. The first token becomes first_name and the last token becomes last_name; use first_name/last_name when middle names or multi-part surnames matter."
    },
    "postal_code": {
      "type": "string",
      "description": "Practice-location postal/ZIP code (5 or 9 digits)."
    },
    "provider_type": {
      "enum": [
        "individual",
        "organization"
      ],
      "type": "string",
      "description": "Restrict to individuals (NPI-1) or organizations (NPI-2). Omit to search both."
    },
    "organization_name": {
      "type": "string",
      "description": "Organization name (implies provider_type organization). Trailing wildcard \"*\" allowed with at least 2 leading characters."
    },
    "taxonomy_description": {
      "type": "string",
      "description": "Exact NUCC taxonomy description for direct passthrough — use when the taxonomy description is already known. Mutually exclusive with specialty."
    }
  },
  "additionalProperties": false
}
    arguments 75 lines
  • npi_get_provider unknown never probed

    Fetch the complete NPPES record for one or more NPI numbers (up to 10 per call). Decodes an NPI from a claim, prescription, or another health data source into a fully populated provider profile: every taxonomy with its primary flag, license number and state; all practice and mailing addresses; credential, sex, sole-proprietor flag; enumeration and last-updated dates; active/deactivated status; secondary identifiers (Medicaid, etc.); and FHIR/Direct endpoints. The 10-digit NPI format is validated before any API call. Reports partial success: well-formed NPIs with no registry record (deactivated or never enumerated) land in notFound, while NPIs whose lookup hit an upstream error (registry unavailable, timeout) land in errored — kept distinct from confirmed misses — rather than failing the whole call.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "npis"
  ],
  "properties": {
    "npis": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^\\d{10}$",
          "description": "A 10-digit National Provider Identifier."
        },
        {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^\\d{10}$",
            "description": "A 10-digit National Provider Identifier."
          },
          "maxItems": 10,
          "minItems": 1,
          "description": "An array of up to 10 ten-digit NPIs."
        }
      ],
      "description": "A single 10-digit NPI, or an array of up to 10. Each is validated as exactly 10 digits before any API call."
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • npi_lookup_taxonomy unknown never probed

    Resolve and browse the NUCC Healthcare Provider Taxonomy — the specialty code set NPPES uses — fully offline (bundled). Mode `resolve` turns a plain-language specialty (e.g. "cardiologist", "heart doctor") into matching taxonomy entries; mode `get` returns the full entry for an exact code; mode `browse` walks the hierarchy (grouping → classification → specialization), optionally filtered by grouping and by NPI section (Individual/NPI-1 vs Non-Individual/NPI-2). A resolved entry's specialization, or its classification when specialization is absent, maps directly to npi_search_providers.taxonomy_description.

    mcp-tool

    {
  "type": "object",
  "oneOf": [
    {
      "type": "object",
      "required": [
        "mode",
        "query"
      ],
      "properties": {
        "mode": {
          "type": "string",
          "const": "resolve",
          "description": "Resolve a plain-language specialty to taxonomy codes."
        },
        "skip": {
          "type": "integer",
          "default": 0,
          "maximum": 1000,
          "minimum": 0,
          "description": "Entries to skip before the page (0–1000). Keep the same query and limit, then raise skip by limit each call."
        },
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum matching entries to return (1–50)."
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "The plain-language specialty term to resolve, e.g. \"pediatric cardiologist\"."
        }
      },
      "additionalProperties": false
    },
    {
      "type": "object",
      "required": [
        "mode",
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "minLength": 1,
          "description": "The exact NUCC taxonomy code, e.g. \"207RC0000X\"."
        },
        "mode": {
          "type": "string",
          "const": "get",
          "description": "Fetch one exact taxonomy entry by code."
        }
      },
      "additionalProperties": false
    },
    {
      "type": "object",
      "required": [
        "mode"
      ],
      "properties": {
        "mode": {
          "type": "string",
          "const": "browse",
          "description": "Browse the taxonomy hierarchy."
        },
        "skip": {
          "type": "integer",
          "default": 0,
          "maximum": 1000,
          "minimum": 0,
          "description": "Entries to skip before the page (0–1000). Keep the same filters and limit, then raise skip by limit each call."
        },
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum entries to return (1–50)."
        },
        "section": {
          "enum": [
            "Individual",
            "Non-Individual"
          ],
          "type": "string",
          "description": "Filter by NPI section: Individual (NPI-1) or Non-Individual (NPI-2)."
        },
        "grouping": {
          "type": "string",
          "description": "Filter to a top-level grouping by case-insensitive substring, e.g. \"physicians\"."
        }
      },
      "additionalProperties": false
    }
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
    arguments 100 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/53fbf447ae284d17/badge.svg)](https://brick.blue/agent/53fbf447ae284d17)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on caseyjhand.com 81 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

73 more sit on this domain. All of them.