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 Depreciation Schedule

REMOTE · DEPRECIATION.ZOVO.ONE

Depreciation calculator for tax and bookkeeping, for small businesses, landlords and bookkeepers.

+3 this week 78 Trust /100

Last scanned (16 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 Usability69
  • 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 1480 tokens (~493/item across 3 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

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

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

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

  • 9 Nov 26 +1
    • 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://depreciation.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 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 f98f984e77bc662f139a81a47db56811
SANs: zovo.one, depreciation.zovo.one, *.depreciation.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 depreciation.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://depreciation.zovo.one/mcp Verified 200
http (plaintext) http://depreciation.zovo.one/mcp HTTPS enforced 301 https://depreciation.zovo.one/mcp
MCP tools · 2 exposed · ~1,326 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
calculate_depreciation ~834

Use this when the user wants a depreciation calculator result for one asset: a straight-line depreciation schedule, double declining balance or 150% declining balance, sum-of-the-years' digits, units of production, or a MACRS depreciation calculator result for a computer, vehicle, equipment, rental property (27.5-year) or commercial building (39-year). Only cost is required; method, life or property class, salvage value and date placed in service are optional with stated defaults. Returns the year-by-year schedule (depreciation, accumulated depreciation, book value) to the cent, and PDF, Excel and CSV downloads. Does not model Section 179, bonus depreciation, ADS or dispositions, and is not tax advice. Do not use for several assets (use generate_depreciation_schedule).

NameTypeReqDescription
business_use_percentnumber|string|null–Business-use percent of the asset, e.g. 80 for 80%. Default 100. Basis and salvage are scaled by it.
conventionstring|null–First-year convention. MACRS: half_year (default) or mid_quarter; real property always uses mid_month. Book methods: full_month (default, the month placed in service counts), mid_month, half_year or…
costnumber|string|null–Required. Cost basis of the asset (purchase price plus sales tax, shipping and installation), e.g. 25000 or "$25,000". For a building, leave out the land value.
declining_ratenumber|string|null–Declining balance rate in percent: 200 (default, double declining), 150 or 125.
land_valuenumber|string|null–Land value included in cost, e.g. 70000 for a house bought with its lot. It is taken out of the basis because land is not depreciable.
methodstring|null–Depreciation method: straight_line (default), double_declining (200% declining balance), 150db, declining_balance, sum_of_years, units_of_production, or macrs (US tax, IRS Pub 946 tables). Synonyms l…
namestring|null–Asset name or description, e.g. "Dell laptop" or "Rental house at 12 Oak St". Also used to pick a MACRS class or a default life when none is given.
placed_in_servicestring|number|null–Date placed in service, e.g. 2026-03-15, "March 2026" or 03/15/2026 (US order). Only the month and year matter. Default January of this year.
property_classnumber|string|null–MACRS GDS recovery period: 3, 5, 7, 10, 15, 20, 27.5 (residential rental) or 39 (nonresidential real property), or words like "residential rental", "computer", "office furniture".
salvage_valuenumber|string|null–Salvage (residual) value at the end of the life, e.g. 2000 or "10%". Default 0. Ignored by MACRS.
switch_to_straight_lineboolean|string|null–Declining balance only: switch to straight-line when it gives more depreciation. Default true.
units_per_year––Units of production only: units used each year starting with the year placed in service, e.g. [20000, 25000, 18000] or "20000, 25000, 18000".
units_totalnumber|string|null–Units of production only: estimated total lifetime units, e.g. 100000 (miles, hours or pieces).
useful_life_yearsnumber|string|null–Useful life in years for book methods, e.g. 5 or "7 years" or "60 months". Default from the property class or the description, else 5.
NameTypeReqDescription
assetobjectyes–
assumptionsarrayyes–
currencystringyes–
downloadsobjectyes–
ending_book_valuenumberyes–
first_yearobjectyes–
schedulearrayyes–
summarystringyes–
tax_notestringyes–
total_depreciationnumberyes–
warningsarrayyes–
years_countnumberyes–

No examples provided.

generate_depreciation_schedule ~492

Use this when the user wants a depreciation schedule template filled in for several assets or a fixed asset register: a list of assets, pasted CSV, or an attached CSV/Excel file, each with cost, date placed in service and method (straight-line, declining balance, sum-of-the-years' digits, units of production or MACRS). Returns each asset's schedule, totals by year, the IRS 40% mid-quarter test for MACRS assets, and a PDF, Excel workbook and CSV. Rows that cannot be read are listed with the reason, never dropped silently. Does not model Section 179, bonus depreciation, ADS or dispositions, and is not tax advice. Do not use for a single asset (use calculate_depreciation).

NameTypeReqDescription
assets––The assets: an array of objects with name, cost, placed_in_service, method, useful_life_years or property_class, salvage_value, e.g. [{"name":"Laptop","cost":2400,"placed_in_service":"2026-03-15","me…
conventionstring|null–Default convention. For MACRS leave it out to let the 40% mid-quarter test decide per year, or pass half_year or mid_quarter.
declining_ratenumber|string|null–Default declining balance rate in percent, 200 or 150.
fileobject–Optional fixed-asset list as a CSV, TSV or Excel .xlsx file with one asset per row, e.g. fixed-assets.xlsx. Columns like Asset, Cost, Date placed in service, Method, Life or Class, Salvage are detect…
methodstring|null–Default method for assets that do not name one, e.g. macrs or straight_line.
placed_in_servicestring|number|null–Default date placed in service for assets without one, e.g. 2026-01-01.
titlestring|null–Title for the PDF and spreadsheet, e.g. "Acme LLC fixed assets 2026".
useful_life_yearsnumber|string|null–Default useful life in years for book methods, e.g. 5.
NameTypeReqDescription
asset_countnumberyes–
assetsarrayyes–
assets_not_shownnumberyes–
assumptionsarrayyes–
by_yeararrayyes–
currencystringyes–
downloadsobjectyes–
mid_quarter_testarrayyes–
skippedarrayyes–
skipped_countnumberyes–
summarystringyes–
tax_notestringyes–
total_cost_basisnumberyes–
total_depreciationnumberyes–
warningsarrayyes–

No examples provided.

Install

How do I install the Zovo Depreciation Schedule MCP server?

Zovo Depreciation Schedule is a hosted endpoint at https://depreciation.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 · depreciation.zovo.one

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

What is the Zovo Depreciation Schedule MCP server?

Zovo Depreciation Schedule is an MCP server listed in the public MCP registry as io.github.theluckystrike/depreciation. Depreciation calculator for tax and bookkeeping, for small businesses, landlords and bookkeepers. This page covers its hosted endpoint (https://depreciation.zovo.one/mcp).

Is the Zovo Depreciation Schedule MCP server safe to use?

Zovo Depreciation Schedule 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 Depreciation Schedule MCP server expose?

Zovo Depreciation Schedule exposes 2 tools: calculate_depreciation, generate_depreciation_schedule. Their descriptions and schemas cost roughly 1,326 tokens of context every time the server is loaded.

Does the Zovo Depreciation Schedule MCP server require authentication?

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

Is the Zovo Depreciation Schedule MCP server still maintained?

Zovo Depreciation Schedule 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 Depreciation Schedule MCP server?

VerifyMCP ran 14 checks on Zovo Depreciation Schedule, 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.