Reported issues for npi-providers-mcp-server
Pod holds 17 of 17 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.
Back to npi-providers-mcp-server.
Most discussed
bug(npi_get_provider): endpoints drop four live NPPES fields
Server version
0.1.7
mcp-ts-core version
0.10.14
Runtime
Bun
Runtime version
Bun 1.3.x
Transport
HTTP (Streamable HTTP)
Description
npi_get_provider and npi://provider/{npi} drop four fields that live NPPES v2.1 responses carry on endpoints[]: endpointDescription, contentOtherDescription, useOtherDescription, and the endpoint address_2. None reaches structuredContent, the formatted content[] text, or the resource JSON, so an endpoint whose…
Read the thread · 2026-07-10 · closed · 7 comments
bug(npi_search_providers): other-name matches are indistinguishable from current-name matches
Server version
0.2.0
mcp-ts-core version
0.13.6
Runtime
Bun
Runtime version
Bun 1.4.0
Transport
stdio
OS
macOS 26.1
Description
NPPES matches first_name/last_name against a provider's other (former or alternate) names as well as the current name, and sorts by current last name. npi_search_providers rows show only the current name, so an other-name match looks like a wrong result, and for a common name the other-name matches fill the reachable…
Read the thread · 2026-09-24 · closed · 2 comments
bug(npi_lookup_taxonomy): plural stop words are kept as required terms
Server version
0.3.0
mcp-ts-core version
0.13.6
Runtime
Bun
Runtime version
Bun 1.4.0
Transport
stdio
OS
macOS 26.1
Description
npi_lookup_taxonomy mode resolve recognizes stop words only in their singular form. doctors, physicians, specialists, and providers are kept as required terms, so a plural lay phrase that resolves in the singular finds nothing, or matches unrelated words through the stem. npi_search_providers specialty behaves…
Read the thread · 2026-09-24 · closed · 1 comment
bug(npi_lookup_taxonomy): stop-word-only queries match unrelated words
Server version
0.3.0
mcp-ts-core version
0.13.6
Runtime
Bun
Runtime version
Bun 1.4.0
Transport
stdio
OS
macOS 26.1
Description
When a npi_lookup_taxonomy mode resolve query is made only of stop words (physician, doctor, specialist, provider, md, do), the resolver keeps them as required terms and matches their stems at word starts. They then hit unrelated words: physician stems to physic and leads with Radiological Physics, and do…
Read the thread · 2026-09-24 · closed · 1 comment
bug(npi_search_providers): mixed individual and organization criteria get an unrelated hint
Server version
0.3.0
mcp-ts-core version
0.13.6
Runtime
Bun
Runtime version
Bun 1.4.0
Transport
stdio
OS
macOS 26.1
Description
npi_search_providers with a person-name field and provider_type: "organization" (or organization_name with provider_type: "individual") is sent to NPPES, which rejects it with error 13 ("Cannot mix type 1 and type 2 search criteria"). The tool relays it as invalid_search_field with a recovery hint about wildcards and…
Read the thread · 2026-09-24 · closed · 1 comment
bug(npi_lookup_taxonomy): dotted abbreviations resolve through single letters
Server version
0.3.0
mcp-ts-core version
0.13.6
Runtime
Bun
Runtime version
Bun 1.4.0
Transport
stdio
OS
macOS 26.1
Description
npi_lookup_taxonomy mode resolve splits a dotted abbreviation like P.A. into one-letter tokens, and each one-letter token matches any word starting with that letter. Dotted forms of provider credentials resolve to unrelated physician codes, and npi_search_providers specialty filters on them.
Steps to reproduce
1.…
Read the thread · 2026-09-24 · closed · 1 comment
bug(npi_lookup_taxonomy): pediatric variants lead sports and sleep medicine
Server version
0.2.0
mcp-ts-core version
0.13.6
Runtime
Bun
Runtime version
Bun 1.4.0
Transport
stdio
OS
macOS 26.1
Description
npi_lookup_taxonomy mode resolve demotes pediatric variants of a specialty only when "Pediatric" appears in the specialization. Entries whose classification is Pediatrics (Sports Medicine, Sleep Medicine under 2080…) are not demoted, so a bare sports medicine query leads with the pediatric code and npi_search_providers…
Read the thread · 2026-09-24 · closed · 1 comment
bug(npi_lookup_taxonomy): therapist resolves to Therapeutic Radiology
Server version
0.2.0
mcp-ts-core version
0.13.6
Runtime
Bun
Runtime version
Bun 1.4.0
Transport
stdio
OS
macOS 26.1
Description
npi_lookup_taxonomy mode resolve stems therapist to therap, which also starts the word "therapeutic". Therapeutic Radiology Physician then ranks first on the physician-grouping tier, ahead of every therapist profession, and npi_search_providers specialty: "therapist" filters on Therapeutic Radiology.
Steps to…
Read the thread · 2026-09-24 · closed · 1 comment
Most recent
bug(npi_lookup_taxonomy): physician assistant resolves to Dental Assistant
Server version
0.1.9
mcp-ts-core version
0.13.6
Runtime
Bun
Runtime version
Bun 1.4.0
Transport
stdio
OS
macOS 26.1
Description
npi_lookup_taxonomy mode resolve drops physician as a stop word whenever another token remains, so physician assistant resolves as assistant and ranks Dental Assistant above Physician Assistant. The same stripping applies to any NUCC label where physician is part of the specialty's own name.
Steps to reproduce…
Read the thread · 2026-09-24 · closed · 1 comment
bug(npi_lookup_taxonomy): resolve matches query stems inside unrelated words
Server version
0.1.9
mcp-ts-core version
0.13.6
Runtime
Bun
Runtime version
Bun 1.4.0
Transport
stdio
OS
macOS 26.1
Description
npi_lookup_taxonomy mode resolve matches a query's stem anywhere inside an entry's words, so a stem that happens to sit inside an unrelated word pulls that entry in — and can rank it first. npi_search_providers resolves specialty through the same resolver and sends the top hit's description to NPPES, so the wrong…
Read the thread · 2026-09-24 · closed · 1 comment
feat(npi_search_providers): restrict location searches to practice addresses upstream
Use case
A location-constrained npi_search_providers call sends only city/state/postal_code upstream. NPPES then matches mailing addresses as well as practice locations, so part of every page is mailing-only rows the tool's post-filter drops — 23 of 200 on city=SEATTLE&state=WA&enumeration_type=NPI-1, 32 of 200 on a Seattle cardiology search (2026-09-24). Those rows spend page slots and skip offsets inside the registry's 1200-row window without ever reaching the caller.
###…
Read the thread · 2026-09-24 · closed · 1 comment
bug(npi_search_providers): location post-filter drops providers practicing at a secondary location
Server version
0.1.9
mcp-ts-core version
0.13.6
Runtime
Bun
Runtime version
Bun 1.4.0
Transport
stdio
OS
macOS 26.1
Description
npi_search_providers post-filters rows against the requested city/state/postal_code using only the record's primary LOCATION address. NPPES matches a location search against the mailing address or any practice location, so a provider who practices in the requested city at a secondary location (practiceLocations[]) is…
Read the thread · 2026-09-24 · closed · 1 comment
bug(npi_lookup_taxonomy): resolve returns inactive NUCC codes
Server version
0.1.7
mcp-ts-core version
0.10.14
Runtime
Bun
Runtime version
Bun 1.3.14
Transport
stdio
OS
macOS 26.1
Description
npi_lookup_taxonomy mode resolve returns NUCC codes marked inactive, with nothing in the output flagging them, and npi_search_providers sends its top resolve() hit to NPPES as taxonomy_description. 28 bundled codes are inactive; 22 of them are the top hit for their own specialization name (e.g. psychotherapy,…
Read the thread · 2026-08-02 · closed · 1 comment
bug(nppes): malformed results fabricate misses and provider state
Server version
0.1.7
mcp-ts-core version
0.10.14
Runtime
Bun
Runtime version
Bun 1.3.14
Transport
stdio
OS
macOS 26.1
Description
The NPPES response boundary casts parsed JSON directly to RawNppesResponse without runtime shape validation. Structurally malformed or partial success bodies can become confirmed misses, fabricated provider identities, or a retried native error instead of a typed upstream-response failure.
Steps to reproduce
Stub the…
Read the thread · 2026-08-02 · closed · 1 comment
bug(npi_get_provider): individual mailing addresses cross the practice-data boundary
Server version
0.1.7
mcp-ts-core version
0.10.14
Runtime
Bun
Runtime version
Bun 1.3.14
Transport
stdio
OS
macOS 26.1
Description
npi_get_provider and npi://provider/{npi} return every addresses[] row for an individual (NPI-1), including MAILING, which for a sole practitioner can be a home address and phone — contradicting the server's own scope statement ("no personal or home data"). npi_search_providers falls back to the first address when a…
Read the thread · 2026-08-02 · closed · 1 comment
bug(npi_get_provider): invalid-check-digit NPIs reach NPPES and read as deactivated
Server version
0.1.7
mcp-ts-core version
0.10.14
Runtime
Bun
Runtime version
Bun 1.3.14
Transport
stdio
OS
macOS 26.1
Description
npi_get_provider and npi://provider/{npi} check only that an NPI is 10 digits. A value with a failing check digit (Luhn, calculated as if prefixed by 80840) is sent to NPPES, which answers…
Read the thread · 2026-08-02 · closed · 1 comment
bug(npi_lookup_taxonomy): full entries drop NUCC Notes
Server version
0.1.7
mcp-ts-core version
0.10.14
Runtime
Bun
Runtime version
Bun 1.3.x
Transport
HTTP (Streamable HTTP)
Description
npi_lookup_taxonomy describes mode get as returning "the full entry for an exact code", but scripts/generate-taxonomy-data.ts drops the NUCC Notes column at bundle time, so neither mode get nor npi://taxonomy/{code} can return it. Notes is not sparse: 597 of the 879 bundled codes carry one, and some carry substantive…
Read the thread · 2026-07-16 · closed · 1 comment
The remaining reports are on the project's issue tracker.