Remote MCP · Endpoint

io.carrierscore/carrierscore MCP server

No. io.carrierscore/carrierscore answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.carrierscore.io/mcp

The last check completed an MCP handshake.

Registry name
io.carrierscore/carrierscore
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
217 ms
Tools exposed
8 tools
Uptime, last 30 days
88.9% from 18 checks
Described by its publisher as
FMCSA motor-carrier risk scores, monitoring, and carrier-selection evidence reports for AI agents.
Listing
From the official MCP registry (active).
Recent checks of io.carrierscore/carrierscore
CheckedResultHandshake
1 hour agoHandshake completed217 ms
1 day agoHandshake completed268 ms
2 days agoHandshake completed295 ms
3 days agoHandshake completed288 ms
4 days agoHandshake completed211 ms
5 days agoHandshake completed250 ms
6 days agoHandshake completed317 ms
9 days agoHandshake completed1.11 s
11 days agoHandshake completed367 ms
14 days agoHandshake completed339 ms
16 days agoHandshake completed274 ms
18 days agoHandshake completed193 ms
20 days agoHandshake completed1.07 s
22 days agoHandshake completed401 ms
24 days agoFailed - the server returned an HTTP error—
26 days agoFailed - the server returned an HTTP error—
27 days agoHandshake completed271 ms
28 days agoHandshake completed822 ms

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

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