Remote MCP · Endpoint

Ucc Liens MCP server

No. Ucc Liens answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/ucc-liens/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/ucc-liens
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.93 s
Tools exposed
46 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
UCC Liens — business-debtor UCC (Uniform Commercial Code) financing statements for Colorado…
Listing
From the official MCP registry (active).
Recent checks of Ucc Liens
CheckedResultHandshake
2 hours agoHandshake completed1.93 s
1 day agoHandshake completed282 ms
2 days agoHandshake completed1.06 s
2 days agoHandshake completed1.56 s
4 days agoHandshake completed1.11 s
7 days agoHandshake completed986 ms
9 days agoHandshake completed1.33 s
12 days agoHandshake completed1.35 s
14 days agoHandshake completed203 ms
16 days agoHandshake completed405 ms
18 days agoHandshake completed824 ms
20 days agoHandshake completed311 ms
22 days agoHandshake completed70 ms
24 days agoHandshake completed56 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 Ucc Liens and makes no claim about it beyond what these checks measured.