InPlan

io.inplanPublished by inplan.ioOfficial publisherv1.0.0Updated Oct 30, 2026

Is this US provider in this health plan? Network checks by NPI and plan ID, with dated sources.

VerifiedStreamable HTTPWeb executableLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

Remote InPlan MCP server that lets an assistant check whether a US provider is in a given health plan's network, by NPI and plan ID, with dated sources.

What you can do
  • Check provider network participation: look up whether a US provider is in a specified health plan.
  • Query by NPI and plan ID to run network checks.
  • Return dated sources alongside the results so answers can be traced.
When to use it
Useful when you need to verify US health plan network status for a provider, for example before a referral, appointment or billing question, and want the answer tied to dated sources.
Requirements
A remote endpoint at api.inplan.io over streamable HTTP. Requires an InPlan API key sent in the Authorization header as a bearer token; a free key is offered at signup. Network access to the endpoint is needed.
Before you install
The API key is a secret sent in the Authorization header; keep it private and store it securely. Results reflect the sources and dates returned, so verify current network status before relying on it for care or billing decisions.

Installation

In SourceWeft

  1. Open InPlan in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.inplan%2Finplan/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": {
    "inplan": {
      "type": "http",
      "url": "https://api.inplan.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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

1
  1. v1.0.0LatestOct 30, 2026

Score

39% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.