Remote MCP · Endpoint

EasyPost MCP by usefulapi MCP server

No. EasyPost MCP by usefulapi answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://easypost.usefulapi.io/mcp

The last check completed an MCP handshake.

Registry name
io.usefulapi/easypost
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
327 ms
Tools exposed
11 tools
Uptime, last 30 days
50.0% from 18 checks
Described by its publisher as
MCP server for EasyPost — rate shipments, buy & refund labels, track packages, verify addresses.
Website
https://usefulapi.io/easypost/
Repository
https://github.com/m190/usefulapi-mcp
Listing
From the official MCP registry (active).
Recent checks of EasyPost MCP by usefulapi
CheckedResultHandshake
2 hours agoHandshake completed327 ms
2 days agoHandshake completed202 ms
4 days agoHandshake completed256 ms
6 days agoHandshake completed258 ms
7 days agoHandshake completed181 ms
9 days agoFailed - the check failed for an unclassified reason—
10 days agoHandshake completed226 ms
11 days agoHandshake completed409 ms
14 days agoHandshake completed208 ms
15 days agoFailed - the check failed for an unclassified reason—
17 days agoHandshake completed281 ms
18 days agoFailed - the check failed for an unclassified reason—
19 days agoFailed - the check failed for an unclassified reason—
20 days agoFailed - the check failed for an unclassified reason—
21 days agoFailed - the check failed for an unclassified reason—
22 days agoFailed - the check failed for an unclassified reason—
23 days agoFailed - the check failed for an unclassified reason—
24 days agoFailed - the check failed for an unclassified reason—

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 9 responding of 18.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with EasyPost MCP by usefulapi and makes no claim about it beyond what these checks measured.