Remote MCP · Endpoint

blicht MCP MCP server

No. blicht MCP answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://blicht.com/mcp

The last check completed an MCP handshake.

Registry name
com.blicht/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
142 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
blicht.com knowledge platform: full-text search + Markdown articles (e-commerce, AI, lifestyle)
Listing
From the official MCP registry (active).
Recent checks of blicht MCP
CheckedResultHandshake
6 hours agoHandshake completed142 ms
2 days agoHandshake completed199 ms
4 days agoHandshake completed109 ms
5 days agoHandshake completed93 ms
7 days agoHandshake completed117 ms
8 days agoHandshake completed220 ms
9 days agoHandshake completed99 ms
12 days agoHandshake completed115 ms
13 days agoHandshake completed82 ms
15 days agoHandshake completed209 ms
16 days agoHandshake completed71 ms
17 days agoHandshake completed88 ms
18 days agoHandshake completed94 ms
19 days agoHandshake completed49 ms
20 days agoHandshake completed152 ms
21 days agoHandshake completed97 ms
22 days agoHandshake completed142 ms

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

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