Remote MCP · Endpoint

Carrier Ledger MCP server

No. Carrier Ledger answered an MCP handshake 58 minutes ago.

UpLast checked 58 minutes ago

Server URL

https://carrier-ledger.neoaethel.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.neoaethel.carrier-ledger/carrier-ledger
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
171 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check U.S. trucking carriers and freight brokers in FMCSA records: authority, insurance, notices.
Listing
From the official MCP registry (active).
Recent checks of Carrier Ledger
CheckedResultHandshake
58 minutes agoHandshake completed171 ms
13 hours agoHandshake completed106 ms
1 day agoHandshake completed158 ms
2 days agoHandshake completed298 ms
4 days agoHandshake completed363 ms
7 days agoHandshake completed84 ms
9 days agoHandshake completed145 ms
12 days agoHandshake completed130 ms
14 days agoHandshake completed93 ms
16 days agoHandshake completed93 ms
18 days agoHandshake completed73 ms
20 days agoHandshake completed227 ms
22 days agoHandshake completed78 ms
23 days agoHandshake completed67 ms

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

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 Carrier Ledger and makes no claim about it beyond what these checks measured.