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.

Money Tools

REMOTE · MONEY-TOOLS-547074823179.ASIA-SOUTH1.RUN.APP

US retirement calculators with every number cited to official SSA and Medicare sources.

+3 this week 65 Trust /100

Last scanned (18 hours ago)

Scores higher than 46% 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 Security57
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 540 tokens (~180/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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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 3 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 (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

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

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 0
    • Schema quality: 342 → 540 ▼ functional
    • Server version: 0.1.0 → 0.2.0 functional
    • New tool “rmd” functional
  • 14 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 61

    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://money-tools-547074823179.asia-south1.run.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.a.run.app CN=WE2,O=Google Trust Services,C=US 3 Nov 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 f668c9036838957b095b05d18ab2228d
SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more
CN=WE2,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 7ff32d6b409d15d5965b05873a7c72e0
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 money-tools-547074823179.asia-south1.run.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
run.app. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://money-tools-547074823179.asia-south1.run.app/mcp Verified 200
http (plaintext) http://money-tools-547074823179.asia-south1.run.app/mcp HTTPS enforced 302 https://money-tools-547074823179.asia-south1.run.app/mcp
MCP tools · 3 exposed · ~540 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
rmd ~198

Required minimum distributions (RMDs) for a US traditional IRA owner. Args: birth_year: account owner's year of birth (1935-1965). balance: total balance of all traditional/SEP/SIMPLE IRAs as of last December 31, USD. Returns JSON with the next three RMD years: age attained, IRS Uniform Lifetime Table divisor, the RMD amount, and each deadline (first RMD due April 1 of the following year). RMD ages from Treasury/IRS final rule 89 FR 58886: 73 for births 1951-1958, 75 for 1960+; 1959 births are flagged (statute is ambiguous, calculated at 73). Missed-RMD excise tax is 25%, 10% if corrected within two years.

NameTypeReqDescription
balancenumberyes–
birth_yearintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

roth_irmaa ~175

What a Roth conversion does to Medicare costs (2026 IRMAA tiers). Args: status: filing status: "single", "joint" (married filing jointly) or "separate" (married filing separately). magi: modified adjusted gross income before the conversion, USD. roth_conversion: extra income the Roth conversion would add, USD. Returns JSON with the IRMAA tier before and after, Part B monthly premium, Part D surcharge, the extra annual Medicare cost per person, and the MAGI room left before the next bracket cliff. Tiers from the official Medicare 2026 costs fact sheet; IRMAA is a two-year lookback.

NameTypeReqDescription
maginumberyes–
roth_conversionnumber––
statusstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

ss_break_even ~167

Social Security claiming break-even analysis for a US worker. Args: birth_year: worker's year of birth (1938-2010). pia: monthly retirement benefit at full retirement age in USD, as printed on the worker's ssa.gov statement. claim_ages: whole claiming ages to compare, each 62-70 (default 62, 67, 70). Returns JSON with each age's monthly benefit, cumulative totals to 75/80/85/90 (today's dollars), and the break-even age for each pair. Rules and factors from ssa.gov/OACT (nra.html, early_late.html).

NameTypeReqDescription
birth_yearintegeryes–
claim_ages–––
pianumberyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the Money Tools MCP server?

Money Tools is a hosted endpoint at https://money-tools-547074823179.asia-south1.run.app/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 · money-tools-547074823179.asia-south1.run.app

# add to Claude Code
claude mcp add --transport http vsjagati-money-tools 'https://money-tools-547074823179.asia-south1.run.app/mcp'
Common questions

What is the Money Tools MCP server?

Money Tools is an MCP server listed in the public MCP registry as io.github.vsjagati/money-tools. US retirement calculators with every number cited to official SSA and Medicare sources. This page covers its hosted endpoint (https://money-tools-547074823179.asia-south1.run.app/mcp).

Is the Money Tools MCP server safe to use?

Money Tools scores 65 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 Money Tools MCP server expose?

Money Tools exposes 3 tools: ss_break_even, roth_irmaa, rmd. Their descriptions and schemas cost roughly 540 tokens of context every time the server is loaded.

Does the Money Tools MCP server require authentication?

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

Is the Money Tools MCP server still maintained?

Money Tools 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 Money Tools MCP server?

VerifyMCP ran 12 checks on Money Tools, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Money Tools: Authorization. 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.