io.github.theluckystrike/asset-register
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Fixed assets and depreciation from bundled Polish KST, HMRC and IRS MACRS tables.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 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 1720 tokens (~156/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 Management37
- Stability observed for 11 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "asset_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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
How do I install the io.github.theluckystrike/asset-register MCP server?
io.github.theluckystrike/asset-register is a hosted endpoint at https://mcp.zovo.one/mcp/asset-register, 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
claude mcp add --transport http theluckystrike-asset-register 'https://mcp.zovo.one/mcp/asset-register'
{
"mcpServers": {
"theluckystrike-asset-register": {
"url": "https://mcp.zovo.one/mcp/asset-register"
}
}
} {
"servers": {
"theluckystrike-asset-register": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/asset-register"
}
}
} [mcp_servers.theluckystrike-asset-register] url = "https://mcp.zovo.one/mcp/asset-register"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-asset-register": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/asset-register",
"enabled": true
}
}
} openclaw mcp add theluckystrike-asset-register --url 'https://mcp.zovo.one/mcp/asset-register' --transport streamable-http
mcp_servers:
theluckystrike-asset-register:
url: "https://mcp.zovo.one/mcp/asset-register" {
"McpServers": {
"theluckystrike-asset-register": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/asset-register"
}
}
} assistant mcp add theluckystrike-asset-register -t streamable-http -u 'https://mcp.zovo.one/mcp/asset-register'
{
"mcpServers": {
"theluckystrike-asset-register": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/asset-register"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 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 Sept 26 +1
- Server version: 0.21.0 → 0.22.0 functional
- 15 Sept 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.
- 13 Sept 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.
- 11 Sept 26 +1
- Tool “asset_report” rewrote its description, which is the text the model reads security
- Tool “license_activate” rewrote its description, which is the text the model reads security
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 0
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Tool “license_status” rewrote its description, which is the text the model reads security
- Tool “asset_dispose” rewrote its description, which is the text the model reads security
- Tool “asset_report” rewrote its description, which is the text the model reads security
- Tool “asset_schedule” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Tool coverage: 98 functional
- 5 Sept 26 36
First indexed and scored.
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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/asset-register
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 Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
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/asset-register | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/asset-register | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/asset-register |
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 →
asset_add Add a fixed asset ~466
Add one fixed asset to the register and return its id with the rate, useful life and convention taken from the bundled tax table. Cost and residual are whole minor units. Free tier holds ten assets.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | A code or name from the bundled table, e.g. "487" or "Computers and computer sets" (pl), "main" (uk), "5-year" (us). Read assets://categories for the list |
| cost_minor | integer | yes | Acquisition cost in MINOR units (integer cents/grosze), e.g. 549900 for 5499.00. Never a decimal |
| currency | string | – | ISO code. Defaults to the shared business profile currency, else the scheme table currency |
| declining_coefficient | number | – | Declining-balance coefficient. Polish default 2.0, capped by the table; ignored with straight-line |
| in_service_date | string | – | ISO date YYYY-MM-DD the asset entered use and the register. Defaults to purchase_date |
| life_years | number | – | Override the useful life derived from the table, in years. The answer reports that it was an override |
| method | string | – | "straight-line" or "declining-balance". Default: the table row method, straight-line for the Polish annex and the reducing-balance pool rate for the UK |
| name | string | yes | What the asset is, e.g. "MacBook Pro 16" or "Delivery van" |
| note | string | – | – |
| project | string | – | Project, department or cost centre this asset belongs to |
| purchase_date | string | yes | ISO date YYYY-MM-DD the asset was bought |
| rate_pct | number | – | Override the annual percentage derived from the table. Use for a lowered Polish rate under art. 16i |
| residual_minor | integer | – | Residual or salvage value in MINOR units, default 0. Must be less than cost. MACRS ignores it and the answer says so |
| scheme | string | – | "pl" Polish KST annex rates, "uk" HMRC capital allowance pools, "us" IRS MACRS GDS. Omit to derive it from the shared business profile currency |
No output schema declared.
No examples provided.
asset_delete Delete an asset ~77
Remove one asset from the register when nothing depends on it: not disposed of, never journaled. Its free-tier slot is free again. An asset with a dependent is refused and the dependent is named. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset id such as ASSET-2026-0001, or an exact or partial name |
No output schema declared.
No examples provided.
asset_dispose Dispose of an asset ~152
Record that an asset left the business on a date and return the gain or loss against net book value. proceeds_minor is in MINOR units. Depreciation stops here, and a second disposal is refused.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset id such as ASSET-2026-0001, or an exact or partial name |
| date | string | yes | ISO date YYYY-MM-DD the asset left the business. It cannot be before the in-service date |
| note | string | – | What happened, e.g. sold to a dealer, written off after a fire |
| proceeds_minor | integer | – | Sale proceeds in MINOR units, default 0 for a scrapping or a write-off |
No output schema declared.
No examples provided.
asset_journal Journal the month's depreciation ~157
Return the depreciation journal for one month: debit depreciation expense and credit accumulated depreciation, per asset and in total, plus an expense_add-ready payload per currency. It writes no expense. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| accumulated_account | string | – | Credit account name. Default "Accumulated depreciation" |
| category | string | – | Expense category to put on the expense_add payload. Default "depreciation" |
| expense_account | string | – | Debit account name. Default "Depreciation expense" |
| month | string | yes | The month to journal, YYYY-MM. A date YYYY-MM-DD is read as its month |
| project | string | – | Only assets on this project or cost centre |
| scheme | string | – | Only assets on this tax scheme |
No output schema declared.
No examples provided.
asset_list List the fixed asset register ~161
List the assets in the register with cost, method, rate and net book value at a date, filtered by scheme, category, project, currency or disposal state. Free and unlimited.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Value the register at this month or date, YYYY-MM or YYYY-MM-DD. Default today |
| category | string | – | Only assets in this table category code or name |
| currency | string | – | Only assets held in this currency |
| include_disposed | boolean | – | Include assets already disposed of. Default false |
| limit | integer | – | Maximum rows, default and ceiling 2000 |
| project | string | – | Only assets on this project or cost centre |
| scheme | string | – | Only assets on this tax scheme |
No output schema declared.
No examples provided.
asset_report Report the register ~143
For one year: net book value by category, scheme and currency at as_of, the year's depreciation charge per currency, and every disposal with its gain or loss. Pro; asset_list and asset_schedule are free per-asset views.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Value the register at this month or date, YYYY-MM or YYYY-MM-DD. Default the last day of the year |
| project | string | – | Only assets on this project or cost centre |
| scheme | string | – | Only assets on this tax scheme |
| year | integer | – | Calendar year to report, e.g. 2026. Default the year of as_of, else this year |
No output schema declared.
No examples provided.
asset_schedule Build a depreciation schedule ~347
Build the depreciation schedule for a stored asset, or price one not in the register, per year or per month, to residual or zero, with the table's rate, life and convention. Periods sum exactly to the base.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Asset id such as ASSET-2026-0001, or an exact or partial name. Omit and pass the fields below to price an asset that is not in the register |
| category | string | – | Table category code or name, when pricing an asset that is not in the register |
| cost_minor | integer | – | Cost in MINOR units, when pricing an asset that is not in the register |
| currency | string | – | ISO code, when pricing an asset that is not in the register |
| declining_coefficient | number | – | Declining-balance coefficient; ignored with straight-line |
| granularity | string | – | "year" for one row per period, "month" for the monthly charge. Default "year" |
| in_service_date | string | – | ISO date YYYY-MM-DD the asset entered use. Defaults to purchase_date |
| life_years | number | – | Override the useful life from the table, in years |
| method | string | – | "straight-line" or "declining-balance" |
| purchase_date | string | – | ISO date YYYY-MM-DD, when pricing an asset that is not in the register |
| rate_pct | number | – | Override the annual percentage from the table |
| residual_minor | integer | – | Residual in MINOR units, default 0 |
| scheme | string | – | Scheme, when pricing an asset that is not in the register |
No output schema declared.
No examples provided.
license_activate Activate license ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status 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.
What is the io.github.theluckystrike/asset-register MCP server?
io.github.theluckystrike/asset-register is an MCP server listed in the public MCP registry as io.github.theluckystrike/asset-register. Fixed assets and depreciation from bundled Polish KST, HMRC and IRS MACRS tables. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/asset-register).
Is the io.github.theluckystrike/asset-register MCP server safe to use?
io.github.theluckystrike/asset-register scores 82 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/asset-register MCP server expose?
io.github.theluckystrike/asset-register exposes 9 tools: asset_add, asset_list, asset_schedule, asset_journal, asset_dispose, and 4 more. Their descriptions and schemas cost roughly 1,634 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/asset-register MCP server require authentication?
Yes. io.github.theluckystrike/asset-register 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/asset-register MCP server still maintained?
io.github.theluckystrike/asset-register is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.