Remote MCP · Endpoint

Chain of Title MCP server

No. Chain of Title answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://chainoftitle.org/mcp

The last check completed an MCP handshake.

Registry name
org.chainoftitle/chain-of-title
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
7.41 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Solana launches recorded at creation: what each claimed, hashed. Observations, never verdicts.
Listing
From the official MCP registry (active).
Recent checks of Chain of Title
CheckedResultHandshake
2 hours agoHandshake completed7.41 s
2 days agoHandshake completed86 ms
4 days agoHandshake completed110 ms
6 days agoHandshake completed106 ms
9 days agoHandshake completed202 ms
11 days agoHandshake completed60 ms
13 days agoHandshake completed106 ms
14 days agoHandshake completed1.05 s
16 days agoHandshake completed57 ms
17 days agoHandshake completed79 ms
18 days agoHandshake completed119 ms
21 days agoHandshake completed35 ms
22 days agoHandshake completed400 ms
24 days agoHandshake completed46 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 Chain of Title and makes no claim about it beyond what these checks measured.