EasyPost MCP by usefulapi
REMOTE · EASYPOST.USEFULAPI.IO
MCP server for EasyPost — rate shipments, buy & refund labels, track packages, verify addresses.
Available components
Last scanned (4 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- Stability: 0.97 → pass security
- MCP protocol: fail → pass ▲ functional
- New prompt “buy_a_label_or_refund_one” functional
- New prompt “check_where_packages_are” functional
- New prompt “create_a_shipment_and_compare_its_rates” functional
- New prompt “create_and_verify_a_delivery_address” functional
- New prompt “review_recent_shipments_and_their_tracking_codes” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 +1
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 −1
- Stability: pass → 0.93 functional
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
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 6 Nov 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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of easypost.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://easypost.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/easypost/ |
| http (plaintext) | http://easypost.usefulapi.io/mcp | Inconclusive | 302 | http://easypost.usefulapi.io/mcp |
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 →
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? }).
| 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 }).
| 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 }).
| 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}.
| 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}.
| 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}.
| 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.
| 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.
| 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.
| 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.
| 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"] }).
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| company | string | – | – |
| country | string | – | 2-letter ISO country code, default US |
| 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.
How do I install the EasyPost MCP by usefulapi server?
EasyPost MCP by usefulapi is a hosted endpoint at https://easypost.usefulapi.io/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 · easypost.usefulapi.io
claude mcp add --transport http io-usefulapi-easypost 'https://easypost.usefulapi.io/mcp'
What is the EasyPost MCP by usefulapi server?
EasyPost MCP by usefulapi is listed in the public MCP registry as io.usefulapi/easypost. MCP server for EasyPost, rate shipments, buy & refund labels, track packages, verify addresses. This page covers its hosted endpoint (https://easypost.usefulapi.io/mcp).
Is the EasyPost MCP by usefulapi server safe to use?
EasyPost MCP by usefulapi scores 18 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 EasyPost MCP by usefulapi server expose?
EasyPost MCP by usefulapi exposes 11 tools: easypost_list_shipments, easypost_get_shipment, easypost_list_trackers, easypost_get_tracker, easypost_list_addresses, and 6 more. Their descriptions and schemas cost roughly 1,044 tokens of context every time the server is loaded.
Does the EasyPost MCP by usefulapi server require authentication?
Its publisher declares no required credentials for EasyPost MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the EasyPost MCP by usefulapi server still maintained?
EasyPost MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 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 EasyPost MCP by usefulapi server?
VerifyMCP ran 4 checks on EasyPost MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about EasyPost MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.