io.github.theluckystrike/amortization
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Loan and lease schedules: payment, interest, early settlement and the journal, to the minor unit.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1355 tokens (~123/item across 11 items; 9 tools + 2 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 Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "loan_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.theluckystrike/amortization MCP server?
io.github.theluckystrike/amortization is a hosted endpoint at https://mcp.zovo.one/mcp/amortization, 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 · mcp.zovo.one
claude mcp add --transport http theluckystrike-amortization 'https://mcp.zovo.one/mcp/amortization'
{
"mcpServers": {
"theluckystrike-amortization": {
"url": "https://mcp.zovo.one/mcp/amortization"
}
}
} {
"servers": {
"theluckystrike-amortization": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/amortization"
}
}
} [mcp_servers.theluckystrike-amortization] url = "https://mcp.zovo.one/mcp/amortization"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-amortization": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/amortization",
"enabled": true
}
}
} openclaw mcp add theluckystrike-amortization --url 'https://mcp.zovo.one/mcp/amortization' --transport streamable-http
mcp_servers:
theluckystrike-amortization:
url: "https://mcp.zovo.one/mcp/amortization" {
"McpServers": {
"theluckystrike-amortization": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/amortization"
}
}
} assistant mcp add theluckystrike-amortization -t streamable-http -u 'https://mcp.zovo.one/mcp/amortization'
{
"mcpServers": {
"theluckystrike-amortization": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/amortization"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 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.
- 18 Sept 26 +56
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.30 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Server version: 0.21.0 → 0.22.0 functional
- 17 Sept 26 −55
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 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 Sept 26 +1
- Tool “loans_report” rewrote its description, which is the text the model reads security
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Tool “loan_list” rewrote its description, which is the text the model reads security
- Tool “loan_journal” rewrote its description, which is the text the model reads security
- Schema quality: good → excellent functional
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 0
- Tool “loan_create” rewrote its description, which is the text the model reads security
- Tool “loan_list” rewrote its description, which is the text the model reads security
- Tool “loan_schedule” rewrote its description, which is the text the model reads security
- Tool “loans_report” rewrote its description, which is the text the model reads security
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Tool “license_status” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 98 functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: fail functional
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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/amortization
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| 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 mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/amortization | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/amortization | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/amortization |
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 →
license_activate Activate license ~76
Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
loan_create Record a loan or lease ~326
Record a loan or lease and return its id, level payment and effective annual rate. principal_minor, fees and balloon are whole MINOR units; rate_bps is the nominal annual rate in basis points. Free: 3 agreements.
| Name | Type | Req | Description |
|---|---|---|---|
| balloon_minor | integer | – | Final balloon or residual value in whole minor units, due with the last payment and not inside it. Default 0 |
| compounding | string | yes | How often interest compounds |
| currency | string | yes | ISO code the agreement is denominated in |
| fees_minor | integer | – | Arrangement fees in whole minor units, paid at drawdown. Default 0 |
| kind | string | – | Default "loan" |
| lender | string | – | Who the money is owed to |
| method | string | yes | annuity for a level payment, straight-principal for equal principal and a falling payment |
| name | string | yes | What this agreement is, e.g. Van finance or Office lease |
| note | string | – | – |
| payment_frequency | string | yes | How often a payment falls due |
| principal_minor | integer | yes | Amount borrowed, in whole minor units (integer cents). 1,000,000 is EUR 10,000.00 |
| rate_bps | integer | yes | Nominal annual interest rate in basis points. 1200 is 12 percent. Zero is allowed |
| start_date | string | yes | Drawdown date, YYYY-MM-DD. The first payment falls one period after it |
| term_periods | integer | yes | Number of payment periods, not years |
No output schema declared.
No examples provided.
loan_delete Delete a loan from the register ~71
Remove one loan or lease from the register and give its free-tier slot back. Refused, with the entry named, if a journal has already been taken from it. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| loan | string | yes | The loan id, e.g. LOAN-2026-0001, or its exact name |
No output schema declared.
No examples provided.
loan_journal Journal a loan payment ~194
Return the double entry for one payment period or month: debit interest expense and loan liability, credit cash, in the cash book's account names, with an expense_add-ready payload. Give period or month, not both. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| cash_account | string | – | Credit account for the payment. Default "cash" |
| category | string | – | Expense category for the expense_add payload. Default "interest" |
| interest_account | string | – | Debit account for the interest. Default "interest_expense" |
| liability_account | string | – | Debit account for the principal. Default "loan_liability" |
| loan | string | yes | The loan id, e.g. LOAN-2026-0001, or its exact name |
| month | string | – | Journal every payment falling in this month, YYYY-MM. Give this or period |
| period | integer | – | The payment period to journal. Give this or month |
No output schema declared.
No examples provided.
loan_list List the loan register ~116
List the register with terms, level payment, effective annual rate and, at as_of, periods paid, balance outstanding, interest to date and the next payment, totalled per currency. Free; loans_report is the Pro roll-up.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Value the register at this date, YYYY-MM-DD. Default today |
| currency | string | – | Only agreements in this currency |
| kind | string | – | Only loans, or only leases |
| limit | integer | – | Maximum rows, default and ceiling 600 |
No output schema declared.
No examples provided.
loan_repay_early Settle or overpay a loan early ~205
Work out what settling or overpaying costs as of a period: the outstanding balance, the penalty if one is given, the recalculated remaining schedule and the interest saved, stated gross and net of the penalty. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_period | integer | yes | The period the extra money is paid at the end of. Period 1 is the first payment |
| extra_minor | integer | – | A partial overpayment in whole minor units. Omit to settle the loan in full |
| keep_payment | boolean | – | On a partial overpayment, keep the same payment and shorten the term. Default false, which keeps the term and lowers the payment |
| limit | integer | – | Maximum remaining rows to return, ceiling 600 |
| loan | string | yes | The loan id, e.g. LOAN-2026-0001, or its exact name |
| penalty_minor | integer | – | Early repayment charge in whole minor units. Default 0 |
No output schema declared.
No examples provided.
loan_schedule Build the amortization schedule ~125
Build one loan's schedule: opening balance, payment, interest, principal and closing per period, with total interest. The last period absorbs rounding, landing exactly on the balloon or zero. loans_report totals it.
| Name | Type | Req | Description |
|---|---|---|---|
| from_period | integer | – | First period to return. Default 1 |
| limit | integer | – | Maximum rows, default and ceiling 600 |
| loan | string | yes | The loan id, e.g. LOAN-2026-0001, or its exact name |
| year | string | – | Only the periods falling in this calendar year, YYYY |
No output schema declared.
No examples provided.
loans_report Report what is owed and what it costs ~111
The debt at as_of: per loan what is outstanding, whether it is settled, the next payment, and the interest and principal charged in a year, then totals per currency. Contractual balance, not cash paid. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Value the debt at this date, YYYY-MM-DD. Default today |
| currency | string | – | Only agreements in this currency |
| year | string | – | The calendar year to total the interest for, YYYY. Default the year of as_of |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/amortization MCP server?
io.github.theluckystrike/amortization is an MCP server listed in the public MCP registry as io.github.theluckystrike/amortization. Loan and lease schedules: payment, interest, early settlement and the journal, to the minor unit. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/amortization).
Is the io.github.theluckystrike/amortization MCP server safe to use?
io.github.theluckystrike/amortization scores 82 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 io.github.theluckystrike/amortization MCP server expose?
io.github.theluckystrike/amortization exposes 9 tools: loan_create, loan_schedule, loan_repay_early, loan_journal, loan_list, and 4 more. Their descriptions and schemas cost roughly 1,279 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/amortization MCP server require authentication?
Yes. io.github.theluckystrike/amortization asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.theluckystrike/amortization MCP server still maintained?
io.github.theluckystrike/amortization is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.