lastscanned — 542-Carrier Package Tracking, Webhooks & Watches
REMOTE · MCP.LASTSCANNED.COM
Track 542 carriers (USPS, UPS, FedEx, UniUni, LTL) via MCP, API, Webhooks & Watches.
Available components
Last scanned (11 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability38
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 2350 tokens (~783/item across 3 items; 3 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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
- 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 3 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “track_packages” rewrote its description, which is the text the model reads security
- Tool “list_carriers” now declares an output schema ▲ functional
- Tool “track_package” now declares an output schema ▲ functional
- Tool “track_packages” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 1.0.0 → 1.0.6 functional
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Tool “track_packages” rewrote its description, which is the text the model reads security
- 28 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 57
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 5 Nov 2026 · Probed https://mcp.lastscanned.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lastscanned.com | CN=WE1,O=Google Trust Services,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3e4f1a89b663555a0ef87a4afcb271ed |
| SANs: lastscanned.com, mcp.lastscanned.com, *.mcp.lastscanned.com | ||||||
| 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 mcp.lastscanned.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lastscanned.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.lastscanned.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.lastscanned.com/mcp | Inconclusive | 405 |
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 →
list_carriers List carriers ~18
Carrier ids that can be passed as carrier.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| carriers | array | yes | – |
No examples provided.
track_package Track a package ~68
Current status, estimated delivery and full scan history of one tracking number.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | string | – | Carrier id (see list_carriers). Omit to detect it from the number. |
| tracking_number | string | yes | Tracking number, e.g. 1Z999AA10123456784 |
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | string | yes | – |
| credits_remaining | integer | – | – |
| deliveredAt | string|null | – | – |
| deliveredAtLocal | string|null | – | – |
| destination | object|null | – | – |
| estimatedDelivery | string|null | – | – |
| estimatedDeliveryAt | string|null | – | – |
| events | array | yes | Scan history, newest first |
| message | string|null | – | – |
| notice | string | – | – |
| service | string|null | – | – |
| signedBy | string|null | – | – |
| status | string | yes | – |
| statusDescription | string | – | – |
| trackingNumber | string | yes | – |
No examples provided.
track_packages Track several packages ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | string | – | Carrier id (see list_carriers). Omit to detect it from the number. |
| tracking_numbers | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_remaining | integer | – | – |
| notice | string | – | – |
| results | array | yes | – |
No examples provided.
How do I install the lastscanned — 542-Carrier Package Tracking, Webhooks… MCP server?
lastscanned — 542-Carrier Package Tracking, Webhooks… is a hosted endpoint at https://mcp.lastscanned.com/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 · mcp.lastscanned.com
claude mcp add --transport http com-lastscanned-lastscanned 'https://mcp.lastscanned.com/mcp'
What is the lastscanned — 542-Carrier Package Tracking, Webhooks… MCP server?
lastscanned — 542-Carrier Package Tracking, Webhooks… is an MCP server listed in the public MCP registry as com.lastscanned/lastscanned. Track 542 carriers (USPS, UPS, FedEx, UniUni, LTL) via MCP, API, Webhooks & Watches. This page covers its hosted endpoint (https://mcp.lastscanned.com/mcp).
Is the lastscanned — 542-Carrier Package Tracking, Webhooks… MCP server safe to use?
lastscanned — 542-Carrier Package Tracking, Webhooks… scores 62 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 lastscanned — 542-Carrier Package Tracking, Webhooks… MCP server expose?
lastscanned — 542-Carrier Package Tracking, Webhooks… exposes 3 tools: track_package, track_packages, list_carriers. Their descriptions and schemas cost roughly 187 tokens of context every time the server is loaded.
Does the lastscanned — 542-Carrier Package Tracking, Webhooks… MCP server require authentication?
No. We connected to lastscanned — 542-Carrier Package Tracking, Webhooks… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the lastscanned — 542-Carrier Package Tracking, Webhooks… MCP server still maintained?
lastscanned — 542-Carrier Package Tracking, Webhooks… is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.