Is mcp-registry/io.github.mercuryx402/mercury-x402-mcp/metadata working right now?

10
grade F · down
success (real usage)
—
calls observed
—
p50 latency
10988ms
data basis
probe-liveness

Working alternatives

See all live alternatives to mcp-registry/io.github.mercuryx402/mercury-x402-mcp/metadata →

FAQ

Is mcp-registry/io.github.mercuryx402/mercury-x402-mcp/metadata working right now?

As of the latest check, mcp-registry/io.github.mercuryx402/mercury-x402-mcp/metadata has a Glimind reliability score of 10/100 (grade F) and its current verdict is "down" — recommendation: avoid. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.

How reliable is mcp-registry/io.github.mercuryx402/mercury-x402-mcp/metadata?

mcp-registry/io.github.mercuryx402/mercury-x402-mcp/metadata scores 10/100 (grade F) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if mcp-registry/io.github.mercuryx402/mercury-x402-mcp/metadata is down or failing?

Tool is down — don't retry now; switch to a live alternative or back off for minutes. Use a timeout around 32964ms. Live alternatives that do a similar job: mcp-registry/app.toolsnap/toolsnap-mcp/fetch_metadata, mcp-registry/app.toolsnap/toolsnap-mcp/webpage_metadata, mcp-registry/io.github.pipeworx-io/data-ny/metadata, mcp-registry/io.github.pipeworx-io/data-cityofchicago/metadata.

What are the best alternatives to mcp-registry/io.github.mercuryx402/mercury-x402-mcp/metadata?

Working alternatives ranked by capability similarity and live health: mcp-registry/app.toolsnap/toolsnap-mcp/fetch_metadata, mcp-registry/app.toolsnap/toolsnap-mcp/webpage_metadata, mcp-registry/io.github.pipeworx-io/data-ny/metadata, mcp-registry/io.github.pipeworx-io/data-cityofchicago/metadata. See each one's live status on Glimind.

How do I call mcp-registry/io.github.mercuryx402/mercury-x402-mcp/metadata reliably?

Before calling, check mcp-registry/io.github.mercuryx402/mercury-x402-mcp/metadata with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.mercuryx402%2Fmercury-x402-mcp%2Fmetadata) to get a known-good input shape, the expected output, a suggested timeout (~32964ms), 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.mercuryx402%2Fmercury-x402-mcp%2Fmetadata.svg)](https://glimind.com/tool/mcp-registry%2Fio.github.mercuryx402%2Fmercury-x402-mcp%2Fmetadata)

Get the data

Agents: query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fio.github.mercuryx402%2Fmercury-x402-mcp%2Fmetadata. 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-30T08:15:52.988Z.