Remote MCP · Endpoint

ai.ruthven/ruthven MCP server

No. ai.ruthven/ruthven answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ruthven.ai/api/ruthven/mcp

The last check completed an MCP handshake.

Registry name
ai.ruthven/ruthven
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.43 s
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Artwork provenance and works for sale: Origin Passports, Ethereum proofs, listings with proof
Listing
From the official MCP registry (active).
Recent checks of ai.ruthven/ruthven
CheckedResultHandshake
1 hour agoHandshake completed1.43 s
2 days agoHandshake completed268 ms
4 days agoHandshake completed471 ms
7 days agoHandshake completed275 ms
9 days agoHandshake completed1.36 s
11 days agoHandshake completed1.08 s
13 days agoHandshake completed1.36 s
15 days agoHandshake completed453 ms
17 days agoHandshake completed278 ms
19 days agoHandshake completed1.47 s
20 days agoHandshake completed314 ms
22 days agoHandshake completed376 ms
23 days agoHandshake completed2.76 s

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