Remote MCP · Endpoint

ClausePilot MCP server

No. ClausePilot answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://clausepilot-pearl.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.sarvin-tech/clausepilot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
76 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
x402 contract tools and premium portfolio scans for AI agents on Base.
Listing
From the official MCP registry (active).
Recent checks of ClausePilot
CheckedResultHandshake
1 hour agoHandshake completed76 ms
2 days agoHandshake completed103 ms
4 days agoHandshake completed78 ms
6 days agoHandshake completed78 ms
8 days agoHandshake completed72 ms
10 days agoHandshake completed196 ms
12 days agoHandshake completed138 ms
14 days agoHandshake completed76 ms
15 days agoHandshake completed127 ms
16 days agoHandshake completed90 ms
17 days agoHandshake completed99 ms
20 days agoHandshake completed66 ms
22 days agoHandshake completed83 ms
23 days agoHandshake completed331 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 ClausePilot and makes no claim about it beyond what these checks measured.