Remote MCP · Endpoint

ai.tigertiger/tigertiger MCP server

No. ai.tigertiger/tigertiger answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://mcp.tigertiger.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.tigertiger/tigertiger
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
969 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Chief of Staff, strategy and writing tools that give your Claude subscription structure and memory.
Listing
From the official MCP registry (active).
Recent checks of ai.tigertiger/tigertiger
CheckedResultHandshake
7 hours agoHandshake completed969 ms
4 days agoHandshake completed967 ms
14 days agoHandshake completed987 ms
15 days agoHandshake completed1.02 s
15 days agoHandshake completed1.02 s
17 days agoHandshake completed948 ms
18 days agoHandshake completed1.00 s
19 days agoHandshake completed999 ms
20 days agoHandshake completed1.04 s
21 days agoHandshake completed966 ms
23 days agoHandshake completed1.00 s
26 days agoHandshake completed656 ms
28 days agoHandshake completed660 ms

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

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