# io.github.theluckystrike/mileage-log (remote · mcp.zovo.one)

Mileage log for deductible driving: trips, effective-dated rates, summaries and CSV export.

- Trust score: 81/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.zovo.one`: 81/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-mileage-log/mcp-mileage-log.md), [page](https://verifymcp.io/servers/theluckystrike-mileage-log/mcp-mileage-log)
- mcpb · `mileage-log.mcpb`: 46/100, [markdown](https://verifymcp.io/servers/theluckystrike-mileage-log/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-mileage-lo.md), [page](https://verifymcp.io/servers/theluckystrike-mileage-log/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-mileage-lo)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/mileage-log`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.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-09-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1262 tokens (~126/item across 10 items; 9 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 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.

## Install

### How do I install the io.github.theluckystrike/mileage-log MCP server?

io.github.theluckystrike/mileage-log is a hosted endpoint at https://mcp.zovo.one/mcp/mileage-log, 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-mileage-log 'https://mcp.zovo.one/mcp/mileage-log'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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-09-21 (score 81, +2)

- [security] Tool “trip_remove” is now declared destructive
- [functional] Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.

### 2026-09-20 (score 79, +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-09-18 (score 78, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 78)

First indexed and scored.

## MCP tools (9)

### `trip_add` (~295 tokens)

Log a trip

Log one drive in the mileage log: the date, where from and to, the distance in miles or km, the purpose, and the category (business, medical, moving, charitable, personal). Returns its TR-YYYY-NNNN id. Free tier: 20 trips per calendar month, counted on the month of the trip date.

Input parameters:

- `category` (string, required): One of: business, medical, moving, charitable, personal. Personal trips are kept for the record and priced only if a rate exists
- `date` (string, required): The day the trip was driven, YYYY-MM-DD. A future date is refused: the trip cannot have been driven yet
- `distance` (number, required): How far, to the thousandth of the unit, e.g. 12.5
- `from` (string, required): Where the trip started, e.g. Home office, 14 Nowa Street
- `jurisdiction` (string): Which rate set prices this trip, when more than one jurisdiction has a rate for its category. Omit when only one does
- `note` (string)
- `purpose` (string, required): Why the trip was made, e.g. Site visit for the Kowalski refit
- `to` (string, required): Where it ended, e.g. Client site, 2 Mill Lane
- `unit` (string, required): miles or km; spellings like mi and kilometre are accepted

### `trip_list` (~121 tokens)

List trips

List trips in the mileage log, oldest first: date, from, to, distance, category, and the amount each earns under the rate in force on its day (or the plain reason it is unpriced). Filter by date range and category. Reads only.

Input parameters:

- `category` (string): Only trips of this category: business, medical, moving, charitable, personal
- `from_date` (string): Only trips dated on or after this, YYYY-MM-DD
- `to_date` (string): Only trips dated on or before this, YYYY-MM-DD

### `trip_remove` (~76 tokens)

Remove a trip

Remove one trip from the mileage log by its exact TR-YYYY-NNNN id, for entries made by mistake. The id is not reissued: a gap in the TR series is the record that a trip was removed.

Input parameters:

- `id` (string, required): The exact trip id, e.g. TR-2026-0003

### `rate_set` (~250 tokens)

Set a mileage rate

Set what one mile or km is worth for one category in one jurisdiction from a date forward: the jurisdiction label, the category, the rate per unit, the currency, and the date it takes effect. Rates form a series per jurisdiction and category, and each trip earns the rate in force on the day it was driven. No rate ships with this server; the figures are yours to verify. Free tier: one rate per jurisdiction and category; the year-over-year series is Pro.

Input parameters:

- `category` (string, required): Which category this prices: business, medical, moving, charitable, personal
- `currency` (string, required): ISO code the rate is in
- `effective_from` (string, required): The date the rate starts to apply, YYYY-MM-DD. May be in the future: authorities announce next year's rate ahead of time
- `jurisdiction` (string, required): A label for the rate set, e.g. US federal or Canada federal. It is a label, not legal advice
- `rate` (number, required): The rate per unit in currency units, to the thousandth, e.g. 0.70 for 70 cents a mile
- `unit` (string, required): The distance unit the rate prices

### `rate_list` (~39 tokens)

List the rates on file

List every mileage rate on file, grouped by jurisdiction and category with the effective-from dates in order: the series each trip is priced from. Reads only.

### `mileage_summary` (~146 tokens)

Summarize a date range

The deductible mileage for a date range, per category: trips, distance kept per unit, the rate each trip earned (the one in force on its day), and the deductible amount, totalled per currency. Trips with no applicable rate are listed with the reason, not silently dropped. Defaults to the current calendar year. Never metered.

Input parameters:

- `category` (string): Only this category: business, medical, moving, charitable, personal
- `from_date` (string): Start of the range, YYYY-MM-DD. Default January 1 of the current year
- `to_date` (string): End of the range, YYYY-MM-DD. Default December 31 of the current year

### `mileage_export` (~153 tokens)

Export the log as CSV for an accountant

The mileage log as CSV, one row per trip, oldest first: date, from, to, distance, unit, category, the rate applied (the one in force on the trip's day), the currency and the amount, plus purpose, jurisdiction, effective_from and id. The amount column is a bare number a spreadsheet reads. Refuses while any non-personal trip in the window is unpriced, so an accountant never receives a log with silent gaps. Pro.

Input parameters:

- `from_date` (string): Start of the range, YYYY-MM-DD. Default January 1 of the current year
- `to_date` (string): End of the range, YYYY-MM-DD. Default December 31 of the current year

### `license_status` (~55 tokens)

License status

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.

### `license_activate` (~76 tokens)

Activate license

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.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

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

## Score history

- 2026-09-21: 81
- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 78

## Common questions

### What is the io.github.theluckystrike/mileage-log MCP server?

io.github.theluckystrike/mileage-log is an MCP server listed in the public MCP registry as io.github.theluckystrike/mileage-log. Mileage log for deductible driving: trips, effective-dated rates, summaries and CSV export. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/mileage-log).

### Is the io.github.theluckystrike/mileage-log MCP server safe to use?

io.github.theluckystrike/mileage-log scores 81 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/mileage-log MCP server expose?

io.github.theluckystrike/mileage-log exposes 9 tools: trip_add, trip_list, trip_remove, rate_set, rate_list, and 4 more. Their descriptions and schemas cost roughly 1,211 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/mileage-log MCP server require authentication?

Yes. io.github.theluckystrike/mileage-log 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/mileage-log MCP server still maintained?

io.github.theluckystrike/mileage-log is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/mileage-log
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/mileage-log
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/mileage-log
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-mileage-log/mcp-mileage-log.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-mileage-log/mcp-mileage-log.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-mileage-log/mcp-mileage-log