io.usefulapi/easypost

REMOTE · EASYPOST.USEFULAPI.IO · SCANNED AUG 3

MCP server for EasyPost — rate shipments, buy & refund labels, track packages, verify addresses.

Available components

+4 this week 72 72 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security78

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability75

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 1044 tokens (~94/item across 11 items; 11 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage94

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
83% of tool parameters carry a description.Partial

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · easypost.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-usefulapi-easypost https://easypost.usefulapi.io/mcp

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-easypost]
url = "https://easypost.usefulapi.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-easypost": {
      "type": "remote",
      "url": "https://easypost.usefulapi.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add io-usefulapi-easypost --url https://easypost.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-easypost:
    url: "https://easypost.usefulapi.io/mcp"

// mcp.json

{
  "mcpServers": {
    "io-usefulapi-easypost": {
      "type": "http",
      "url": "https://easypost.usefulapi.io/mcp"
    }
  }
}

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

Changelog

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.

2 Aug 26 +54
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
1 Aug 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +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.
28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +56
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 12

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Probed https://easypost.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=usefulapi.io	CN=WE1,O=Google Trust Services,C=US	17 Jul 2026	15 Oct 2026	ECDSA 256	ECDSA-SHA256	f69c04d4a33f656e1364afdcfab8467b
SANs: usefulapi.io, easypost.usefulapi.io, *.easypost.usefulapi.io
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

DNSSEC insecure

Validation of easypost.usefulapi.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
usefulapi.io.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://easypost.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Bearer realm="OAuth", resource_metadata="https://easypost.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document	https://easypost.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved	Yes
Resource	https://easypost.usefulapi.io/mcp
Authorisation server	https://easypost.usefulapi.io

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://easypost.usefulapi.io/mcp	Verified	200
http (plaintext)	http://easypost.usefulapi.io/mcp	Inconclusive	401

MCP tools — 11 exposed · ~1,044 tokens

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.

Tool Tokens

easypost_buy_shipment Buy a shipping label ~160

PURCHASE a shipping label for a shipment at a chosen rate. WARNING: this CHARGES the EasyPost account balance and is irreversible except by requesting a refund (easypost_refund_shipment). Pick a rate_id from the rates returned by easypost_create_shipment or easypost_get_shipment. API: POST /shipments/{id}/buy (body { rate: { id }, insurance? }).

Input Output Examples

Name	Type	Req	Description
insurance	string	—	Dollar amount to insure the shipment for, e.g. "249.99".
rate_id	string	yes	Rate id to purchase (from create_shipment / get_shipment rates).
shipment_id	string	yes	Shipment id to buy, e.g. shp_...

No output schema declared.

No examples provided.

easypost_create_shipment Create a shipment (get rates) ~145

Create a shipment from a to_address, from_address, and parcel, returning the available RATES from all enabled carriers. This only RATES the shipment — it does NOT purchase a label and does NOT charge the account; buying is a separate step (easypost_buy_shipment). API: POST /shipments (body { shipment }).

Input Output Examples

Name	Type	Req	Description
carrier_accounts	array	—	Restrict rating to these carrier_account ids.
from_address	object	yes	Origin/return address.
parcel	object	yes	Package dimensions and weight.
reference	string	—	Your internal reference string for the shipment.
to_address	object	yes	Destination address.

No output schema declared.

No examples provided.

easypost_create_tracker Create a tracker ~81

Start tracking a package by its carrier tracking code. Returns the tracker with current status. No charge. API: POST /trackers (body { tracker }).

Input Output Examples

Name	Type	Req	Description
carrier	string	—	Carrier name, e.g. USPS, UPS, FedEx (helps disambiguate).
tracking_code	string	yes	The carrier tracking code to track.

No output schema declared.

No examples provided.

easypost_get_address Get an address ~45

Retrieve a single address by id, including verification details. API: GET /addresses/{id}.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Address id, e.g. adr_...

No output schema declared.

No examples provided.

easypost_get_shipment Get a shipment ~58

Retrieve a single shipment by id, including its available rates, tracking_code, and postage_label (if purchased). API: GET /shipments/{id}.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Shipment id, e.g. shp_...

No output schema declared.

No examples provided.

easypost_get_tracker Get a tracker ~51

Retrieve a single tracker by id, including current status and tracking_details history. API: GET /trackers/{id}.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Tracker id, e.g. trk_...

No output schema declared.

No examples provided.

easypost_list_addresses List addresses ~72

List saved addresses on the account, with pagination. API: GET /addresses.

Input Output Examples

Name	Type	Req	Description
after_id	string	—	Return records created after this address id.
before_id	string	—	Return records created before this address id.
page_size	integer	—	Results per page (max 100).

No output schema declared.

No examples provided.

easypost_list_shipments List shipments ~136

List shipments on the account, most recent first, with pagination and optional filters. API: GET /shipments.

Input Output Examples

Name	Type	Req	Description
after_id	string	—	Return records created after this shipment id.
before_id	string	—	Return records created before this shipment id.
end_datetime	string	—	ISO 8601 upper bound on created_at.
page_size	integer	—	Results per page (max 100).
purchased	boolean	—	Filter to only purchased (true) or unpurchased (false) shipments.
start_datetime	string	—	ISO 8601 lower bound on created_at.

No output schema declared.

No examples provided.

easypost_list_trackers List trackers ~80

List package trackers, optionally filtered by tracking_code or carrier. API: GET /trackers.

Input Output Examples

Name	Type	Req	Description
carrier	string	—	Filter by carrier name, e.g. USPS, UPS, FedEx.
page_size	integer	—	Results per page (max 100).
tracking_code	string	—	Filter by carrier tracking code.

No output schema declared.

No examples provided.

easypost_refund_shipment Refund / void a label ~69

Request a refund (void) of a purchased shipping label. WARNING: reverses a purchase; approval depends on the carrier and label age. API: POST /shipments/{id}/refund.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Shipment id to refund, e.g. shp_...

No output schema declared.

No examples provided.

easypost_verify_address Verify an address ~147

Create and verify a US or international address, returning deliverability and normalized/corrected fields. No charge. API: POST /addresses (body { address, verify: ["delivery"] }).

Input Output Examples

Name	Type	Req	Description
city	string	—	—
company	string	—	—
country	string	—	2-letter ISO country code, default US
email	string	—	—
name	string	—	—
phone	string	—	—
state	string	—	2-letter state/province code
street1	string	yes	Street address line 1
street2	string	—	—
zip	string	yes	Postal/ZIP code

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	68
28 Jul	68
29 Jul	69
30 Jul	67
31 Jul	71
1 Aug	18
2 Aug	72
3 Aug	72