Remote MCP · Endpoint

TGGET Niche Research MCP server

No. TGGET Niche Research answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://tgget.io/mcp

The last check completed an MCP handshake.

Registry name
io.tgget/niche-research
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
116 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Validate app and SaaS ideas: search demand, competitors, app store data and a verdict.
Listing
From the official MCP registry (active).
Recent checks of TGGET Niche Research
CheckedResultHandshake
2 hours agoHandshake completed116 ms
2 days agoHandshake completed109 ms
4 days agoHandshake completed114 ms
6 days agoHandshake completed155 ms
8 days agoHandshake completed121 ms
10 days agoHandshake completed117 ms
12 days agoHandshake completed86 ms
13 days agoHandshake completed113 ms
15 days agoHandshake completed81 ms
16 days agoHandshake completed110 ms
18 days agoHandshake completed85 ms
20 days agoHandshake completed79 ms
21 days agoHandshake completed81 ms
23 days agoCredentials required—

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