Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

InPlan

REMOTE · API.INPLAN.IO

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

Available components

74 Trust /100

Last scanned (21 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +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.

  • 2 Nov 26 0
    • 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 security
    • Schema quality: 216 → 260 ▼ functional
  • 1 Nov 26 +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.

  • 31 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 30 Oct 26 72

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://api.inplan.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=inplan.io CN=YE1,O=Let's Encrypt,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA384 6081e99d26bfc9f505dbd35fa7254c01823
SANs: *.inplan.io, inplan.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.inplan.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
inplan.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data: blob: https://*.google-analytics.com https://*.googletagmanager.com; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; manifest-src 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.inplan.io/mcp Verified 200
http (plaintext) http://api.inplan.io/mcp HTTPS enforced 301 https://api.inplan.io/mcp
MCP tools · 7 exposed · ~1,640 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_network ~388

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.

NameTypeReqDescription
npistringyes10-digit National Provider Identifier, as a string, e.g. "1184617268".
plan_idstringyesPlan 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).
yearinteger–Plan year, e.g. 2026. Optional; by default all plan years we hold are considered.
NameTypeReqDescription
dataobjectyesThe answer. Same shape as the matching InPlan API v1 endpoint.
data_as_ofstring|nullyesDate (YYYY-MM-DD) of the newest data behind this answer.
notesarray–How to read the answer.
request_idstringyesRequest id; quote it when you contact support.
sourcesarrayyesSource types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

No examples provided.

check_network_batch ~112

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.

NameTypeReqDescription
itemsarrayyes1 to 100 pairs.
yearinteger–Default plan year for items that do not set one. Optional.
NameTypeReqDescription
dataobjectyesThe answer. Same shape as the matching InPlan API v1 endpoint.
data_as_ofstring|nullyesDate (YYYY-MM-DD) of the newest data behind this answer.
notesarray–How to read the answer.
request_idstringyesRequest id; quote it when you contact support.
sourcesarrayyesSource types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

No examples provided.

coverage ~132

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.

NameTypeReqDescription
marketstring–"aca" = Marketplace plans, "ma" = Medicare Advantage plans. Optional; default both.
statestring–2-letter US state code, e.g. "OH". Optional.
yearinteger–Plan year, e.g. 2026. Optional; by default all plan years we hold are considered.
NameTypeReqDescription
dataobjectyesThe answer. Same shape as the matching InPlan API v1 endpoint.
data_as_ofstring|nullyesDate (YYYY-MM-DD) of the newest data behind this answer.
notesarray–How to read the answer.
request_idstringyesRequest id; quote it when you contact support.
sourcesarrayyesSource types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

No examples provided.

get_plan ~189

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.

NameTypeReqDescription
plan_idstringyesPlan 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).
yearinteger–Plan year, e.g. 2026. Optional; by default all plan years we hold are considered.
NameTypeReqDescription
dataobjectyesThe answer. Same shape as the matching InPlan API v1 endpoint.
data_as_ofstring|nullyesDate (YYYY-MM-DD) of the newest data behind this answer.
notesarray–How to read the answer.
request_idstringyesRequest id; quote it when you contact support.
sourcesarrayyesSource types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

No examples provided.

lookup_provider ~115

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.

NameTypeReqDescription
npistringyes10-digit National Provider Identifier, as a string, e.g. "1184617268".
NameTypeReqDescription
dataobjectyesThe answer. Same shape as the matching InPlan API v1 endpoint.
data_as_ofstring|nullyesDate (YYYY-MM-DD) of the newest data behind this answer.
notesarray–How to read the answer.
request_idstringyesRequest id; quote it when you contact support.
sourcesarrayyesSource types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

No examples provided.

plans_for_provider ~383

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.

NameTypeReqDescription
limitinteger–Plans per page, 1 to 500. Default 50.
marketstring–"aca" = Marketplace plans, "ma" = Medicare Advantage plans. Optional; default both.
npistringyes10-digit National Provider Identifier, as a string, e.g. "1184617268".
offsetinteger–Rows to skip; pass next_offset from the previous page. Default 0.
statestring–2-letter US state code, e.g. "OH". Optional.
yearinteger–Plan year, e.g. 2026. Optional; by default all plan years we hold are considered.
NameTypeReqDescription
dataobjectyesThe answer. Same shape as the matching InPlan API v1 endpoint.
data_as_ofstring|nullyesDate (YYYY-MM-DD) of the newest data behind this answer.
notesarray–How to read the answer.
request_idstringyesRequest id; quote it when you contact support.
sourcesarrayyesSource types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

No examples provided.

search_plan_providers ~321

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.

NameTypeReqDescription
cursorstring–next_cursor from the previous page.
limitinteger–Providers per page, 1 to 100. Default 25.
plan_idstringyesPlan 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).
radiusinteger–Miles around zip, 1 to 100. Needs zip.
specialtystring–Specialty name or part of it, e.g. "family medicine". Optional.
statestring–2-letter US state code, e.g. "OH". Optional.
yearinteger–Plan year, e.g. 2026. Optional; by default all plan years we hold are considered.
zipstring–5-digit ZIP code, as a string. Optional.
NameTypeReqDescription
dataobjectyesThe answer. Same shape as the matching InPlan API v1 endpoint.
data_as_ofstring|nullyesDate (YYYY-MM-DD) of the newest data behind this answer.
notesarray–How to read the answer.
request_idstringyesRequest id; quote it when you contact support.
sourcesarrayyesSource types behind the answer (insurer_directory, plan_directory, provider_registry, plan_catalog), each with its as_of date.

No examples provided.

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.

remote · api.inplan.io

# add to Claude Code
claude mcp add --transport http io-inplan-inplan 'https://api.inplan.io/mcp'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.