Remote MCP · Endpoint

Mike Fluff MCP server

No. Mike Fluff answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://www.mikefluff.com/mcp

The last check completed an MCP handshake.

Registry name
com.mikefluff/mikefluff
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
422 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Answers from Mike Fluff Press books, the business diagnostic, AI-text check, call booking.
Listing
From the official MCP registry (active).
Recent checks of Mike Fluff
CheckedResultHandshake
43 minutes agoHandshake completed422 ms
8 days agoHandshake completed356 ms
9 days agoHandshake completed301 ms
11 days agoHandshake completed313 ms
12 days agoHandshake completed409 ms
13 days agoHandshake completed319 ms
14 days agoHandshake completed314 ms
14 days agoHandshake completed336 ms
16 days agoHandshake completed379 ms
19 days agoHandshake completed300 ms
21 days agoHandshake completed301 ms
24 days agoHandshake completed323 ms
26 days agoHandshake completed293 ms
28 days agoHandshake completed276 ms

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

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