Skip to content

McpStamp Mileage Log MCP server

io.github.theluckystrike/mileage-logtheluckystrikestreamable-httpv0.23.0Scanned

Log drives by purpose, apply your own dated rates, get deductible totals and a CSV for taxes.

9 tools: 1 can delete or cancel things, 1 do something that can't be undone, 4 change things and 3 only read.

Tools: 1 delete, 1 irreversible, 4 write, 3 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the McpStamp Mileage Log MCP server can do

The McpStamp Mileage Log MCP server is published by the GitHub account theluckystrike. It has 9 tools. It can delete or cancel things (1 tool: trip_remove), do things that cannot be undone, such as sending, paying or publishing (trip_add) and create or change data (4 tools: rate_set, mileage_summary, mileage_export and license_activate). 3 tools only read.

1 tool reads private data (rate_list); 1 tool brings in text other people can write (license_status); 1 tool can send data out of your system (trip_add). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.23.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 1Claude Code: deny
  • trip_removeRemove one trip from the mileage log by its exact TR-YYYY-NNNN id, for entries made by mistake.No findings

    Why it is in this group

    • The name "trip_remove" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • trip_addLog 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).Can send data outNo findings

    Why it is in this group

    • The name "trip_add" says "add": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 4Claude Code: ask
  • license_activateTurn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • mileage_exportThe 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mileage_summaryThe 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 p…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • rate_setSet 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 ta…No findings

    Why it is in this group

    • The name "rate_set" says "set": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • license_statusReport 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.Reads text others writeNo findings

    Why it is in this group

    • The name "license_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • rate_listList 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 private dataNo findings

    Why it is in this group

    • The name "rate_list" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "file": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trip_listList 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).No findings

    Why it is in this group

    • The name "trip_list" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__mileage-log__trip_add"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:34 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/mileage-log
Authorization servers
https://mcp.zovo.one
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 destructive, 1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.zovo.one/mcp/mileage-log: tools/list returned 9 tools to an anonymous client, including trip_remove (destructive), trip_add (irreversible), rate_set (write), mileage_summary (write), mileage_export (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 429 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 6
    • Protocol version: none to 2025-06-18
  2. Nov 6, 2026
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/mileage-log
  3. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 429 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 6 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 429 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 6
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource -> https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/mileage-log.View diff
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/mileage-log
  3. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 6 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.23.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http mileage-log https://mcp.zovo.one/mcp/mileage-log
claude mcp add --transport http mileage-log https://mcp.zovo.one/mcp/mileage-log

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mileage-log__trip_list",
      "mcp__mileage-log__rate_list",
      "mcp__mileage-log__license_status"
    ],
    "ask": [
      "mcp__mileage-log__trip_add",
      "mcp__mileage-log__rate_set",
      "mcp__mileage-log__mileage_summary",
      "mcp__mileage-log__mileage_export",
      "mcp__mileage-log__license_activate"
    ],
    "deny": [
      "mcp__mileage-log__trip_remove"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mileage-log. Review it before you use it.

Capability tags behind 3 rules
  • mcp__mileage-log__trip_add outbound
  • mcp__mileage-log__rate_list private-data
  • mcp__mileage-log__license_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/mileage-log/verify?hash=8574eb46cb311a4bdccedaadbb70cc0164e3f7a8f9369fbadafc821cb14d7990" | jq -e '.changed == false'

Pinned hash 8574eb46cb31, from Nov 15, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.theluckystrike/mileage-log/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/mileage-log
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/mileage-log.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/mileage-log)

Source: MCP Registry · repository. Synced Nov 2, 2026, 03:18 UTC.

McpStamp Mileage Log MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the McpStamp Mileage Log MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the McpStamp Mileage Log MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: trip_remove.

Can the McpStamp Mileage Log MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: trip_add.

What tools does the McpStamp Mileage Log MCP server have?

9 tools: 1 destructive, 1 irreversible, 4 write, 3 read. trip_remove, trip_add, rate_set, mileage_summary, mileage_export, license_activate, trip_list, rate_list and 1 more.

Does the McpStamp Mileage Log MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the McpStamp Mileage Log MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): trip_add.

Has the McpStamp Mileage Log MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.