Roth vs Traditional Optimizer

com.kindoflost.roth-vs-traditional-calculatorPublished by roth-vs-traditional-calculator.kindoflost.comOfficial publisherv1.0.0Updated Nov 2, 2026

Optimal yearly Roth vs traditional split: 401(k), IRA, HSA, brokerage, employer match. Free.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote MCP endpoint that computes an optimal yearly split between Roth and traditional retirement accounts across 401(k), IRA, HSA and brokerage.

What you can do
  • Compute an optimal yearly Roth versus traditional contribution split.
  • Cover 401(k), IRA, HSA, brokerage and employer match in the same calculation.
  • Return a suggested allocation for the year based on the inputs provided.
When to use it
Useful when someone is deciding how to divide yearly retirement contributions between Roth and traditional accounts and wants a quick modeled recommendation rather than a manual spreadsheet.
Requirements
A remote streamable HTTP endpoint; no package installation, account, API key or environment variable is declared.
Before you install
The manifest lists no tools, so the exact inputs and outputs are unknown until you connect. It is a free calculator, but its output is a model, not personalized financial advice; check assumptions before acting on it.

Installation

In SourceWeft

  1. Open Roth vs Traditional Optimizer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.kindoflost.roth-vs-traditional-calculator%2Froth-vs-traditional-optimizer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "roth-vs-traditional-optimizer": {
      "type": "http",
      "url": "https://roth-vs-traditional-calculator.kindoflost.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestNov 2, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.