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.

Amortization Schedule

REMOTE · AMORTIZE.GUMBALLTOOLS.COM · SCANNED SEP 25

Row-by-row loan amortization schedules: monthly or daily accrual, extra principal, PMI, biweekly.

+3 this week 73 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 973 tokens (~973/item across 1 items; 1 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 Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
Install

How do I install the Amortization Schedule MCP server?

Amortization Schedule is a hosted endpoint at https://amortize.gumballtools.com/api/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 · amortize.gumballtools.com

# add to Claude Code
claude mcp add --transport http com-gumballtools-amortize 'https://amortize.gumballtools.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-gumballtools-amortize": {
      "url": "https://amortize.gumballtools.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-gumballtools-amortize": {
      "type": "http",
      "url": "https://amortize.gumballtools.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-gumballtools-amortize]
url = "https://amortize.gumballtools.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-gumballtools-amortize": {
      "type": "remote",
      "url": "https://amortize.gumballtools.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-gumballtools-amortize --url 'https://amortize.gumballtools.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-gumballtools-amortize:
    url: "https://amortize.gumballtools.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-gumballtools-amortize": {
      "Transport": "http",
      "Url": "https://amortize.gumballtools.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-gumballtools-amortize -t streamable-http -u 'https://amortize.gumballtools.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "com-gumballtools-amortize": {
      "type": "http",
      "url": "https://amortize.gumballtools.com/api/mcp"
    }
  }
}

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

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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

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

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

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

  • 14 Sept 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.

  • 12 Sept 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.

  • 10 Sept 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.

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 25 Sept 2026 · Probed https://amortize.gumballtools.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.gumballtools.com CN=YR2,O=Let's Encrypt,C=US 6 Sept 2026 5 Dec 2026 RSA 2048 SHA256-RSA 60927985e79d22e7a1106139f609d74b0e4
SANs: *.gumballtools.com, gumballtools.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of amortize.gumballtools.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
gumballtools.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=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://amortize.gumballtools.com/api/mcp Verified 200
http (plaintext) http://amortize.gumballtools.com/api/mcp HTTPS enforced 308 https://amortize.gumballtools.com/api/mcp
MCP tools · 1 exposed · ~973 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
amortize ~973

Builds the full row-by-row amortization schedule for a loan — interest, principal, PMI, and running balance for every payment — instead of just the monthly payment amount. Use this whenever a row-by-row schedule matters: "what is my balance after payment 47", "what does an extra $200/month do to my payoff date", "when does PMI drop off", or "give me the whole amortization table". Do not do this arithmetic by hand or in your head. Two things go wrong reliably when a model tries: 1. THE LAST ROW. The textbook payment formula only amortizes to exactly zero in infinite precision. Rounded to cents and carried over up to a few hundred rows, a hand-rolled schedule drifts and ends with a balance of a few cents to a few dollars instead of zero — exactly the row a person checks against their real statement. This tool recomputes the final row as "remaining balance + that row's interest" so it always ends at zero, and reports the delta. 2. COMPOUNDING CONVENTION. Fixed mortgages compound monthly (rate/12). HELOCs, most auto loans, and most private student loans accrue interest DAILY on the actual number of days between payments, which is a genuinely different schedule, not a rounding variant. Guessing the wrong one silently produces a plausible but wrong table. Input: `principal`, `annualRatePercent` (e.g. 6.5), `termMonths` (integer), and `compounding` ("monthly" or "daily") are required. For `compounding: "daily"`, supply EITHER `startDate` (YYYY-MM-DD — the tool derives real day counts and leap years from the calendar itself) OR `dayCountBasis` ("30/360" | "actual/365" | "actual/actual") for a hypothetical loan with no dates — never both are needed, and supplying neither is refused rather than guessed. Optional: `paymentFrequency` ("monthly" default | "biweekly", which requires daily compounding — pass `paymentOverride` if the actual billed payment differs from the textbook one, e.g. a HELOC's quoted minimum; `extraPrincipal` as `{type:"oneOff",amount,atPaymentNumber}` o…

NameTypeReqDescription
annualRatePercentnumberyesThe annual interest rate as a percent, e.g. 6.5 for 6.5%.
compoundingstringyes"monthly": rate/12 per period, the fixed-mortgage norm. "daily": actual per-diem accrual, the HELOC/auto-loan/student-loan convention — requires startDate or dayCountBasis.
dayCountBasisstring–Required for daily compounding ONLY when there is no startDate (a hypothetical loan).
extraPrincipal––A one-off extra payment at a given payment number, or a recurring extra payment from a given payment number onward.
paymentFrequencystring–"biweekly" pays half the monthly payment every 14 days and requires compounding "daily".
paymentOverridenumber–The actual per-period payment, if different from the textbook one — e.g. a HELOC minimum payment.
pmiobject–Models PMI dropping off at 78% (automatic, default) or 80% (requestable) of originalValue.
principalnumberyesThe loan amount, > 0.
startDatestring–YYYY-MM-DD. For daily compounding, supplying this lets the tool read real day counts and leap years off the calendar.
termMonthsintegeryesThe original term in whole months, e.g. 360 for 30 years.

No output schema declared.

No examples provided.

Common questions

What is the Amortization Schedule MCP server?

Amortization Schedule is an MCP server listed in the public MCP registry as com.gumballtools/amortize. Row-by-row loan amortization schedules: monthly or daily accrual, extra principal, PMI, biweekly. This page covers its hosted endpoint (https://amortize.gumballtools.com/api/mcp).

Is the Amortization Schedule MCP server safe to use?

Amortization Schedule scores 73 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 Amortization Schedule MCP server expose?

Amortization Schedule exposes 1 tool: amortize. Their descriptions and schemas cost roughly 973 tokens of context every time the server is loaded.

Does the Amortization Schedule MCP server require authentication?

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

Is the Amortization Schedule MCP server still maintained?

Amortization Schedule is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.