Remote MCP · Endpoint

TechFabric MCP server

No. TechFabric answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://www.techfabric.com/mcp

The last check completed an MCP handshake.

Registry name
com.techfabric/techfabric
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
893 ms
Tools exposed
36 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Write TechFabric posts from your agent. Walk through posts, compare studies, check readiness.
Listing
From the official MCP registry (active).
Recent checks of TechFabric
CheckedResultHandshake
52 minutes agoHandshake completed893 ms
3 days agoHandshake completed985 ms
12 days agoHandshake completed1.59 s
13 days agoHandshake completed419 ms
14 days agoHandshake completed1.63 s
15 days agoHandshake completed502 ms
17 days agoHandshake completed1.03 s
18 days agoHandshake completed747 ms
18 days agoHandshake completed808 ms
20 days agoHandshake completed1.13 s
22 days agoHandshake completed1.60 s
25 days agoHandshake completed1.32 s
27 days agoHandshake completed1.22 s
29 days agoHandshake completed930 ms

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