Skip to content

lastscanned: Parcel & Ocean Container Tracking MCP server

com.lastscanned/lastscannedlastscanned.comstreamable-httpv1.0.7Scanned

Track parcels + ocean containers across 549 total carriers via REST and four existing MCP tools.

4 tools: 2 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. 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 lastscanned: Parcel & Ocean Container Tracking MCP server can do

The lastscanned: Parcel & Ocean Container Tracking MCP server is published by lastscanned.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: track_package and track_packages), but cannot delete data. 2 tools only read.

3 tools bring in text other people can write (track_package, track_packages and get_rates).

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, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 22, 2026, version 1.0.7.

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.

4 tools

Changes things 2Claude Code: ask
  • track_packageCurrent status, estimated delivery and full scan history of one tracking number.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Current status, estimated delivery and full scan history of one tracking number. A carrier that needs the recipient's postcode answers postcode_required until zipcode is passed.

    Annotations the server declares

    • title: Track a package
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • track_packagesTrack up to 100 numbers at once (at most 35 per carrier).Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Track up to 100 numbers at once (at most 35 per carrier). Each entry has a result or an error; one bad number never fails the rest. Without sign-in only the first number is tracked; past a daily limit the remaining entries come back with error code auth_required or rate_limited. zipcode applies to every number whose carrier takes a postcode.

    Annotations the server declares

    • title: Track several packages
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • get_ratesShipping prices for one parcel between two postal codes from USPS, UPS and FedEx, cheapest first, with delivery days and surcharges.Reads text others writeNo findings

    Why it is in this group

    • The name "get_rates" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Shipping prices for one parcel between two postal codes from USPS, UPS and FedEx, cheapest first, with delivery days and surcharges. Each quote names its source and rateType (retail, list, or a postage reseller's price). Quotes only: nothing is bought and no label is made. Sources that can't quote come back in errors.

    Annotations the server declares

    • title: Compare shipping rates
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_carriersCarrier ids that can be passed as carrier; zipcode lists the ones that need the recipient's postcode.No findings

    Why it is in this group

    • The name "list_carriers" says "list": a word for reading.
    Description, as the server wrote it
    Carrier ids that can be passed as carrier; zipcode lists the ones that need the recipient's postcode.

    Annotations the server declares

    • title: List carriers
    • 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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 18, 2026, 16:23 UTC, unchanged since Nov 4, 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
2
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.lastscanned.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://app.lastscanned.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

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

    Matched text

    https://mcp.lastscanned.com/mcp: tools/list returned 4 tools to an anonymous client, including track_package (write), track_packages (write)

    What this check looks for

Posture changes

  1. Nov 4, 2026
    • RFC 9728 protected resource metadata: none to https://mcp.lastscanned.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://app.lastscanned.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

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. Tools3 changed.~3 changedView diff
  2. Tools1 added, 1 changed.+1 added~1 changedView diff
  3. Tools3 changed.~3 changedView diff
  4. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://mcp.lastscanned.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://app.lastscanned.com; Dynamic client registration: not observe…View diff
    • RFC 9728 protected resource metadata: none to https://mcp.lastscanned.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://app.lastscanned.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Install

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

claude mcp add --transport http lastscanned https://mcp.lastscanned.com/mcp
claude mcp add --transport http lastscanned https://mcp.lastscanned.com/mcp

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__lastscanned__get_rates",
      "mcp__lastscanned__list_carriers"
    ],
    "ask": [
      "mcp__lastscanned__track_package",
      "mcp__lastscanned__track_packages"
    ],
    "deny": []
  }
}

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 lastscanned. Review it before you use it.

Capability tags behind 3 rules
  • mcp__lastscanned__track_package untrusted-input
  • mcp__lastscanned__track_packages untrusted-input
  • mcp__lastscanned__get_rates 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/com.lastscanned/lastscanned/verify?hash=1d9a566082dc81e5d89af2f688cfe2202d0eda0c5d47257cff55ba8be10df145" | jq -e '.changed == false'

Pinned hash 1d9a566082dc, from Nov 22, 2026, 02:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.lastscanned/lastscanned/changes.xml

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

Badge

Anlyon Radar badge for com.lastscanned/lastscanned
[![Anlyon Radar](https://radar.anlyon.com/badge/com.lastscanned/lastscanned.svg)](https://radar.anlyon.com/servers/com.lastscanned/lastscanned)

Source: MCP Registry. Synced Nov 7, 2026, 20:17 UTC.

lastscanned: Parcel & Ocean Container Tracking MCP server: questions and answers

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

Is the lastscanned: Parcel & Ocean Container Tracking MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 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 lastscanned: Parcel & Ocean Container Tracking MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the lastscanned: Parcel & Ocean Container Tracking MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the lastscanned: Parcel & Ocean Container Tracking MCP server have?

4 tools: 2 write, 2 read. track_package, track_packages, get_rates and list_carriers.

Does the lastscanned: Parcel & Ocean Container Tracking MCP server need sign-in or OAuth?

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

Does the lastscanned: Parcel & Ocean Container Tracking MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the lastscanned: Parcel & Ocean Container Tracking MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 22, 2026. Every change is on this page and in its Atom feed.