Skip to content
lastscanned logo

lastscanned MCP server

Which MCP servers are lastscanned's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to lastscanned

Whose server it is
  • Registry namecom.lastscanned/lastscannedverified in the MCP registry

The registry name sits under lastscanned.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools3
  • Server calls itselflastscanned
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 578 ms.

Should an agent connect itConnect it, with care
  • Its tools do look up a parcel's status from its tracking number; check a late order's carrier scans to answer a customer, but not get webhook updates when a tracked parcel's status changes.

Once connected

  • For "look up a parcel's status from its tracking number", the likely first call is track_package.
  • For "check a late order's carrier scans to answer a customer", the likely first call is track_package.
  • Parameters are untyped or undescribed in 1 of 3 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-29
  • INITE MCP score89 of 100answers 100 · does the job 67 · definitions 94 · context 100 · connects 100
  • What an agent can do with it2 of 3 use cases
  • Answered100% of days7 of 7 daily checks
  • Median first answer285 ms
  • Space in an agent's context≈ 284 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsA · 94 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 3

What an agent can do with it

  • can do · look up a parcel's status from its tracking number
  • cannot · get webhook updates when a tracked parcel's status changes
  • can do · check a late order's carrier scans to answer a customer

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-29
  • track_package

    Current status, estimated delivery and full scan history of one tracking number.

  • track_packages

    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. Past the caller's daily limit (one number without a key), the remaining entries come back with error code…

  • list_carriers

    Carrier ids that can be passed as carrier.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "lastscanned": {
      "type": "http",
      "url": "https://mcp.lastscanned.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.lastscanned.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.