Remote MCP · Endpoint

Conduit Router — Governed MCP Routing MCP server

No. Conduit Router — Governed MCP Routing answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://router.pipavia.com/mcp

The last check completed an MCP handshake.

Registry name
org.aimlds/conduit-router
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
85 ms
Tools exposed
6 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Governed MCP routing: every agent call spend-capped, metered, sealed with a verifiable receipt.
Listing
From the official MCP registry (active).
Recent checks of Conduit Router — Governed MCP Routing
CheckedResultHandshake
1 hour agoHandshake completed85 ms
4 days agoHandshake completed213 ms
7 days agoHandshake completed67 ms

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

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 Conduit Router — Governed MCP Routing and makes no claim about it beyond what these checks measured.