Remote MCP · Endpoint

com.substradium/carrier-records MCP server

No. com.substradium/carrier-records answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://substradium.com/mcp

The last check completed an MCP handshake.

Registry name
com.substradium/carrier-records
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
131 ms
Tools exposed
5 tools
Uptime, last 30 days
55.6% from 18 checks
Described by its publisher as
Dated motor-carrier records with receipts, verification, and specimens, from a records custodian.
Listing
From the official MCP registry (active).
Recent checks of com.substradium/carrier-records
CheckedResultHandshake
1 hour agoHandshake completed131 ms
1 day agoHandshake completed136 ms
2 days agoHandshake completed462 ms
3 days agoHandshake completed180 ms
4 days agoHandshake completed163 ms
5 days agoHandshake completed135 ms
6 days agoHandshake completed170 ms
9 days agoHandshake completed200 ms
12 days agoHandshake completed134 ms
14 days agoHandshake completed577 ms
16 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
22 days agoFailed - the server returned an HTTP error—
24 days agoFailed - the server returned an HTTP error—
26 days agoFailed - the server returned an HTTP error—
27 days agoFailed - the server returned an HTTP error—
29 days agoFailed - the server returned an HTTP error—

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 com.substradium/carrier-records and makes no claim about it beyond what these checks measured.