Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Roth Conversion Calculator

REMOTE · ROTH-CONVERSION-CALCULATOR.KINDOFLOST.COM

Optimal Roth conversion plan by year: amounts, tax, and after-tax wealth vs no conversion. Free.

+3 this week 75 Trust /100

Last scanned (14 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 992 tokens (~330/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 Management37
  • Stability observed for 11 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
  • 93% 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 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.

  • 13 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.

  • 11 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 70

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://roth-conversion-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-conversion-calculator.kindoflost.com CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 89deb9c44a5decd113152b7909cd8442
SANs: roth-conversion-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-conversion-calculator.kindoflost.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
kindoflost.com. No DS 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-conversion-calculator.kindoflost.com/mcp Verified 200
http (plaintext) http://roth-conversion-calculator.kindoflost.com/mcp HTTPS enforced 301 https://roth-conversion-calculator.kindoflost.com/mcp
MCP tools · 3 exposed · ~627 tokens

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 →

Tool Tokens
check_request ~81

Say in plain words what the user wants (e.g. 'I'm still working and want to know Roth vs traditional 401k'). Returns whether this optimizer can do it and, if not, the closest thing it can do (or the sister server that can). Fast, no solve.

NameTypeReqDescription
descriptionstringyesThe user's question in a sentence or two.

No output schema declared.

No examples provided.

get_conversion_example ~79

Return a complete example input for optimize_roth_conversions with a one-line explanation of every field. No solve. Edit it to the user's situation. kind 'single' (default: a 60-year-old early retiree with a traditional IRA, a brokerage account and Social Security later) or 'married'.

NameTypeReqDescription
kindstring––

No output schema declared.

No examples provided.

optimize_roth_conversions ~467

Find the best Roth conversion amount for each year of a retirement plan, with living expenses funded from the right accounts and tax paid each year. Returns per-year conversions, taxes and balances, the after-tax wealth at the end with vs without conversions, totals, a plain-language plan narrative and the assumptions used. Advanced options (IRMAA, NIIT, real state brackets) are off by default. Runs in 1-3 seconds (up to ~15 with IRMAA/NIIT on a long horizon). All money in today's dollars. Optimal for the stated assumptions; not tax advice. Call get_conversion_example first if unsure of the shape.

NameTypeReqDescription
advancedobject–Advanced layers, all OFF by default exactly like the web tool. IRMAA and NIIT make the solve a MILP (a few seconds longer; each solve is capped at 5 s, best plan found is returned).
ageintegeryesYour age this year. The plan starts now (conversions can begin this year).
assumptionsobject–Modeling assumptions; the defaults (same as the web tool) are reported back.
balancesobjectyesCurrent household balances, dollars. Omitted = 0; at least one must be above 0.
end_ageinteger–Plan until this age (default 90; horizon at most 70 years).
filingstring–Tax filing status. Default 'single'. 'married' = one joint return (both spouses assumed the same age).
find_max_spendingboolean–Instead of fixed spending, solve for the highest constant yearly spending the accounts can fund, ending near $0. Default false.
other_incomeobject–Other steady ordinary income (pension, rental, part-time pay), today's dollars. Omitted = none.
social_securityobject–Expected Social Security (household). Omitted = none.
spending_end_ageinteger–Age spending ends (default: end of plan).
spending_per_yearnumber–Yearly spending the plan must fund, today's dollars, before income tax. Required unless find_max_spending is true.
spending_start_ageinteger–Age spending begins (default: now).

No output schema declared.

No examples provided.

Install

How do I install the Roth Conversion Calculator MCP server?

Roth Conversion Calculator is a hosted endpoint at https://roth-conversion-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-conversion-calculator.kindoflost.com

# add to Claude Code
claude mcp add --transport http com-kindoflost-roth-conversion-calculator-roth-c 'https://roth-conversion-calculator.kindoflost.com/mcp'
Common questions

What is the Roth Conversion Calculator MCP server?

Roth Conversion Calculator is an MCP server listed in the public MCP registry as com.kindoflost.roth-conversion-calculator/roth-conversion-c…. Optimal Roth conversion plan by year: amounts, tax, and after-tax wealth vs no conversion. Free. This page covers its hosted endpoint (https://roth-conversion-calculator.kindoflost.com/mcp).

Is the Roth Conversion Calculator MCP server safe to use?

Roth Conversion Calculator scores 75 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 Conversion Calculator MCP server expose?

Roth Conversion Calculator exposes 3 tools: get_conversion_example, optimize_roth_conversions, check_request. Their descriptions and schemas cost roughly 627 tokens of context every time the server is loaded.

Does the Roth Conversion Calculator MCP server require authentication?

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

Is the Roth Conversion Calculator MCP server still maintained?

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

What did VerifyMCP test on the Roth Conversion Calculator MCP server?

VerifyMCP ran 13 checks on Roth Conversion Calculator, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.