Remote MCP · Endpoint

lt.namiko/mcp MCP server

No. lt.namiko/mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.namiko.lt/mcp

The last check completed an MCP handshake.

Registry name
lt.namiko/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
278 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search NAMIKO fermented drinks products and get product details via AI agents.
Listing
From the official MCP registry (active).
Recent checks of lt.namiko/mcp
CheckedResultHandshake
1 hour agoHandshake completed278 ms
2 days agoHandshake completed285 ms
4 days agoHandshake completed274 ms
5 days agoHandshake completed282 ms
7 days agoHandshake completed276 ms
8 days agoHandshake completed277 ms
9 days agoHandshake completed782 ms
12 days agoHandshake completed275 ms
13 days agoHandshake completed280 ms
15 days agoHandshake completed276 ms
17 days agoHandshake completed294 ms
18 days agoHandshake completed274 ms
19 days agoHandshake completed351 ms
20 days agoHandshake completed280 ms
21 days agoHandshake completed300 ms
21 days agoHandshake completed1.03 s
23 days agoHandshake completed289 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 lt.namiko/mcp and makes no claim about it beyond what these checks measured.