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.

Zovo Installment Planner

REMOTE · INSTALLMENT-PLAN.ZOVO.ONE

Split an amount into a payment plan schedule with exact installments.

+3 this week 78 Trust /100

Last scanned (22 hours ago)

Scores higher than 71% 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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability66
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 984 tokens (~492/item across 2 items; 1 tools + 1 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 Management43
  • Stability observed for 13 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
  • 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 1 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

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

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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 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.

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

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

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

  • 10 Nov 26 +1

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

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 72

    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://installment-plan.zovo.one/mcp

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 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 1a6be51dae225a780e14b5b59cd24fa3
SANs: zovo.one, *.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 installment-plan.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. 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
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://installment-plan.zovo.one/mcp Verified 200
http (plaintext) http://installment-plan.zovo.one/mcp HTTPS enforced 301 https://installment-plan.zovo.one/mcp
MCP tools · 1 exposed · ~856 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
generate_installment_plan ~856

Use this when the user wants a payment plan or installment schedule ("split 1200 into 6 monthly payments", "payment plan template", "installment plan for a customer", "pay this off in 4 payments every 2 weeks", "payment schedule with a deposit"). Pass total_amount, installments or installment_amount, frequency and first_due_date; optional deposit (amount or percent), annual_interest_rate (flat simple interest), rounding_rule, round_to, weekend_rule, payer_name, payee_name, plan_title and reference. Returns exact installment amounts that add up to the total, due dates, the remaining balance after each payment, and a printable PDF schedule with signature lines, an Excel file, a CSV and an ICS calendar file with a reminder before each payment. Ask for the first due date if it is unknown. Does not compute amortizing loan payments or APR, does not collect payments, and is not legal or financial advice.

NameTypeReqDescription
annual_interest_ratenumber|string|null–Optional flat simple interest in percent a year on the amount paid in installments, e.g. 6 or "5.25%". Default 0 (interest-free).
currencystring|null–ISO currency code, e.g. USD (default), EUR, GBP, JPY. A symbol in total_amount (€, £, ¥) also sets it.
depositnumber|string|null–Optional down payment taken off the total first: an amount, e.g. 300, or a percent of the total, e.g. "20%".
deposit_datestring|null–Optional date the deposit is paid, e.g. "2026-11-15". Without it the deposit is shown as paid on signing.
first_due_datestring|null–Date of the first installment, e.g. "2026-12-01". Required: ask the user if it is not known.
frequencystring|null–weekly, biweekly (every 2 weeks), semimonthly (twice a month: the 1st and 15th when the first date is the 1st), monthly (default) or quarterly.
installment_amountnumber|string|null–Fixed amount of each installment instead of a count, e.g. 250; the last one is the smaller rest.
installmentsnumber|string|null–Number of installments, 1 to 360, e.g. 6. Give this or installment_amount.
page_sizestring|null–PDF page size: Letter (default) or A4.
payee_name––Optional name of the person or business being paid, e.g. "Northside Dental".
payer_name––Optional name of the person or business paying, printed on the schedule, e.g. "Sam Lee".
plan_title––Optional title, e.g. "Payment plan for invoice 1042". Default "Payment schedule".
reference––Optional reference such as an invoice or account label, e.g. "INV-1042". Do not pass bank or card numbers.
reminder_days_beforenumber|string|null–Days before each due date for the calendar reminder, 0 to 30. Default 2.
reminder_timestring|null–Time of the reminder, e.g. "09:00" (default).
round_tonumber|string|null–Make installments multiples of this amount, e.g. 0.01 (default, to the cent), 1, 5 or 10.
rounding_rulestring|null–remainder_last (default: equal installments rounded down, the last one takes the rest), remainder_first (the first takes the rest) or even_up (each rounded up, the last one is smaller).
total_amountnumber|string|null–The full amount owed before any deposit, e.g. 1200 or "$2,450.00" or "1.250,00 €".
weekend_rulestring|null–none (default), next_business_day (Saturday or Sunday moves to Monday) or previous_business_day (moves to Friday). Holidays are not known.
NameTypeReqDescription
currencystringyes–
depositstringyes–
deposit_datestring|nullyes–
different_installment–yes–
downloadsobjectyes–
financedstringyes–
first_duestringyes–
frequencystringyes–
installmentsnumberyes–
interestobjectyes–
last_duestringyes–
links_expire_minutesnumber|nullyes–
notesarrayyes–
notes_countobject––
regular_installmentstringyes–
schedulearrayyes–
schedule_countobject––
titlestringyes–
totalstringyes–
total_of_installmentsstringyes–
total_to_paystringyes–

No examples provided.

Install

How do I install the Zovo Installment Planner MCP server?

Zovo Installment Planner is a hosted endpoint at https://installment-plan.zovo.one/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 · installment-plan.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-installment-plan 'https://installment-plan.zovo.one/mcp'
Common questions

What is the Zovo Installment Planner MCP server?

Zovo Installment Planner is an MCP server listed in the public MCP registry as io.github.theluckystrike/installment-plan. Split an amount into a payment plan schedule with exact installments. This page covers its hosted endpoint (https://installment-plan.zovo.one/mcp).

Is the Zovo Installment Planner MCP server safe to use?

Zovo Installment Planner scores 78 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 Zovo Installment Planner MCP server expose?

Zovo Installment Planner exposes 1 tool: generate_installment_plan. Their descriptions and schemas cost roughly 856 tokens of context every time the server is loaded.

Does the Zovo Installment Planner MCP server require authentication?

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

Is the Zovo Installment Planner MCP server still maintained?

Zovo Installment Planner 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 Zovo Installment Planner MCP server?

VerifyMCP ran 14 checks on Zovo Installment Planner, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. 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.