# io.github.theluckystrike/lease-schedule (remote · mcp.zovo.one)

Lease schedules with a residual: the payment, the interest split and the journal per month.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

- remote · `mcp.zovo.one`: 84/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-lease-schedule/mcp-lease-schedule.md), [page](https://verifymcp.io/servers/theluckystrike-lease-schedule/mcp-lease-schedule)
- mcpb · `amortization.mcpb`: 49/100, [markdown](https://verifymcp.io/servers/theluckystrike-lease-schedule/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-amortizati.md), [page](https://verifymcp.io/servers/theluckystrike-lease-schedule/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-amortizati)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/lease-schedule`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.22.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-30.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.theluckystrike/lease-schedule MCP server?

io.github.theluckystrike/lease-schedule is a hosted endpoint at https://mcp.zovo.one/mcp/lease-schedule, 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-lease-schedule 'https://mcp.zovo.one/mcp/lease-schedule'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-lease-schedule": {
      "url": "https://mcp.zovo.one/mcp/lease-schedule"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-lease-schedule": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/lease-schedule"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-lease-schedule]
url = "https://mcp.zovo.one/mcp/lease-schedule"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-lease-schedule": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/lease-schedule",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-lease-schedule --url 'https://mcp.zovo.one/mcp/lease-schedule' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-lease-schedule:
    url: "https://mcp.zovo.one/mcp/lease-schedule"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-lease-schedule": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/lease-schedule"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-lease-schedule -t streamable-http -u 'https://mcp.zovo.one/mcp/lease-schedule'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-lease-schedule": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/lease-schedule"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-30 (score 84, +1)

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

### 2026-09-28 (score 83, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 82, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 81, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-23 (score 81)

First indexed and scored.

## MCP tools (9)

### `loan_create` (~326 tokens)

Record a loan or lease

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.

Input parameters:

- `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, required): How often interest compounds
- `currency` (string, required): 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, required): annuity for a level payment, straight-principal for equal principal and a falling payment
- `name` (string, required): What this agreement is, e.g. Van finance or Office lease
- `note` (string)
- `payment_frequency` (string, required): How often a payment falls due
- `principal_minor` (integer, required): Amount borrowed, in whole minor units (integer cents). 1,000,000 is EUR 10,000.00
- `rate_bps` (integer, required): Nominal annual interest rate in basis points. 1200 is 12 percent. Zero is allowed
- `start_date` (string, required): Drawdown date, YYYY-MM-DD. The first payment falls one period after it
- `term_periods` (integer, required): Number of payment periods, not years

### `loan_schedule` (~125 tokens)

Build the amortization schedule

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.

Input parameters:

- `from_period` (integer): First period to return. Default 1
- `limit` (integer): Maximum rows, default and ceiling 600
- `loan` (string, required): The loan id, e.g. LOAN-2026-0001, or its exact name
- `year` (string): Only the periods falling in this calendar year, YYYY

### `loan_repay_early` (~205 tokens)

Settle or overpay a loan early

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.

Input parameters:

- `as_of_period` (integer, required): 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, required): The loan id, e.g. LOAN-2026-0001, or its exact name
- `penalty_minor` (integer): Early repayment charge in whole minor units. Default 0

### `loan_journal` (~194 tokens)

Journal a loan payment

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.

Input parameters:

- `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, required): 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

### `loan_list` (~116 tokens)

List the loan register

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.

Input parameters:

- `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

### `loan_delete` (~71 tokens)

Delete a loan from the register

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.

Input parameters:

- `loan` (string, required): The loan id, e.g. LOAN-2026-0001, or its exact name

### `loans_report` (~111 tokens)

Report what is owed and what it costs

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.

Input parameters:

- `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

### `license_status` (~55 tokens)

License status

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.

### `license_activate` (~76 tokens)

Activate license

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.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-lease-schedule/mcp-lease-schedule#diagnostics

## Score history

- 2026-09-30: 84
- 2026-09-29: 83
- 2026-09-28: 83
- 2026-09-27: 82
- 2026-09-26: 82
- 2026-09-25: 82
- 2026-09-24: 81
- 2026-09-23: 81

## Common questions

### What is the io.github.theluckystrike/lease-schedule MCP server?

io.github.theluckystrike/lease-schedule is an MCP server listed in the public MCP registry as io.github.theluckystrike/lease-schedule. Lease schedules with a residual: the payment, the interest split and the journal per month. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/lease-schedule).

### Is the io.github.theluckystrike/lease-schedule MCP server safe to use?

io.github.theluckystrike/lease-schedule scores 84 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/lease-schedule MCP server expose?

io.github.theluckystrike/lease-schedule 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/lease-schedule MCP server require authentication?

Yes. io.github.theluckystrike/lease-schedule 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/lease-schedule MCP server still maintained?

io.github.theluckystrike/lease-schedule is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/lease-schedule
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/amortization
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-lease-schedule/mcp-lease-schedule.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-lease-schedule/mcp-lease-schedule.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-lease-schedule/mcp-lease-schedule