Skip to content

InPlan MCP server

io.inplan/inplaninplan.iostreamable-httpv1.0.0Scanned

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

7 tools: 4 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 4 write, 3 read.
  • Reads private data · 3
  • Reads text others write · 0
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the InPlan MCP server can do

The InPlan MCP server is published by inplan.io, a domain the MCP Registry verified. It has 7 tools. It can create or change data (4 tools: plans_for_provider, check_network, check_network_batch and coverage), but cannot delete data. 3 tools only read.

3 tools read private data (lookup_provider, get_plan and search_plan_providers).

The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 4Claude Code: ask
  • check_networkAnswers whether one plan's network directory lists one provider.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Is this provider in this plan?
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_network_batchThe 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 se…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check up to 100 provider and plan pairs
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • coverageThe markets, states and insurers InPlan holds directory listings for, with plan counts and as_of dates, by plan year.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: What InPlan covers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • plans_for_providerEvery 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, e…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Plans that list a provider
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_planDetails 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 wh…Reads private dataNo findings

    Why it is in this group

    • The name "get_plan" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "directory": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Plan details
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • lookup_providerIdentity 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 whos…Reads private data1 finding

    Why it is in this group

    • The name "lookup_provider" says "lookup": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "credential": it reads secrets.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...a US healthcare provider by NPI: name, credential, specialties, practice locations and gr..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Look up a provider by NPI
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_plan_providersProviders that a Marketplace (ACA) plan's network directory lists, with name, credential, primary specialty, network tiers and up to 5 locations.Reads private data1 finding

    Why it is in this group

    • The name "search_plan_providers" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "directory": it reads files.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...n's network directory lists, with name, credential, primary specialty, network tiers and u..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Providers listed in a plan
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:23 UTC, unchanged since Oct 30, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.inplan.io/mcp: tools/list returned 7 tools to an anonymous client, including plans_for_provider (write), check_network (write), check_network_batch (write), coverage (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http inplan https://api.inplan.io/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http inplan https://api.inplan.io/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__inplan__lookup_provider",
      "mcp__inplan__get_plan",
      "mcp__inplan__search_plan_providers"
    ],
    "ask": [
      "mcp__inplan__plans_for_provider",
      "mcp__inplan__check_network",
      "mcp__inplan__check_network_batch",
      "mcp__inplan__coverage"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as inplan. Review it before you use it.

Capability tags behind 3 rules
  • mcp__inplan__lookup_provider private-data
  • mcp__inplan__get_plan private-data
  • mcp__inplan__search_plan_providers private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.inplan/inplan/verify?hash=c4662072d6dc7870dec95a1787bebeb63ee7de3b320d7a308834d6baf8ad7f12" | jq -e '.changed == false'

Pinned hash c4662072d6dc, from Nov 12, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.inplan/inplan/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.inplan/inplan
[![Anlyon Radar](https://radar.anlyon.com/badge/io.inplan/inplan.svg)](https://radar.anlyon.com/servers/io.inplan/inplan)

Source: MCP Registry. Synced Oct 30, 2026, 12:17 UTC.

InPlan MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the InPlan MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the InPlan MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the InPlan MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the InPlan MCP server have?

7 tools: 4 write, 3 read. plans_for_provider, check_network, check_network_batch, coverage, lookup_provider, get_plan and search_plan_providers.

Does the InPlan MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the InPlan MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the InPlan MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.