Is mcp-registry/io.github.lazymac2x/api-schema-drift-detector/breaking-change-analyzer working right now?

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

See all live alternatives to mcp-registry/io.github.lazymac2x/api-schema-drift-detector/breaking-change-analyzer →

FAQ

Is mcp-registry/io.github.lazymac2x/api-schema-drift-detector/breaking-change-analyzer working right now?

As of the latest check, mcp-registry/io.github.lazymac2x/api-schema-drift-detector/breaking-change-analyzer has a Glimind reliability score of 85/100 (grade B) and its current verdict is "healthy" — recommendation: proceed. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.

How reliable is mcp-registry/io.github.lazymac2x/api-schema-drift-detector/breaking-change-analyzer?

mcp-registry/io.github.lazymac2x/api-schema-drift-detector/breaking-change-analyzer scores 85/100 (grade B) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if mcp-registry/io.github.lazymac2x/api-schema-drift-detector/breaking-change-analyzer is down or failing?

Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 1000ms. Check Glimind for a live alternative before retrying.

What are the best alternatives to mcp-registry/io.github.lazymac2x/api-schema-drift-detector/breaking-change-analyzer?

Glimind surfaces live, capability-matched alternatives the moment mcp-registry/io.github.lazymac2x/api-schema-drift-detector/breaking-change-analyzer degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.lazymac2x%2Fapi-schema-drift-detector%2Fbreaking-change-analyzer.

How do I call mcp-registry/io.github.lazymac2x/api-schema-drift-detector/breaking-change-analyzer reliably?

Before calling, check mcp-registry/io.github.lazymac2x/api-schema-drift-detector/breaking-change-analyzer with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.lazymac2x%2Fapi-schema-drift-detector%2Fbreaking-change-analyzer) to get a known-good input shape, the expected output, a suggested timeout (~1000ms), and a live fallback.

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.lazymac2x%2Fapi-schema-drift-detector%2Fbreaking-change-analyzer.svg)](https://glimind.com/tool/mcp-registry%2Fio.github.lazymac2x%2Fapi-schema-drift-detector%2Fbreaking-change-analyzer)

Get the data

Agents: query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fio.github.lazymac2x%2Fapi-schema-drift-detector%2Fbreaking-change-analyzer. 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-30T11:06:34.029Z.