Remote MCP · Endpoint

Breeze ChMS MCP by usefulapi MCP server

Yes, as of 2 hours ago: the server returned an HTTP error.

DownLast checked 2 hours ago

Server URL

https://breeze-chms.usefulapi.io/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.usefulapi/breeze-chms
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
24 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Manage Breeze ChMS people, tags, events, check-ins, volunteers and contributions.
Website
https://usefulapi.io/breeze-chms/
Repository
https://github.com/m190/usefulapi-mcp
Listing
From the official MCP registry (active).
Recent checks of Breeze ChMS MCP by usefulapi
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
2 days agoHandshake completed430 ms
4 days agoHandshake completed197 ms
6 days agoHandshake completed243 ms
8 days agoHandshake completed322 ms
10 days agoHandshake completed484 ms
12 days agoHandshake completed322 ms
14 days agoHandshake completed200 ms
15 days agoHandshake completed197 ms
16 days agoHandshake completed225 ms
18 days agoHandshake completed328 ms
20 days agoHandshake completed229 ms
22 days agoHandshake completed167 ms
23 days agoHandshake completed289 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Breeze ChMS MCP by usefulapi and makes no claim about it beyond what these checks measured.