# Odometry Mileage Log (remote · mileage-log.zovo.one)

Mileage log and reimbursement

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

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

## Channel facts

- Endpoint: `https://mileage-log.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-10-23.

- **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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 70/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 1286 tokens (~428/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**: 3/100
  - Stability observed for 1 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 Odometry Mileage Log MCP server?

Odometry Mileage Log is a hosted endpoint at https://mileage-log.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-odometry-mileage-log 'https://mileage-log.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-odometry-mileage-log": {
      "type": "http",
      "url": "https://mileage-log.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-10-23 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 73)

First indexed and scored.

## MCP tools (2)

### `generate_mileage_log` (~696 tokens)

Generate mileage log

Use this when the user wants a mileage log, mileage log template, mileage log for taxes, printable mileage log, mileage log in Excel, or mileage reimbursement report from trips they drove ("turn these trips into a mileage log for my taxes", "reconstruct my mileage log from my calendar"). Takes typed trips (date, from, to, purpose, miles or odometer start/end), recurring trips (for example weekdays in a month) and/or an attached CSV/XLSX file. Applies the IRS standard mileage rate for each trip's date (2025: 70 cents; Jan-Jun 2026: 72.5 cents; Jul-Dec 2026: 76 cents per business mile; medical, moving and charity rates) or a custom employer rate, checks odometer continuity, flags commuting and missing purposes, and totals by month, purpose and client. Returns a PDF mileage log and an XLSX file. Does not look up distances between addresses, track GPS, or give tax advice. Do not use for a single quick mileage total with no trip list (use calculate_mileage_reimbursement).

Input parameters:

- `custom_rate_per_mile` (number): Employer or contract reimbursement rate in US dollars per mile for business trips, e.g. 0.60. Leave out to use the IRS standard mileage rate for each trip date.
- `driver_name` (string): Optional driver name printed on the log, e.g. "Dana Lee".
- `file` (object): Optional trip spreadsheet the user attached (CSV, TSV or XLSX) with columns such as Date, From, To, Purpose, Miles, or Odometer start and Odometer end, e.g. trips.xlsx.
- `home_office_is_principal_place` (boolean): true if the user's home office is their principal place of business (then trips from home are not flagged as commuting).
- `log_title` (string): Title printed on the log, e.g. "October 2026 mileage".
- `recurring` (array): Repeating trips, e.g. "every weekday in October, 18 mi to the clinic" -> [{"start_date":"2026-10-01","end_date":"2026-10-31","to":"Clinic","purpose":"Patient visits","miles":18}].
- `regular_workplace` (string): Name of the user's regular office or workplace, e.g. "Main St office", to flag home-to-office commuting.
- `skip_dates` (array): Dates to leave out of recurring trips (holidays, PTO), YYYY-MM-DD, e.g. ["2026-10-12"].
- `trips` (array): Typed trips, one per drive, e.g. [{"date":"2026-10-05","from":"Office","to":"Client A","purpose":"Sales meeting","miles":12.4}].
- `vehicle` (string): Optional vehicle description printed on the log, e.g. "2021 Toyota Camry". No VIN or plate needed.
- `year_end_odometer` (number): Odometer at the end of the year (or of the log period), e.g. 52120.
- `year_start_odometer` (number): Odometer at the start of the year (or of the log period), e.g. 38500. With year_end_odometer it gives total miles and business-use percentage.

Output parameters:

- `by_client` (array)
- `by_month` (array)
- `by_purpose` (array)
- `downloads` (object)
- `flags` (object)
- `kind` (string)
- `notes` (array)
- `period` (string)
- `preview` (array)
- `rate_basis` (string)
- `rates_used` (array)
- `source` (object)
- `title` (string)
- `totals` (object)
- `vehicle_use`

### `calculate_mileage_reimbursement` (~472 tokens)

Calculate mileage reimbursement

Use this when the user asks for a mileage reimbursement calculator, mileage deduction, or the IRS mileage rate 2026 applied to a number of miles ("how much can I deduct for 4,200 business miles", "my employer pays 0.70 a mile how much do I get", "odometer 41230 to 46890 how many business miles"). Applies the IRS standard mileage rate for the date driven (2025: 70 cents; Jan-Jun 2026: 72.5 cents; Jul-Dec 2026: 76 cents per business mile; medical/moving 21, 20.5, 23.5 cents; charity 14 cents), splits miles across the July 1, 2026 rate change, compares a custom employer rate with the IRS rate, and turns odometer readings into miles. Does not build a trip-by-trip log (use generate_mileage_log), look up distances, or give tax advice.

Input parameters:

- `category` (string): business (default), medical, moving (Armed Forces only) or charity.
- `custom_rate_per_mile` (number): Employer or contract rate in US dollars per mile, e.g. 0.70 or 0.60. The IRS amount is shown next to it.
- `date` (string): When the miles were driven, YYYY-MM-DD or YYYY-MM, e.g. "2026-08-15" or "2026-03". Picks the IRS rate for that date. Default: today.
- `miles` (number): Miles to reimburse or deduct, e.g. 4200. Leave out when odometer_start and odometer_end are given.
- `odometer_end` (number): Odometer reading at the end, e.g. 46890.
- `odometer_start` (number): Odometer reading at the start, e.g. 41230.
- `personal_miles` (number): Personal or commuting miles inside the odometer range to subtract, e.g. 900.
- `segments` (array): Miles split by date when they straddle a rate change, e.g. [{"miles":1800,"date":"2026-05"},{"miles":2400,"date":"2026-09"}].

Output parameters:

- `alternatives` (array)
- `amount` (number)
- `amount_text` (string)
- `category` (string)
- `custom`
- `irs_amount` (number)
- `kind` (string)
- `lines` (array)
- `miles` (number)
- `notes` (array)
- `odometer`
- `rate_basis` (string)

## Diagnostics

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

## Score history

- 2026-10-23: 73
- 2026-10-22: 73

## Common questions

### What is the Odometry Mileage Log MCP server?

Odometry Mileage Log is an MCP server listed in the public MCP registry as io.github.theluckystrike/odometry-mileage-log. Mileage log and reimbursement. This page covers its hosted endpoint (https://mileage-log.zovo.one/mcp).

### Is the Odometry Mileage Log MCP server safe to use?

Odometry Mileage Log scores 73 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 Odometry Mileage Log MCP server expose?

Odometry Mileage Log exposes 2 tools: generate_mileage_log, calculate_mileage_reimbursement. Their descriptions and schemas cost roughly 1,168 tokens of context every time the server is loaded.

### Does the Odometry Mileage Log MCP server require authentication?

No. We connected to Odometry Mileage Log without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Odometry Mileage Log MCP server still maintained?

Odometry Mileage Log is still listed as active in the MCP registry. We last reached this channel on 23 October 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://mileage-log.zovo.one/mcp
- Website: https://mileage-log.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-odometry-mileage-log/mileage-log.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-odometry-mileage-log/mileage-log.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-odometry-mileage-log/mileage-log