AdisInsight
Query Springer Nature's drug-pipeline and trial database from an AI agent.
Look up and search US provider records from the CMS NPPES NPI Registry.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The NPI Registry connector puts the CMS National Plan and Provider Enumeration System inside Claude, ChatGPT and any MCP-compatible agent. Its three read-only tools check an NPI's format, retrieve a provider record, and search by name, location or specialty. Anthropic builds and hosts it. It needs no sign-in, and it returns provider practice information rather than patient data.
Verified connector
Listed by Anthropic as an Anthropic-built connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Validate NPI format and Luhn check digit. Instant local validation - no API call. WHEN TO USE: - ALWAYS use before npi_lookup to catch typos and save API calls - Validating NPI numbers from external sources (documents, forms, databases) - Quick format check without network dependency - Pre-filtering lists of NPIs before bulk lookups WHAT THIS CHECKS: 1. Format: Exactly 10 digits, numeric characters only (0-9) 2. Check digit: Valid Luhn algorithm calculation with healthcare prefix (80840) WHAT THIS DOES NOT CHECK: - Whether the NPI is actually assigned to a provider in NPPES - Whether the provider is active or deactivated - Whether the provider is licensed or credentialed - Whether the NPI has ever been issued VALIDATION RESULTS: ✓ VALID: NPI has correct format AND valid check digit -> Proceed to npi_lookup to verify assignment ✗ INVALID FORMAT: Not 10 digits or contains non-numeric characters -> Cannot be a real NPI, check for typos ✗ INVALID CHECK DIGIT: 10 digits but check digit doesn't match -> Likely a typo in one of the digits IMPORTANT: A valid check digit does NOT guarantee the NPI exists! Many mathematically valid NPIs have never been assigned. Use npi_lookup after validation to confirm the NPI is in NPPES. EXAMPLES: - '1234567893' -> VALID (correct format + valid check digit) - '123456789' -> INVALID (only 9 digits) - '1234567890' -> INVALID (wrong check digit, expected 3) - '123456789X' -> INVALID (contains non-digit character) - ' 1234567893 ' -> VALID (whitespace is stripped automatically)
Get comprehensive provider details by NPI number from the CMS NPPES Registry. WHEN TO USE: - You have a specific NPI and need full provider information - Verifying provider credentials, specialty, or practice location - Following up on results from npi_search to get complete details - Cross-referencing clinical trial investigators with US credentials - Getting raw API response for advanced data extraction USE npi_search INSTEAD FOR: - Finding providers by name, location, or specialty - When you don't have a specific NPI number - Browsing providers in a geographic area WHAT THIS RETURNS: Basic Information: - Provider type: Individual (NPI-1) or Organization (NPI-2) - Name: Full name (individuals) or Legal Business Name (organizations) - Credentials: MD, DO, RN, PA-C, NP, etc. (for individuals) - Status: 'A' (Active) or 'D' (Deactivated) - Enumeration date: When the NPI was first assigned - Last updated: When the record was last modified Specialty/Taxonomy: - Primary taxonomy code: NUCC healthcare provider taxonomy code - Primary taxonomy description: Human-readable specialty name - License state and number: From primary taxonomy Location: - Practice address: Primary practice location with full address - Phone number: Practice telephone (if available) Advanced: - Raw API response: Complete NPPES data including: - All taxonomies (up to 15) - Other identifiers (state license, DEA, etc.) - Other practice locations - Authorized officials (for organizations) - Endpoints (health information exchange) NOTE: Automatically validates NPI format before API call. Returns found=false if NPI is valid but not assigned to any provider. IMPORTANT CAVEATS: - Having an NPI does NOT guarantee the provider is currently licensed - Provider self-reports data; NPPES does not verify accuracy - Deactivated providers remain in database but should not be used for billing - Verify credentials through state licensing boards for official confirmation
Search the CMS NPPES Registry for healthcare providers by name, location, specialty, or organization. WHEN TO USE: - Finding providers by name (e.g., 'Find Dr. John Smith') - Finding providers by specialty (e.g., 'Cardiologists in Boston') - Finding organizations (e.g., 'Mayo Clinic locations') - Verifying clinical trial investigators have US credentials - Building provider networks by location or specialty - Finding all providers at a specific facility USE npi_lookup INSTEAD FOR: - When you already have a specific NPI number - Getting full details including raw API response SEARCH REQUIREMENTS: - At least one search parameter required (besides enumeration_type/country_code) - State cannot be the only criterion - must combine with name, specialty, or city - Country code alone only works for non-US countries WILDCARD SUPPORT (min 2 characters before *): - first_name: 'Jo*' matches John, Joseph, Jonathan - last_name: 'Smi*' matches Smith, Smithson, Smitty - organization_name: 'Mayo*' matches Mayo Clinic, Mayo Foundation - taxonomy_description: 'Cardio*' matches Cardiology, Cardiovascular Disease - postal_code: '212*' matches all ZIP codes starting with 212 NAME ALIAS FEATURE (DEFAULT: ON): Automatically expands first name searches to include common nicknames: - Robert -> also finds Bob, Rob, Robbie, Bobby - William -> also finds Bill, Will, Billy, Willy - Elizabeth -> also finds Beth, Liz, Betty, Eliza - Michael -> also finds Mike, Mick, Mickey Set use_first_name_alias=false for exact match only. PAGINATION: - Maximum 200 results per request (limit parameter) - Skip up to 1000 records (skip parameter) - Maximum 1,200 total results accessible (6 requests × 200) - Use next_skip from response to get next page - Set limit=200 for comprehensive searches COMMON SPECIALTY SEARCHES (taxonomy_description): - Physicians: 'Internal Medicine', 'Family Practice', 'Cardiology', 'Oncology' - Surgeons: 'Orthopedic Surgery', 'General Surgery', 'Neurosurgery' - Mental Health: 'Psychiatry', 'Psychology', 'Clinical Social Worker' - Allied Health: 'Physical Therapist', 'Nurse Practitioner', 'Physician Assistant' - Organizations: 'General Acute Care Hospital', 'Pharmacy', 'Clinical Laboratory' EXAMPLES: - Find cardiologists in Boston: taxonomy_description='Cardiology', city='Boston', state='MA' - Find Dr. Smith (individual): first_name='John', last_name='Smith', enumeration_type='NPI-1' - Find Mayo Clinic (organization): organization_name='Mayo Clinic', enumeration_type='NPI-2' - Find oncologists in California: taxonomy_description='Oncology', state='CA', limit=100 - Find all pharmacies in NYC: taxonomy_description='Pharmacy', city='New York', state='NY' - Find nurse practitioners in Texas: taxonomy_description='Nurse Practitioner', state='TX' - Exact name match: first_name='Robert', use_first_name_alias=false
Read from the server on 2026-08-18, including each tool's own safety annotations.
last_updated is the only currency signal. Confirm licensure with the relevant state licensing board, which is the connector's own advice.D status, but CMS's public registry states it does not display NPIs that are not in service — so a deactivated NPI likely returns not-found, indistinguishable from an NPI that was never assigned. CMS ships a separate monthly deactivation file for this.npi_validate confirms format and Luhn arithmetic only. Many mathematically valid NPIs have never been issued, and CMS describes the NPI as an intelligence-free identifier whose digits encode no state, specialty or status.skip ceiling of 1,000, per CMS. Broad searches are samples, not enumerations, and the total field will exceed what you can page through. CMS's web interface uses a different cap of 2,100.npi_search with no arguments returns an empty result rather than an error. We observed this live. An empty result set is not evidence that no matching providers exist.initialize, tools/list, prompts/list and resources/list handshake, plus two deliberately safe tool calls: npi_validate on 1234567890, the tool's own documented invalid example, which performs no registry query; and npi_search with no arguments, which returned an empty set. No lookup was performed against any real provider's NPI, and no real provider's name, identifier, address or telephone number appears anywhere in this work.No. It returns healthcare provider practice information only — the fields CMS publishes about people and organisations who hold a National Provider Identifier. No tool takes a patient, member, claim, diagnosis or date-of-service parameter, and none returns clinical information. There is nowhere in this connector for protected health information to enter or appear.
It is data about healthcare providers, published by the Centers for Medicare and Medicaid Services under federal law at 45 CFR Part 162. CMS states it publishes the parts of an NPI record that have public relevance — name, specialty and practice address — and that only Freedom of Information Act disclosable fields are viewable. The registry exists so payers and providers can route claims correctly.
Yes, and that is a deliberate design of the CMS registry rather than something the connector adds. The npi_search tool accepts a first and last name with trailing wildcards after two characters, and expands nicknames by default. Searching by state alone is refused; state must be combined with a name, city or specialty.
No. CMS states plainly on its own data pages that issuance of an NPI does not ensure or validate that the healthcare provider is licensed or credentialed. The connector's own tool description repeats it. NPPES data is self-reported by providers and CMS does not verify accuracy, so confirm licensure through the relevant state licensing board.
No. We opened an anonymous handshake on 2026-08-18 and it returned all three tool definitions, then executed one read-only tool call with no credential of any kind and got a normal result. Anthropic's directory records the server as authless with a no_auth posture, and the host publishes no OAuth protected-resource descriptor at any of the three locations we probed.
Not reliably. The output schema carries a status field documented as A for active or D for deactivated, but CMS's own public registry states it does not display information about NPIs that are not in service. So a deactivated NPI is more likely to come back as not found than as status D. CMS publishes a separate monthly deactivation file.
No. NPPES carries no payer-network or contract data at all. The server ships a prompt template named verify_network_participation, and what it can actually support is comparing registry facts — specialty taxonomy, practice state, licence state — against requirements you supply. Network participation itself must come from the payer's own directory or contract records.
/plugin install npi-registry@healthcare, which the marketplace manifest marks deprecated. claude.com/robots.txt is Allow: / with no Content-Signal line (retrieved 2026-08-18). · retrieved 2026-08-18initialize, tools/list, prompts/list and resources/list handshake against https://hcls.mcp.claude.com/npi_registry/mcp — three tools with descriptions, input and output schemas and annotations, and three prompts with their arguments, over an anonymous connection (2026-08-18). serverInfo reported npi_registry version 3.2.0. Source for the tool count, every tool description, parameter and default named on this page, the uniform read-only/non-destructive/idempotent annotations, the openWorldHint split, the NPI-1/NPI-2 distinction, the US-only and daily-update statements in the server's instructions block, and the three prompt names and arguments. resources/list returned JSON-RPC error -32601 "Method not found", consistent with initialize declaring no resources capability. The initialize response declares the io.modelcontextprotocol/ui extension while no tool carries per-tool UI metadata. · retrieved 2026-08-18tools/call requests: npi_validate with 1234567890 returned HTTP 200 and a check-digit error from the local validator, and npi_search with no arguments returned HTTP 200 with an empty result set. Both executed with no credential, which observes the absence of an auth gate directly rather than inferring it from a successful tools/list. https://hcls.mcp.claude.com/.well-known/oauth-protected-resource, the path-suffixed form .../oauth-protected-resource/npi_registry/mcp, the path-prefixed form under the endpoint, .well-known/oauth-authorization-server and .well-known/mcp/server-card.json all returned 404. One prompts/get call on analyze_provider_credentials with the same placeholder NPI returned a no-provider-found message, showing the prompt performs a live registry lookup during rendering; the other two prompts failed to render against a placeholder and were not retried. · retrieved 2026-08-18/robots.txt, so help content was read from the application bundle https://npiregistry.cms.hhs.gov/main-3C7NMC67.js (HTTP 200, 1.5 MB) rather than from rendered HTML. Source for CMS publishing "the parts of the NPI record that have public relevance, including the provider's name, specialty (taxonomy) and practice address"; for the service being provided "based on federal law (45 CFR Part 162)"; for only Freedom of Information Act data associated with a record being viewable; for the registry describing itself as a directory of all active NPI records and returning "Our public registry does not display information about NPIs that are not in service" for a deactivated NPI; for the 200-per-request / 1,000-skip / 1,200-total API ceiling and the separate 2,100-result web-interface cap; for the hourly query limit effective 25 June 2024 and the instruction that bulk queries must use the data-dissemination file; for the API retrieving from NPPES daily and pending changes not being presented; for the address array placing the primary practice location first and the mailing address second; for the state-cannot-be-the-sole-criterion rule; and for the sole-proprietor and authorised-official record fields. · retrieved 2026-08-18www.cms.gov/robots.txt allows this path and carries no Content-Signal line (retrieved 2026-08-18). The link CMS's dissemination page still publishes to its "NPI: What You Need to Know" booklet resolves to a one-page PDF stating the booklet is no longer available and pointing here; this page is the destination cited. · retrieved 2026-08-18npi-registry plugin in favour of the bundled healthcare plugin at version 3.0.1, and for the bundle's server URL matching the directory endpoint byte-for-byte. · retrieved 2026-08-181234567890 as demo NPI data for the same placeholder reason this page does. · retrieved 2026-08-18anthropic tier, the health category, is_authless: true, auth_posture: no_auth, streamable-HTTP transport, Anthropic as author, and exactly the three tool names the live server returns, matching case-sensitively. Its prompt_names array is empty, against three prompts served live. · retrieved 2026-01-07Connect NPI Registry once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.