Remote MCP · Endpoint

parcelapi.net MCP server

No. parcelapi.net answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://api.parcelapi.net/mcp

The last check completed an MCP handshake.

Registry name
net.parcelapi/parcelapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
279 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
US parcels and building permits from public sources. No owner data. Pay per record or monthly plan.
Listing
From the official MCP registry (active).
Recent checks of parcelapi.net
CheckedResultHandshake
34 minutes agoHandshake completed279 ms
9 days agoHandshake completed204 ms
10 days agoHandshake completed212 ms
11 days agoHandshake completed187 ms
12 days agoHandshake completed242 ms
14 days agoHandshake completed269 ms
14 days agoHandshake completed191 ms
15 days agoHandshake completed189 ms
17 days agoHandshake completed796 ms
19 days agoHandshake completed276 ms
21 days agoHandshake completed183 ms
24 days agoHandshake completed299 ms
26 days agoHandshake completed284 ms
28 days agoHandshake completed209 ms

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

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.

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