Odometry Mileage Log
REMOTE · MILEAGE-LOG.ZOVO.ONE
Mileage log and reimbursement
Available components
Last scanned (5 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Finance and Payments
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- 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 1286 tokens (~428/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 Management3
- Stability observed for 1 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
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.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 73
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 23 Oct 2026 · Probed https://mileage-log.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 | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6ab8e422862cc65a0e5264f1bf99d2b2 |
| SANs: zovo.one, mileage-log.zovo.one, *.mileage-log.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 mileage-log.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 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://mileage-log.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://mileage-log.zovo.one/mcp | HTTPS enforced | 301 | https://mileage-log.zovo.one/mcp |
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 →
calculate_mileage_reimbursement Calculate mileage reimbursement ~472
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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"}]. |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | yes | – |
| amount | number | yes | – |
| amount_text | string | yes | – |
| category | string | yes | – |
| custom | – | yes | – |
| irs_amount | number | yes | – |
| kind | string | yes | – |
| lines | array | yes | – |
| miles | number | yes | – |
| notes | array | yes | – |
| odometer | – | yes | – |
| rate_basis | string | yes | – |
No examples provided.
generate_mileage_log Generate mileage log ~696
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| by_client | array | yes | – |
| by_month | array | yes | – |
| by_purpose | array | yes | – |
| downloads | object | yes | – |
| flags | object | yes | – |
| kind | string | yes | – |
| notes | array | yes | – |
| period | string | yes | – |
| preview | array | yes | – |
| rate_basis | string | yes | – |
| rates_used | array | yes | – |
| source | object | yes | – |
| title | string | yes | – |
| totals | object | yes | – |
| vehicle_use | – | yes | – |
No examples provided.
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.
remote · mileage-log.zovo.one
claude mcp add --transport http theluckystrike-odometry-mileage-log 'https://mileage-log.zovo.one/mcp'
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.