Remote MCP · Endpoint

io.brewmark/brewmark MCP server

No. io.brewmark/brewmark answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://brewmark.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.brewmark/brewmark
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
121 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Grind settings for 200+ home coffee grinders, conversion between them, and help choosing one.
Listing
From the official MCP registry (active).
Recent checks of io.brewmark/brewmark
CheckedResultHandshake
33 minutes agoHandshake completed121 ms
3 days agoHandshake completed132 ms
13 days agoHandshake completed679 ms
13 days agoHandshake completed228 ms
15 days agoHandshake completed220 ms
16 days agoHandshake completed328 ms
17 days agoHandshake completed255 ms
18 days agoHandshake completed593 ms
18 days agoHandshake completed321 ms
20 days agoHandshake completed391 ms
22 days agoHandshake completed173 ms
25 days agoHandshake completed172 ms
27 days agoHandshake completed147 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 io.brewmark/brewmark and makes no claim about it beyond what these checks measured.