io.github.builtforai/part-d-cap is an MCP server published by io.github.builtforai, hosted at insurewith.ai. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 1 tool, including medicare_part_d_out_of_pocket_cap.
Medicare Part D out-of-pocket cap: when you hit it, and what the payment plan changes
11 connections through 5 shared values. Tap any node.
Project month-by-month Medicare Part D out-of-pocket spending against the statutory annual cap, identify the month the cap is reached, quantify what the cap itself saves, and compare normal payment timing against the Medicare Prescription Payment Plan — which spreads the SAME total across the year without reducing it. Supports plan years 2026 and 2027 and fails closed to 2026 for any unsupported year rather than extrapolating. This is a standard-benefit simulation, NOT a plan-specific pharmacy quote: plan negotiated prices and plan cost sharing are not held and are never inferred.
| Parameter | Type | Description |
|---|---|---|
| drug | string | Optional drug name — checks formulary status and whether spending on it counts toward the cap |
| join | string | Optional month (1-12) the payment plan would be joined |
| year | string | Optional plan year: 2026 or 2027 |
| monthly * | string | Expected monthly out-of-pocket spend on covered drugs, in USD, e.g. "300" |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
| deductible | string | Optional plan drug deductible in USD, e.g. "615" or "0" |
{
"name": "medicare_part_d_out_of_pocket_cap",
"description": "Project month-by-month Medicare Part D out-of-pocket spending against the statutory annual cap, identify the month the cap is reached, quantify what the cap itself saves, and compare normal payment timing against the Medicare Prescription Payment Plan — which spreads the SAME total across the year without reducing it. Supports plan years 2026 and 2027 and fails closed to 2026 for any unsupported year rather than extrapolating. This is a standard-benefit simulation, NOT a plan-specific pharmacy quote: plan negotiated prices and plan cost sharing are not held and are never inferred.",
"inputSchema": {
"type": "object",
"required": [
"monthly"
],
"properties": {
"drug": {
"type": "string",
"description": "Optional drug name — checks formulary status and whether spending on it counts toward the cap"
},
"join": {
"type": "string",
"description": "Optional month (1-12) the payment plan would be joined"
},
"year": {
"type": "string",
"description": "Optional plan year: 2026 or 2027"
},
"monthly": {
"type": "string",
"description": "Expected monthly out-of-pocket spend on covered drugs, in USD, e.g. \"300\""
},
"deductible": {
"type": "string",
"description": "Optional plan drug deductible in USD, e.g. \"615\" or \"0\""
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.