Remote MCP · Endpoint

Claim by Ouroboros Apps MCP server

No. Claim by Ouroboros Apps answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://claim-continuity2.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.LAHutchins91/claim
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
122 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Approved brand claims, offers, proof, and banned phrases for AI-written marketing copy
Listing
From the official MCP registry (active).
Recent checks of Claim by Ouroboros Apps
CheckedResultHandshake
1 hour agoHandshake completed122 ms
2 days agoHandshake completed56 ms
5 days agoHandshake completed71 ms
7 days agoHandshake completed68 ms
9 days agoHandshake completed62 ms
11 days agoHandshake completed94 ms
13 days agoHandshake completed78 ms
15 days agoHandshake completed92 ms
17 days agoHandshake completed50 ms
19 days agoHandshake completed108 ms
20 days agoHandshake completed72 ms
21 days agoHandshake completed58 ms
23 days agoHandshake completed67 ms

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

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