# Zovo Depreciation Schedule (remote · depreciation.zovo.one)

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

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `depreciation.zovo.one`: 78/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-depreciation/depreciation.md), [page](https://verifymcp.io/servers/theluckystrike-depreciation/depreciation)

## Channel facts

- Endpoint: `https://depreciation.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.
  - Supports UI / widget rendering.

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

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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-11-19 (score 78, +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.

### 2026-11-17 (score 77, +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.

### 2026-11-15 (score 76, +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-11-13 (score 75, +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.

### 2026-11-11 (score 74, +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.

### 2026-11-09 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 72)

First indexed and scored.

## MCP tools (2)

### `calculate_depreciation` (~834 tokens)

Calculate depreciation for one asset

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

Input parameters:

- `business_use_percent` (number|string|null): Business-use percent of the asset, e.g. 80 for 80%. Default 100. Basis and salvage are scaled by it.
- `convention` (string|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…
- `cost` (number|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_rate` (number|string|null): Declining balance rate in percent: 200 (default, double declining), 150 or 125.
- `land_value` (number|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.
- `method` (string|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…
- `name` (string|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_service` (string|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_class` (number|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_value` (number|string|null): Salvage (residual) value at the end of the life, e.g. 2000 or "10%". Default 0. Ignored by MACRS.
- `switch_to_straight_line` (boolean|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_total` (number|string|null): Units of production only: estimated total lifetime units, e.g. 100000 (miles, hours or pieces).
- `useful_life_years` (number|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.

Output parameters:

- `asset` (object)
- `assumptions` (array)
- `currency` (string)
- `downloads` (object)
- `ending_book_value` (number)
- `first_year` (object)
- `schedule` (array)
- `summary` (string)
- `tax_note` (string)
- `total_depreciation` (number)
- `warnings` (array)
- `years_count` (number)

### `generate_depreciation_schedule` (~492 tokens)

Generate a depreciation schedule for several assets

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

Input parameters:

- `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…
- `convention` (string|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_rate` (number|string|null): Default declining balance rate in percent, 200 or 150.
- `file` (object): 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…
- `method` (string|null): Default method for assets that do not name one, e.g. macrs or straight_line.
- `placed_in_service` (string|number|null): Default date placed in service for assets without one, e.g. 2026-01-01.
- `title` (string|null): Title for the PDF and spreadsheet, e.g. "Acme LLC fixed assets 2026".
- `useful_life_years` (number|string|null): Default useful life in years for book methods, e.g. 5.

Output parameters:

- `asset_count` (number)
- `assets` (array)
- `assets_not_shown` (number)
- `assumptions` (array)
- `by_year` (array)
- `currency` (string)
- `downloads` (object)
- `mid_quarter_test` (array)
- `skipped` (array)
- `skipped_count` (number)
- `summary` (string)
- `tax_note` (string)
- `total_cost_basis` (number)
- `total_depreciation` (number)
- `warnings` (array)

## Diagnostics

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

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74
- 2026-11-10: 73
- 2026-11-09: 73
- 2026-11-08: 72

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

## Links

- Remote endpoint: https://depreciation.zovo.one/mcp
- Website: https://depreciation.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-depreciation/depreciation.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-depreciation/depreciation/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-depreciation/depreciation.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-depreciation/depreciation
