McpStamp Mileage Log
MCPB · MILEAGE-LOG.MCPB · 2 COMPONENTS
Log drives by purpose, apply your own dated rates, get deductible totals and a CSV for taxes.
Available components
Last scanned (6 hours ago)
Scores higher than 94% of MCPB servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 49 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1205 tokens (~133/item across 9 items; 9 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% 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; "trip_remove" implies "remove" 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 9 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
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityNo malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 +1
- Maintenance: unverified → pass ▲ functional
- 2 Nov 26 +54
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → 0.85 ▲ functional
- Licence: MIT functional
- Package version: 0.22.5 → 0.22.0 functional
- 1 Nov 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 26 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 25 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 22 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 18 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 17 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
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 5 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/mileage-log.mcpb@0.22.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
license_activate Activate license ~71
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mileage_export Export the log as CSV for an accountant ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
mileage_summary Summarize a date range ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
rate_list List the rates on file ~39
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rate_set Set a mileage rate ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Which category this prices: business, medical, moving, charitable, personal |
| currency | string | yes | ISO code the rate is in |
| effective_from | string | yes | 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 | yes | A label for the rate set, e.g. US federal or Canada federal. It is a label, not legal advice |
| rate | number | yes | The rate per unit in currency units, to the thousandth, e.g. 0.70 for 70 cents a mile |
| unit | string | yes | The distance unit the rate prices |
No output schema declared.
No examples provided.
trip_add Log a trip ~295
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | One of: business, medical, moving, charitable, personal. Personal trips are kept for the record and priced only if a rate exists |
| date | string | yes | The day the trip was driven, YYYY-MM-DD. A future date is refused: the trip cannot have been driven yet |
| distance | number | yes | How far, to the thousandth of the unit, e.g. 12.5 |
| from | string | yes | 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 | yes | Why the trip was made, e.g. Site visit for the Kowalski refit |
| to | string | yes | Where it ended, e.g. Client site, 2 Mill Lane |
| unit | string | yes | miles or km; spellings like mi and kilometre are accepted |
No output schema declared.
No examples provided.
trip_list List trips ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
trip_remove Remove a trip ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The exact trip id, e.g. TR-2026-0003 |
No output schema declared.
No examples provided.
How do I install the McpStamp Mileage Log MCP server?
McpStamp Mileage Log ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, e0dbcf7865aaba4fd175f1a28dd1dd2a9b82d7510cc6bbee980cca31df631355; the commands to do that are on this page. If it does not match, do not open it.
mcpb · mileage-log.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
e0dbcf7865aaba4fd175f1a28dd1dd2a9b82d7510cc6bbee980cca31df631355
macOS / Linux
echo "e0dbcf7865aaba4fd175f1a28dd1dd2a9b82d7510cc6bbee980cca31df631355 mileage-log.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\mileage-log.mcpb).Hash -eq "e0dbcf7865aaba4fd175f1a28dd1dd2a9b82d7510cc6bbee980cca31df631355"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the McpStamp Mileage Log MCP server?
McpStamp Mileage Log is an MCP server listed in the public MCP registry as io.github.theluckystrike/mileage-log. Log drives by purpose, apply your own dated rates, get deductible totals and a CSV for taxes. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/mileage-log.mcpb).
Is the McpStamp Mileage Log MCP server safe to use?
McpStamp Mileage Log scores 60 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 McpStamp Mileage Log MCP server expose?
McpStamp 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,205 tokens of context every time the server is loaded.
What licence is the McpStamp Mileage Log MCP server under?
McpStamp Mileage Log declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the McpStamp Mileage Log MCP server?
VerifyMCP ran 15 checks on McpStamp Mileage Log, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about McpStamp Mileage Log: Malware scan. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.