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.
Available components
Last scanned (9 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability57
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +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.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 70
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 5 Nov 2026 · Probed https://roth-vs-traditional-calculator.kindoflost.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=roth-vs-traditional-calculator.kindoflost.com | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a0038df5e5efef8e0ea5cb1c6b3ceb36 |
| SANs: roth-vs-traditional-calculator.kindoflost.com | ||||||
| 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 roth-vs-traditional-calculator.kindoflost.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kindoflost.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://roth-vs-traditional-calculator.kindoflost.com/mcp | Verified | 200 | |
| http (plaintext) | http://roth-vs-traditional-calculator.kindoflost.com/mcp | HTTPS enforced | 301 | https://roth-vs-traditional-calculator.kindoflost.com/mcp |
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 →
check_request Check if a request fits ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | The user's question in a sentence or two. |
No output schema declared.
No examples provided.
get_contribution_example Get an example contribution input ~73
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).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
No output schema declared.
No examples provided.
optimize_retirement_contributions Optimize Roth vs traditional contributions ~481
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accounts | object | – | Which accounts the user can use. Defaults: 401(k) and Roth 401(k) available, IRA allowed, no HSA, no match. |
| age | integer | yes | 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 | yes | Age you stop working. Must be above 'age'. |
| salary | number | yes | Your gross pay this year, in dollars. |
| social_security | object | – | Expected Social Security (household). Omitted = none modeled. |
| spending_in_retirement | number | yes | 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). |
No output schema declared.
No examples provided.
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.
remote · roth-vs-traditional-calculator.kindoflost.com
claude mcp add --transport http com-kindoflost-roth-vs-traditional-calculator-ro 'https://roth-vs-traditional-calculator.kindoflost.com/mcp'
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.