Remote MCP · Endpoint

ClauseAI MCP server

No. ClauseAI answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://clauseai.exe.xyz/mcp

The last check completed an MCP handshake.

Registry name
io.github.wasauce/clauseai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
145 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Generate attorney-drafted NDAs, MSAs, DPAs, and more as PDF, ODT, or Markdown. No account required.
Listing
From the official MCP registry (active).
Recent checks of ClauseAI
CheckedResultHandshake
3 hours agoHandshake completed145 ms
9 days agoHandshake completed214 ms
10 days agoHandshake completed142 ms
11 days agoHandshake completed129 ms
12 days agoHandshake completed140 ms
14 days agoHandshake completed213 ms
14 days agoHandshake completed211 ms
15 days agoHandshake completed210 ms
17 days agoHandshake completed213 ms
19 days agoHandshake completed209 ms
21 days agoHandshake completed208 ms
24 days agoHandshake completed205 ms
26 days agoHandshake completed254 ms
28 days agoHandshake completed262 ms

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

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