io.github.builtforai/part-d-cap
REMOTE · INSUREWITH.AI · SCANNED SEP 28
Medicare Part D out-of-pocket cap: when you hit it, and what the payment plan changes
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 238 tokens (~238/item across 1 items; 1 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 Management33
- Stability observed for 10 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.builtforai/part-d-cap MCP server?
io.github.builtforai/part-d-cap is a hosted endpoint at https://insurewith.ai/mcp/part-d-cap, 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 · insurewith.ai
claude mcp add --transport http builtforai-part-d-cap 'https://insurewith.ai/mcp/part-d-cap'
{
"mcpServers": {
"builtforai-part-d-cap": {
"url": "https://insurewith.ai/mcp/part-d-cap"
}
}
} {
"servers": {
"builtforai-part-d-cap": {
"type": "http",
"url": "https://insurewith.ai/mcp/part-d-cap"
}
}
} [mcp_servers.builtforai-part-d-cap] url = "https://insurewith.ai/mcp/part-d-cap"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"builtforai-part-d-cap": {
"type": "remote",
"url": "https://insurewith.ai/mcp/part-d-cap",
"enabled": true
}
}
} openclaw mcp add builtforai-part-d-cap --url 'https://insurewith.ai/mcp/part-d-cap' --transport streamable-http
mcp_servers:
builtforai-part-d-cap:
url: "https://insurewith.ai/mcp/part-d-cap" {
"McpServers": {
"builtforai-part-d-cap": {
"Transport": "http",
"Url": "https://insurewith.ai/mcp/part-d-cap"
}
}
} assistant mcp add builtforai-part-d-cap -t streamable-http -u 'https://insurewith.ai/mcp/part-d-cap'
{
"mcpServers": {
"builtforai-part-d-cap": {
"type": "http",
"url": "https://insurewith.ai/mcp/part-d-cap"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 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.
- 19 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Sept 26 57
First indexed and scored.
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 28 Sept 2026 · Probed https://insurewith.ai/mcp/part-d-cap
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=insurewith.ai | CN=WE1,O=Google Trust Services,C=US | 10 Aug 2026 | 9 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 98f6119d6e97fd130e37dad78c93949e |
| SANs: insurewith.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of insurewith.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| insurewith.ai. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://insurewith.ai/mcp/part-d-cap | Verified | 200 | |
| http (plaintext) | http://insurewith.ai/mcp/part-d-cap | Inconclusive | 404 |
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 →
medicare_part_d_out_of_pocket_cap ~238
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deductible | string | – | Optional plan drug deductible in USD, e.g. "615" or "0" |
| 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 |
| monthly | string | yes | Expected monthly out-of-pocket spend on covered drugs, in USD, e.g. "300" |
| year | string | – | Optional plan year: 2026 or 2027 |
No output schema declared.
No examples provided.
What is the io.github.builtforai/part-d-cap MCP server?
io.github.builtforai/part-d-cap is an MCP server listed in the public MCP registry as io.github.builtforai/part-d-cap. Medicare Part D out-of-pocket cap: when you hit it, and what the payment plan changes. This page covers its hosted endpoint (https://insurewith.ai/mcp/part-d-cap).
Is the io.github.builtforai/part-d-cap MCP server safe to use?
io.github.builtforai/part-d-cap scores 61 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 io.github.builtforai/part-d-cap MCP server expose?
io.github.builtforai/part-d-cap exposes 1 tool: medicare_part_d_out_of_pocket_cap. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.
Does the io.github.builtforai/part-d-cap MCP server require authentication?
No. We connected to io.github.builtforai/part-d-cap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.builtforai/part-d-cap MCP server still maintained?
io.github.builtforai/part-d-cap is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.