Remote MCP · Endpoint

Boonful Studio MCP server

No. Boonful Studio answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://boonful.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.boonful/studio
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
473 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Publish and sell what you build with Claude: apps, ebooks and courses, with checkout and a feed.
Listing
From the official MCP registry (active).
Recent checks of Boonful Studio
CheckedResultHandshake
6 hours agoHandshake completed473 ms
9 days agoHandshake completed596 ms
10 days agoHandshake completed450 ms
11 days agoHandshake completed591 ms
12 days agoHandshake completed431 ms
14 days agoHandshake completed646 ms
15 days agoHandshake completed466 ms
15 days agoHandshake completed405 ms
17 days agoHandshake completed902 ms
19 days agoHandshake completed501 ms
22 days agoHandshake completed565 ms
24 days agoHandshake completed510 ms
26 days agoHandshake completed384 ms
28 days agoHandshake completed720 ms

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

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