Remote MCP · Endpoint

Tickerz MCP server

No. Tickerz answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tickerz.com/mcp

The last check completed an MCP handshake.

Registry name
com.tickerz/tickerz
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
161 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Daily indexes of what people do, from public data. On-chain in Bitcoin, so nobody can edit them.
Website
https://tickerz.com/connect
Listing
From the official MCP registry (active).
Recent checks of Tickerz
CheckedResultHandshake
1 hour agoHandshake completed161 ms
2 days agoHandshake completed164 ms
5 days agoHandshake completed224 ms
7 days agoHandshake completed179 ms
9 days agoHandshake completed270 ms
11 days agoHandshake completed172 ms
13 days agoHandshake completed231 ms
15 days agoHandshake completed146 ms
17 days agoHandshake completed246 ms
19 days agoHandshake completed382 ms
20 days agoHandshake completed148 ms
21 days agoHandshake completed134 ms
23 days agoHandshake completed515 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Tickerz and makes no claim about it beyond what these checks measured.