# Roth vs Traditional Optimizer (remote · roth-vs-traditional-calculator.kindoflost.com)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `roth-vs-traditional-calculator.kindoflost.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-kindoflost-roth-vs-traditional-calculator-roth-vs-traditional-optimizer/roth-vs-traditional-calculator.md), [page](https://verifymcp.io/servers/com-kindoflost-roth-vs-traditional-calculator-roth-vs-traditional-optimizer/roth-vs-traditional-calculator)

## Channel facts

- Endpoint: `https://roth-vs-traditional-calculator.kindoflost.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 896 tokens (~298/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Roth vs Traditional Optimizer MCP server?

Roth vs Traditional Optimizer is a hosted endpoint at https://roth-vs-traditional-calculator.kindoflost.com/mcp, 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.

### Claude

```bash
claude mcp add --transport http com-kindoflost-roth-vs-traditional-calculator-ro 'https://roth-vs-traditional-calculator.kindoflost.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-kindoflost-roth-vs-traditional-calculator-ro": {
      "url": "https://roth-vs-traditional-calculator.kindoflost.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-kindoflost-roth-vs-traditional-calculator-ro": {
      "type": "http",
      "url": "https://roth-vs-traditional-calculator.kindoflost.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-kindoflost-roth-vs-traditional-calculator-ro]
url = "https://roth-vs-traditional-calculator.kindoflost.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-kindoflost-roth-vs-traditional-calculator-ro": {
      "type": "remote",
      "url": "https://roth-vs-traditional-calculator.kindoflost.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-kindoflost-roth-vs-traditional-calculator-ro --url 'https://roth-vs-traditional-calculator.kindoflost.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-kindoflost-roth-vs-traditional-calculator-ro:
    url: "https://roth-vs-traditional-calculator.kindoflost.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-kindoflost-roth-vs-traditional-calculator-ro": {
      "Transport": "http",
      "Url": "https://roth-vs-traditional-calculator.kindoflost.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-kindoflost-roth-vs-traditional-calculator-ro -t streamable-http -u 'https://roth-vs-traditional-calculator.kindoflost.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 70)

First indexed and scored.

## MCP tools (3)

### `get_contribution_example` (~73 tokens)

Get an example contribution input

Return a complete example input for optimize_retirement_contributions with a one-line explanation of every field. No solve. Edit it to the user's situation. kind 'single' (default) or 'married' (two earners, kids, HSA, two-tier match).

Input parameters:

- `kind` (string)

### `optimize_retirement_contributions` (~481 tokens)

Optimize Roth vs traditional contributions

Find the best yearly split of retirement savings between traditional and Roth 401(k), IRA/backdoor Roth, HSA and brokerage, including employer match, Roth conversions and retirement withdrawals. Returns this year's dollars per account, how the optimal mix compares with always-traditional and always-Roth, Roth share, lifetime totals, the first working years and retirement milestones. Runs in a few seconds (a few more with exact_income_limits). All money in today's dollars. Optimal for the stated assumptions; not tax advice. Call get_contribution_example first if unsure of the shape.

Input parameters:

- `accounts` (object): Which accounts the user can use. Defaults: 401(k) and Roth 401(k) available, IRA allowed, no HSA, no match.
- `age` (integer, required): Your age this year. The plan starts now.
- `assumptions` (object): Modeling assumptions; the defaults are reported back.
- `balances` (object): Current household balances, dollars. Omitted = 0.
- `children_birth_years` (array): Birth years of dependent children (child tax credit, head of household).
- `end_age` (integer): Plan until this age (default 92; horizon at most 90 years).
- `filing` (string): Tax filing status. Default 'single'. 'married' = one joint return; fill in the spouse_* fields.
- `real_raise_pct` (number): Yearly raise above inflation, whole percent (1 = 1%). Default 1.
- `retire_age` (integer, required): Age you stop working. Must be above 'age'.
- `salary` (number, required): Your gross pay this year, in dollars.
- `social_security` (object): Expected Social Security (household). Omitted = none modeled.
- `spending_in_retirement` (number, required): Yearly spending after retiring, today's dollars (before income tax).
- `spending_while_working` (number): Yearly living costs while still working, today's dollars. Default = spending_in_retirement.
- `spouse_retire_age` (integer): Married only: the age YOU will be when your spouse stops working (all ages on this server are the primary earner's). Default = retire_age.
- `spouse_salary` (number): Married only: spouse's gross pay this year (0 or omitted = spouse does not work).

### `check_request` (~73 tokens)

Check if a request fits

Say in plain words what the user wants (e.g. 'I'm self-employed with a solo 401k and a pension'). Returns whether this optimizer can do it and, if not, the closest thing it can do. Fast, no solve.

Input parameters:

- `description` (string, required): The user's question in a sentence or two.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-kindoflost-roth-vs-traditional-calculator-roth-vs-traditional-optimizer/roth-vs-traditional-calculator#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70

## Common questions

### What is the Roth vs Traditional Optimizer MCP server?

Roth vs Traditional Optimizer is an MCP server listed in the public MCP registry as com.kindoflost.roth-vs-traditional-calculator/roth-vs-tradi…. Optimal yearly Roth vs traditional split: 401(k), IRA, HSA, brokerage, employer match. Free. This page covers its hosted endpoint (https://roth-vs-traditional-calculator.kindoflost.com/mcp).

### Is the Roth vs Traditional Optimizer MCP server safe to use?

Roth vs Traditional Optimizer scores 72 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 Roth vs Traditional Optimizer MCP server expose?

Roth vs Traditional Optimizer exposes 3 tools: get_contribution_example, optimize_retirement_contributions, check_request. Their descriptions and schemas cost roughly 627 tokens of context every time the server is loaded.

### Does the Roth vs Traditional Optimizer MCP server require authentication?

No. We connected to Roth vs Traditional Optimizer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Roth vs Traditional Optimizer MCP server still maintained?

Roth vs Traditional Optimizer is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://roth-vs-traditional-calculator.kindoflost.com/mcp
- Website: https://roth-vs-traditional-calculator.kindoflost.com/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/com-kindoflost-roth-vs-traditional-calculator-roth-vs-traditional-optimizer/roth-vs-traditional-calculator.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-kindoflost-roth-vs-traditional-calculator-roth-vs-traditional-optimizer/roth-vs-traditional-calculator.json
- HTML version of this page: https://verifymcp.io/servers/com-kindoflost-roth-vs-traditional-calculator-roth-vs-traditional-optimizer/roth-vs-traditional-calculator