Remote MCP · Endpoint

mcp.tc directory MCP server

No. mcp.tc directory answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://mcp.tc/mcp

The last check completed an MCP handshake.

Registry name
tc.mcp/mcp-tc
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
308 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search the mcp.tc directory of MCP servers: URLs, install commands, sign-in types, tools, setup.
Website
https://mcp.tc/docs/mcp
Listing
From the official MCP registry (active).
Recent checks of mcp.tc directory
CheckedResultHandshake
56 minutes agoHandshake completed308 ms
1 day agoHandshake completed311 ms
2 days agoHandshake completed479 ms
5 days agoHandshake completed315 ms
8 days agoHandshake completed319 ms
10 days agoHandshake completed333 ms
12 days agoHandshake completed333 ms
14 days agoHandshake completed353 ms
16 days agoHandshake completed305 ms
18 days agoHandshake completed386 ms
20 days agoHandshake completed324 ms
22 days agoHandshake completed321 ms
23 days agoHandshake completed321 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 mcp.tc directory and makes no claim about it beyond what these checks measured.