# InPlan (remote · api.inplan.io)

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

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.inplan.io`: 74/100 (this document), [markdown](https://verifymcp.io/servers/io-inplan-inplan/api.md), [page](https://verifymcp.io/servers/io-inplan-inplan/api)

## Channel facts

- Endpoint: `https://api.inplan.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1825 tokens (~260/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the InPlan MCP server?

InPlan is a hosted endpoint at https://api.inplan.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-inplan-inplan 'https://api.inplan.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-inplan-inplan": {
      "url": "https://api.inplan.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-inplan-inplan": {
      "type": "http",
      "url": "https://api.inplan.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-inplan-inplan]
url = "https://api.inplan.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-inplan-inplan": {
      "type": "remote",
      "url": "https://api.inplan.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-inplan-inplan --url 'https://api.inplan.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-inplan-inplan:
    url: "https://api.inplan.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-inplan-inplan": {
      "Transport": "http",
      "Url": "https://api.inplan.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-inplan-inplan -t streamable-http -u 'https://api.inplan.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-inplan-inplan": {
      "type": "http",
      "url": "https://api.inplan.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 73, 0)

- [security] Tool “check_network” rewrote its description, which is the text the model reads
- [security] Tool “check_network_batch” rewrote its description, which is the text the model reads
- [security] Tool “get_plan” rewrote its description, which is the text the model reads
- [security] Tool “plans_for_provider” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 216 → 260

### 2026-11-01 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 72)

First indexed and scored.

## MCP tools (7)

### `lookup_provider` (~115 tokens)

Look up a provider by NPI

Identity of a US healthcare provider by NPI: name, credential, specialties, practice locations and groups, plus a summary of the Marketplace (ACA) and Medicare Advantage plans whose network directories list them (plan counts, states, plan years, as_of dates). Use it to confirm who an NPI is before checking networks. For the plan list itself use plans_for_provider. Costs 1 call.

Input parameters:

- `npi` (string, required): 10-digit National Provider Identifier, as a string, e.g. "1184617268".

Output parameters:

- `data` (object): The answer. Same shape as the matching InPlan API v1 endpoint.
- `data_as_of` (string|null): Date (YYYY-MM-DD) of the newest data behind this answer.
- `notes` (array): How to read the answer.
- `request_id` (string): Request id; quote it when you contact support.
- `sources` (array): Source types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

### `plans_for_provider` (~383 tokens)

Plans that list a provider

Every Marketplace (ACA) and Medicare Advantage plan whose network directory lists the provider, one row per plan and plan year, each with plan name, insurer, state, network tier, evidence_tier (the row's answer, highest tier first), source {type, as_of} and evidence (every proof we hold for that plan, in tier order). Rows with evidence_tier 'named_network' are plans whose own name identifies their network, where the insurer's directory lists the provider in that network (network_name); report them as 'listed in the network this plan names', never as 'listed'. Rows with evidence_tier 'contracted_network' are plans where the insurer's published contract files list this provider in the network for the plan's product (network_labels); report them as 'contracted network', never as 'listed'. Medicare Advantage rows carry service_area_states and provider_state_in_service_area. Filter by market, state or year; page with limit and offset (next_offset is null on the last page). A plan missing from this list is not a statement that the provider is out of network. Costs 1 call per page.

Input parameters:

- `limit` (integer): Plans per page, 1 to 500. Default 50.
- `market` (string): "aca" = Marketplace plans, "ma" = Medicare Advantage plans. Optional; default both.
- `npi` (string, required): 10-digit National Provider Identifier, as a string, e.g. "1184617268".
- `offset` (integer): Rows to skip; pass next_offset from the previous page. Default 0.
- `state` (string): 2-letter US state code, e.g. "OH". Optional.
- `year` (integer): Plan year, e.g. 2026. Optional; by default all plan years we hold are considered.

Output parameters:

- `data` (object): The answer. Same shape as the matching InPlan API v1 endpoint.
- `data_as_of` (string|null): Date (YYYY-MM-DD) of the newest data behind this answer.
- `notes` (array): How to read the answer.
- `request_id` (string): Request id; quote it when you contact support.
- `sources` (array): Source types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

### `check_network` (~388 tokens)

Is this provider in this plan?

Answers whether one plan's network directory lists one provider. answer "listed" (in_network: true) comes with evidence: plan year, network tier and source {type, as_of}. answer "not_found" (in_network: null) means no listing was found in current directory data for this provider and plan; it is NOT a statement that the provider is out of network, so never report it as "out of network". answer "listed_in_named_network" (in_network: null) means the plan's own name identifies its network and the insurer's directory lists the provider in that network; evidence carries network_name and as_of; report it as "listed in the network this plan names", never as "listed". answer "contracted_network" (in_network: null) means the insurer's published contract files list this provider in the network for this plan's product; the evidence item with evidence_tier "contracted_network" carries network_labels and as_of; report it as "contracted network", never as "listed". When a directory listing also exists, the answer is "listed" and the contracted item follows it in evidence. answer "no_provider_network" is a drug-only plan. Directories change; tell users to confirm with the plan before care. Costs 1 call.

Input parameters:

- `npi` (string, required): 10-digit National Provider Identifier, as a string, e.g. "1184617268".
- `plan_id` (string, required): Plan ID. Marketplace (ACA) plans: 14 characters like "29276OH0970001" (a 16-character "-01" variant form is accepted). Medicare Advantage plans: "H1234-001-000" (the segment "-000" is optional).
- `year` (integer): Plan year, e.g. 2026. Optional; by default all plan years we hold are considered.

Output parameters:

- `data` (object): The answer. Same shape as the matching InPlan API v1 endpoint.
- `data_as_of` (string|null): Date (YYYY-MM-DD) of the newest data behind this answer.
- `notes` (array): How to read the answer.
- `request_id` (string): Request id; quote it when you contact support.
- `sources` (array): Source types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

### `check_network_batch` (~112 tokens)

Check up to 100 provider and plan pairs

The check_network answer for up to 100 (npi, plan_id) pairs in one request, with the same listed / listed_in_named_network / contracted_network / not_found / no_provider_network semantics. Invalid pairs come back with a per-item error and are not charged; each accepted pair costs 1 call. Needs the Builder plan or higher.

Input parameters:

- `items` (array, required): 1 to 100 pairs.
- `year` (integer): Default plan year for items that do not set one. Optional.

Output parameters:

- `data` (object): The answer. Same shape as the matching InPlan API v1 endpoint.
- `data_as_of` (string|null): Date (YYYY-MM-DD) of the newest data behind this answer.
- `notes` (array): How to read the answer.
- `request_id` (string): Request id; quote it when you contact support.
- `sources` (array): Source types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

### `get_plan` (~189 tokens)

Plan details

Details of one Marketplace (ACA) or Medicare Advantage plan by plan ID: name, insurer or organization, state or service area, plan type, metal level, the plan years we hold, and whether we hold its directory listings, with their as_of date. For some plans sold only outside the marketplace, contracted_network {labels, as_of}: the network labels of the insurer's published contract files for the plan's product. Costs 1 call.

Input parameters:

- `plan_id` (string, required): Plan ID. Marketplace (ACA) plans: 14 characters like "29276OH0970001" (a 16-character "-01" variant form is accepted). Medicare Advantage plans: "H1234-001-000" (the segment "-000" is optional).
- `year` (integer): Plan year, e.g. 2026. Optional; by default all plan years we hold are considered.

Output parameters:

- `data` (object): The answer. Same shape as the matching InPlan API v1 endpoint.
- `data_as_of` (string|null): Date (YYYY-MM-DD) of the newest data behind this answer.
- `notes` (array): How to read the answer.
- `request_id` (string): Request id; quote it when you contact support.
- `sources` (array): Source types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

### `search_plan_providers` (~321 tokens)

Providers listed in a plan

Providers that a Marketplace (ACA) plan's network directory lists, with name, credential, primary specialty, network tiers and up to 5 locations. Filter by state, specialty (substring, e.g. "cardiology"), zip, or zip plus radius in miles. Pages are cursor-based: pass next_cursor back unchanged until it is null; with filters a page can hold fewer than limit providers. Medicare Advantage plans: use check_network or plans_for_provider instead. Needs the Growth plan or higher. Costs 1 call per page.

Input parameters:

- `cursor` (string): next_cursor from the previous page.
- `limit` (integer): Providers per page, 1 to 100. Default 25.
- `plan_id` (string, required): Plan ID. Marketplace (ACA) plans: 14 characters like "29276OH0970001" (a 16-character "-01" variant form is accepted). Medicare Advantage plans: "H1234-001-000" (the segment "-000" is optional).
- `radius` (integer): Miles around zip, 1 to 100. Needs zip.
- `specialty` (string): Specialty name or part of it, e.g. "family medicine". Optional.
- `state` (string): 2-letter US state code, e.g. "OH". Optional.
- `year` (integer): Plan year, e.g. 2026. Optional; by default all plan years we hold are considered.
- `zip` (string): 5-digit ZIP code, as a string. Optional.

Output parameters:

- `data` (object): The answer. Same shape as the matching InPlan API v1 endpoint.
- `data_as_of` (string|null): Date (YYYY-MM-DD) of the newest data behind this answer.
- `notes` (array): How to read the answer.
- `request_id` (string): Request id; quote it when you contact support.
- `sources` (array): Source types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

### `coverage` (~132 tokens)

What InPlan covers

The markets, states and insurers InPlan holds directory listings for, with plan counts and as_of dates, by plan year. Filter by market, state or year. Use it to see which states and insurers you can query. Costs 1 call.

Input parameters:

- `market` (string): "aca" = Marketplace plans, "ma" = Medicare Advantage plans. Optional; default both.
- `state` (string): 2-letter US state code, e.g. "OH". Optional.
- `year` (integer): Plan year, e.g. 2026. Optional; by default all plan years we hold are considered.

Output parameters:

- `data` (object): The answer. Same shape as the matching InPlan API v1 endpoint.
- `data_as_of` (string|null): Date (YYYY-MM-DD) of the newest data behind this answer.
- `notes` (array): How to read the answer.
- `request_id` (string): Request id; quote it when you contact support.
- `sources` (array): Source types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-inplan-inplan/api#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 72

## Common questions

### What is the InPlan MCP server?

InPlan is an MCP server listed in the public MCP registry as io.inplan/inplan. Is this US provider in this health plan? Network checks by NPI and plan ID, with dated sources. This page covers its hosted endpoint (https://api.inplan.io/mcp).

### Is the InPlan MCP server safe to use?

InPlan scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the InPlan MCP server expose?

InPlan exposes 7 tools: lookup_provider, plans_for_provider, check_network, check_network_batch, get_plan, and 2 more. Their descriptions and schemas cost roughly 1,640 tokens of context every time the server is loaded.

### Does the InPlan MCP server require authentication?

No. We connected to InPlan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the InPlan MCP server still maintained?

InPlan is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.inplan.io/mcp
- Authorisation metadata: https://api.inplan.io/.well-known/oauth-protected-resource/mcp
- Website: https://inplan.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-inplan-inplan/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-inplan-inplan/api.json
- HTML version of this page: https://verifymcp.io/servers/io-inplan-inplan/api