Remote MCP · Endpoint

CodeTrendy MCP server

No. CodeTrendy answered an MCP handshake 59 minutes ago.

UpLast checked 59 minutes ago

Server URL

https://codetrendy.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.codetrendy/directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
424 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search the CodeTrendy directory of websites and tools. Read-only, no API key.
Listing
From the official MCP registry (active).
Recent checks of CodeTrendy
CheckedResultHandshake
59 minutes agoHandshake completed424 ms
9 days agoHandshake completed393 ms
10 days agoHandshake completed190 ms
11 days agoHandshake completed370 ms
12 days agoHandshake completed370 ms
14 days agoHandshake completed373 ms
14 days agoHandshake completed166 ms
15 days agoHandshake completed765 ms
17 days agoHandshake completed419 ms
19 days agoHandshake completed372 ms
21 days agoHandshake completed346 ms
24 days agoHandshake completed172 ms
26 days agoHandshake completed320 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.

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