# USPS Holiday Shipping Deadlines MCP (remote · usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev)

USPS holiday shipping deadlines: Christmas send-by dates, days left, military and international.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-usps-holiday-shipping-deadlines-mcp/usps-holiday-shipping-deadlines-mcp.md), [page](https://verifymcp.io/servers/theluckystrike-usps-holiday-shipping-deadlines-mcp/usps-holiday-shipping-deadlines-mcp)

## Channel facts

- Endpoint: `https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 435 tokens (~145/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the USPS Holiday Shipping Deadlines MCP server?

USPS Holiday Shipping Deadlines MCP is a hosted endpoint at https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/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.

### Claude

```bash
claude mcp add --transport http theluckystrike-usps-holiday-shipping-deadlines-m 'https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-usps-holiday-shipping-deadlines-m": {
      "url": "https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-usps-holiday-shipping-deadlines-m": {
      "type": "http",
      "url": "https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-usps-holiday-shipping-deadlines-m]
url = "https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-usps-holiday-shipping-deadlines-m": {
      "type": "remote",
      "url": "https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-usps-holiday-shipping-deadlines-m --url 'https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-usps-holiday-shipping-deadlines-m:
    url: "https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-usps-holiday-shipping-deadlines-m": {
      "Transport": "http",
      "Url": "https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-usps-holiday-shipping-deadlines-m -t streamable-http -u 'https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-usps-holiday-shipping-deadlines-m": {
      "type": "http",
      "url": "https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `get_usps_holiday_shipping_deadlines` (~105 tokens)

Get USPS holiday shipping deadlines

The USPS recommended send-by dates for delivery before December 25 for the current holiday season, read at call time from usps.com: Ground Advantage, First-Class Mail, Priority Mail and Priority Mail Express to the lower 48 and to Alaska, Hawaii, Puerto Rico and territories; First-Class Package International, Priority Mail International and Priority Mail Express International by world region; and APO/FPO/DPO military mail by ZIP group. Includes days left from today.

### `check_holiday_ship_by_date` (~165 tokens)

Check if a package still makes Christmas

For a ship date (default today, US Eastern) and a destination, lists each USPS service with its send-by date, days left and whether it is still on time for December 25, and names the slowest (usually cheapest) service still on time. Destination can be "lower48", a state or territory ("Alaska", "Hawaii", "Puerto Rico", "Guam"), a country ("Canada", "Germany", "Japan"), a USPS region ("Europe") or an APO/FPO/DPO ZIP ("APO 09021").

Input parameters:

- `destination` (string): Where the package goes. Default "lower48".
- `ship_date` (string): Date you will drop it off, YYYY-MM-DD. Default today in US Eastern time.

### `get_military_mail_deadline` (~88 tokens)

Get military mail holiday deadline

USPS holiday send-by dates for December 25 delivery to one APO/FPO/DPO ZIP code (090-099 AE, 340 AA, 962-966 AP): Ground Advantage, First-Class Mail, Priority Mail and Priority Mail Express Military Service.

Input parameters:

- `zip` (string, required): APO/FPO/DPO ZIP code, for example "09021" or "96601".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-usps-holiday-shipping-deadlines-mcp/usps-holiday-shipping-deadlines-mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 72
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 70
- 2026-11-11: 70
- 2026-11-10: 69
- 2026-11-09: 69
- 2026-11-08: 68
- 2026-11-07: 68
- 2026-11-06: 67
- 2026-11-05: 67

## Common questions

### What is the USPS Holiday Shipping Deadlines MCP server?

USPS Holiday Shipping Deadlines MCP is listed in the public MCP registry as io.github.theluckystrike/usps-holiday-shipping-deadlines-mcp. USPS holiday shipping deadlines: Christmas send-by dates, days left, military and international. This page covers its hosted endpoint (https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp).

### Is the USPS Holiday Shipping Deadlines MCP server safe to use?

USPS Holiday Shipping Deadlines MCP scores 74 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 USPS Holiday Shipping Deadlines MCP server expose?

USPS Holiday Shipping Deadlines MCP exposes 3 tools: get_usps_holiday_shipping_deadlines, check_holiday_ship_by_date, get_military_mail_deadline. Their descriptions and schemas cost roughly 358 tokens of context every time the server is loaded.

### Does the USPS Holiday Shipping Deadlines MCP server require authentication?

No. We connected to USPS Holiday Shipping Deadlines MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the USPS Holiday Shipping Deadlines MCP server still maintained?

USPS Holiday Shipping Deadlines MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the USPS Holiday Shipping Deadlines MCP server?

VerifyMCP ran 12 checks on USPS Holiday Shipping Deadlines MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about USPS Holiday Shipping Deadlines MCP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://usps-holiday-shipping-deadlines-mcp.lipmichal.workers.dev/mcp
- Repository: https://github.com/theluckystrike/usps-holiday-shipping-deadlines-mcp
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-usps-holiday-shipping-deadlines-mcp/usps-holiday-shipping-deadlines-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-usps-holiday-shipping-deadlines-mcp/usps-holiday-shipping-deadlines-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-usps-holiday-shipping-deadlines-mcp/usps-holiday-shipping-deadlines-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-usps-holiday-shipping-deadlines-mcp/usps-holiday-shipping-deadlines-mcp
