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.

io.github.theluckystrike/lease-schedule

REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 30

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

+3 this week 84 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 Security94
Transport & Reachability100
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 Management23
  • Stability observed for 7 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • 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
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.

remote · mcp.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-lease-schedule 'https://mcp.zovo.one/mcp/lease-schedule'
// .cursor/mcp.json
{
  "mcpServers": {
    "theluckystrike-lease-schedule": {
      "url": "https://mcp.zovo.one/mcp/lease-schedule"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "theluckystrike-lease-schedule": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/lease-schedule"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add theluckystrike-lease-schedule --url 'https://mcp.zovo.one/mcp/lease-schedule' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  theluckystrike-lease-schedule:
    url: "https://mcp.zovo.one/mcp/lease-schedule"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "theluckystrike-lease-schedule": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/lease-schedule"
    }
  }
}
# add to Vellum
assistant mcp add theluckystrike-lease-schedule -t streamable-http -u 'https://mcp.zovo.one/mcp/lease-schedule'
// mcp.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 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.

  • 30 Sept 26 +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.

  • 28 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
  • 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
  • 24 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 23 Sept 26 81

    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 30 Sept 2026 · Probed https://mcp.zovo.one/mcp/lease-schedule

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 Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource"

Bearer realm="mcp.zovo.one", error="invalid_token", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

Protected resource metadata

Document https://mcp.zovo.one/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.zovo.one
Authorisation server https://mcp.zovo.one

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/lease-schedule Verified 200
http (plaintext) http://mcp.zovo.one/mcp/lease-schedule HTTPS enforced 301 https://mcp.zovo.one/mcp/lease-schedule
MCP tools · 9 exposed · ~1,279 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
license_activate ~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.

NameTypeReqDescription
keystringyesLicense key from checkout, MCPL1.<payload>.<signature>

No output schema declared.

No examples provided.

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 ~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.

NameTypeReqDescription
balloon_minorinteger–Final balloon or residual value in whole minor units, due with the last payment and not inside it. Default 0
compoundingstringyesHow often interest compounds
currencystringyesISO code the agreement is denominated in
fees_minorinteger–Arrangement fees in whole minor units, paid at drawdown. Default 0
kindstring–Default "loan"
lenderstring–Who the money is owed to
methodstringyesannuity for a level payment, straight-principal for equal principal and a falling payment
namestringyesWhat this agreement is, e.g. Van finance or Office lease
notestring––
payment_frequencystringyesHow often a payment falls due
principal_minorintegeryesAmount borrowed, in whole minor units (integer cents). 1,000,000 is EUR 10,000.00
rate_bpsintegeryesNominal annual interest rate in basis points. 1200 is 12 percent. Zero is allowed
start_datestringyesDrawdown date, YYYY-MM-DD. The first payment falls one period after it
term_periodsintegeryesNumber of payment periods, not years

No output schema declared.

No examples provided.

loan_delete ~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.

NameTypeReqDescription
loanstringyesThe loan id, e.g. LOAN-2026-0001, or its exact name

No output schema declared.

No examples provided.

loan_journal ~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.

NameTypeReqDescription
cash_accountstring–Credit account for the payment. Default "cash"
categorystring–Expense category for the expense_add payload. Default "interest"
interest_accountstring–Debit account for the interest. Default "interest_expense"
liability_accountstring–Debit account for the principal. Default "loan_liability"
loanstringyesThe loan id, e.g. LOAN-2026-0001, or its exact name
monthstring–Journal every payment falling in this month, YYYY-MM. Give this or period
periodinteger–The payment period to journal. Give this or month

No output schema declared.

No examples provided.

loan_list ~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.

NameTypeReqDescription
as_ofstring–Value the register at this date, YYYY-MM-DD. Default today
currencystring–Only agreements in this currency
kindstring–Only loans, or only leases
limitinteger–Maximum rows, default and ceiling 600

No output schema declared.

No examples provided.

loan_repay_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.

NameTypeReqDescription
as_of_periodintegeryesThe period the extra money is paid at the end of. Period 1 is the first payment
extra_minorinteger–A partial overpayment in whole minor units. Omit to settle the loan in full
keep_paymentboolean–On a partial overpayment, keep the same payment and shorten the term. Default false, which keeps the term and lowers the payment
limitinteger–Maximum remaining rows to return, ceiling 600
loanstringyesThe loan id, e.g. LOAN-2026-0001, or its exact name
penalty_minorinteger–Early repayment charge in whole minor units. Default 0

No output schema declared.

No examples provided.

loan_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.

NameTypeReqDescription
from_periodinteger–First period to return. Default 1
limitinteger–Maximum rows, default and ceiling 600
loanstringyesThe loan id, e.g. LOAN-2026-0001, or its exact name
yearstring–Only the periods falling in this calendar year, YYYY

No output schema declared.

No examples provided.

loans_report ~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.

NameTypeReqDescription
as_ofstring–Value the debt at this date, YYYY-MM-DD. Default today
currencystring–Only agreements in this currency
yearstring–The calendar year to total the interest for, YYYY. Default the year of as_of

No output schema declared.

No examples provided.

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.