General Tools
insurewith.ai
Helps Medicare Part D beneficiaries project out-of-pocket spending against the annual cap and navigate coverage restrictions, exceptions, and appeals.
ENDPOINT 1
https://insurewith.ai/mcp
MCP server metadata
- Name
- builtforai-insurewith
- Version
- 1.0.0
Known tools 2
medicare_part_d_out_of_pocket_capProject 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.
Potential side effectsmedicare_coverage_restriction_and_exceptionFor a drug on Medicare Part D, name the coverage problem — covered, prior authorization, step therapy, quantity limit, or not on formulary — and give the exception and appeal path with the CMS-named levels of appeal, who must submit the request, and what to ask the plan and the prescriber.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.builtforai-insurewith]
url = "https://insurewith.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"builtforai-insurewith": {
"type": "http",
"url": "https://insurewith.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: builtforai-insurewith
Remote MCP URL: https://insurewith.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"builtforai-insurewith": {
"url": "https://insurewith.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"builtforai-insurewith": {
"type": "http",
"url": "https://insurewith.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "builtforai-insurewith",
"transport": "streamable-http",
"url": "https://insurewith.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://insurewith.ai/mcp/part-d-cap
MCP server metadata
- Name
- builtforai-insurewith
- Version
- 1.0.0
Known tools 1
medicare_part_d_out_of_pocket_capProject 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.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.builtforai-insurewith]
url = "https://insurewith.ai/mcp/part-d-cap"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"builtforai-insurewith": {
"type": "http",
"url": "https://insurewith.ai/mcp/part-d-cap"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: builtforai-insurewith
Remote MCP URL: https://insurewith.ai/mcp/part-d-cap
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"builtforai-insurewith": {
"url": "https://insurewith.ai/mcp/part-d-cap"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"builtforai-insurewith": {
"type": "http",
"url": "https://insurewith.ai/mcp/part-d-cap"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "builtforai-insurewith",
"transport": "streamable-http",
"url": "https://insurewith.ai/mcp/part-d-cap"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.