Is mcp-registry/io.github.anteos-health/anteos-booking/find_next_available working right now?

85
grade B · healthy
success (real usage)
—
calls observed
—
p50 latency
631ms
data basis
probe-liveness

Embed this badge

Show live reliability in your README or status page:

Glimind reliability badge

[![Glimind reliability](https://glimind.com/v1/badge/mcp-registry%2Fio.github.anteos-health%2Fanteos-booking%2Ffind_next_available.svg)](https://glimind.com/tool/mcp-registry%2Fio.github.anteos-health%2Fanteos-booking%2Ffind_next_available)

Get the data

Agents: query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fio.github.anteos-health%2Fanteos-booking%2Ffind_next_available. Install the SDK to contribute outcomes (privacy-preserving) and sharpen this rating — free key · docs.

Rating methodology is transparent and neutral — Glimind sells no tools and runs no integrations; it only measures. Updated 2026-06-30T01:57:43.304Z.