Is mcp-registry/io.globalping/mcp/mtr working right now?

Working alternatives

• mcp-registry/com.geekflare/mcp/mtr com.geekflare/mcp
• mcp-registry/io.github.pipeworx-io/hackertarget/mtr io.github.pipeworx-io/hackertarget
• mcp-registry/io.github.pipeworx-io/hackertarget/traceroute io.github.pipeworx-io/hackertarget
• mcp-registry/io.github.lazymac2x/citation-verifier/probe_url io.github.lazymac2x/citation-verifier

See all live alternatives to mcp-registry/io.globalping/mcp/mtr →

# MCP client — add one endpoint:
https://glimind.com/mcp

# or wrap your calls with the SDK:
npm i glimind          # pip install glimind

FAQ

Is mcp-registry/io.globalping/mcp/mtr working right now?

As of the latest check, mcp-registry/io.globalping/mcp/mtr has a Glimind reliability score of 15/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.globalping/mcp/mtr?

mcp-registry/io.globalping/mcp/mtr scores 15/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.globalping/mcp/mtr 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 1000ms. Live alternatives that do a similar job: mcp-registry/com.geekflare/mcp/mtr, mcp-registry/io.github.pipeworx-io/hackertarget/mtr, mcp-registry/io.github.pipeworx-io/hackertarget/traceroute, mcp-registry/io.github.lazymac2x/citation-verifier/probe_url.

What are the best alternatives to mcp-registry/io.globalping/mcp/mtr?

Working alternatives ranked by capability similarity and live health: mcp-registry/com.geekflare/mcp/mtr, mcp-registry/io.github.pipeworx-io/hackertarget/mtr, mcp-registry/io.github.pipeworx-io/hackertarget/traceroute, mcp-registry/io.github.lazymac2x/citation-verifier/probe_url. See each one's live status on Glimind.

How do I call mcp-registry/io.globalping/mcp/mtr reliably?

Before calling, check mcp-registry/io.globalping/mcp/mtr with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.globalping%2Fmcp%2Fmtr) to get a known-good input shape, the expected output, a suggested timeout (~1000ms), and a live fallback.

Embed this live badge

Show live reliability in your README or status page. It auto-updates and links back here — copy one:

[![Glimind reliability](https://glimind.com/v1/badge/mcp-registry%2Fio.globalping%2Fmcp%2Fmtr.svg)](https://glimind.com/tool/mcp-registry%2Fio.globalping%2Fmcp%2Fmtr?ref=badge)

<a href="https://glimind.com/tool/mcp-registry%2Fio.globalping%2Fmcp%2Fmtr?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fio.globalping%2Fmcp%2Fmtr.svg" alt="Glimind reliability"></a>

.. image:: https://glimind.com/v1/badge/mcp-registry%2Fio.globalping%2Fmcp%2Fmtr.svg
   :target: https://glimind.com/tool/mcp-registry%2Fio.globalping%2Fmcp%2Fmtr?ref=badge
   :alt: Glimind reliability

Operator of mcp-registry/io.globalping/mcp/mtr?

Claim this listing → Prove you control this server (GitHub repo, live endpoint, or DNS — automated, ~1 min) to unlock the Verified operator marker, a remediation checklist (exactly why your score is what it is + how to raise it), and owner analytics. Or just embed the badge above and improve your score by having users report real outcomes (privacy-clean) via the free SDK. Glimind is neutral and sells no tools — the score is never for sale, so the fastest path to a better score is real uptime plus real usage.

Get the data (agents)

Query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fio.globalping%2Fmcp%2Fmtr. The signed reliability feed for gateways/routers: GET https://glimind.com/v1/reliability/feed.

Rating methodology is transparent and neutral — Glimind sells no tools and runs no integrations; it only measures. Updated 2026-07-02T01:49:33.585Z.

This score is an automated estimate derived from safe liveness probes and privacy-clean outcomes reported by users; it may be incomplete, delayed, or inaccurate, and reflects reachability from Glimind's vantage point — not a statement of fact about the service. Glimind is not affiliated with, endorsed by, or acting for this tool or its operator; all names belong to their owners. Operator? Request a correction, or remove your server from measurement, via https://glimind.com/opt-out or [email protected] — we act promptly.