Is oma_read_dns working right now?

fi.lanetti/oma · mcp-registry/fi.lanetti/oma/oma_read_dns

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-tool. Other clients
healthy
Recommendation: proceed
uptime (30d probes)
99.9%
checks observed
205
p50 latency
880ms
data basis
probe-history (205 checks, 99.9% up)

Recovery track record: 3 outages in 90 days, median time-to-recovery 4 min.

Recent contract changes

Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.

See all live alternatives to oma_read_dns →

Never call a dead tool again

Agents that check Glimind first make fewer failed calls, waste fewer tokens, and auto-route around outages like this one. Add it in ~10 seconds — free, no signup:

One click:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-tool

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-tool"
    }
  }
}

Or wrap your calls with the SDK: npm i glimind · pip install glimind. See how it works

FAQ

Is oma_read_dns working right now?

As of the latest check, oma_read_dns (mcp-registry/fi.lanetti/oma/oma_read_dns) has a Glimind reliability score of 83/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 oma_read_dns?

oma_read_dns scores 83/100 (grade B) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if oma_read_dns is down or failing?

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

What are the best alternatives to oma_read_dns?

Glimind surfaces live, capability-matched alternatives the moment oma_read_dns degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Ffi.lanetti%2Foma%2Foma_read_dns.

How do I call oma_read_dns reliably?

Before calling, check oma_read_dns with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Ffi.lanetti%2Foma%2Foma_read_dns) to get a known-good input shape, the expected output, a suggested timeout (~2640ms), 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 badge for mcp-registry/fi.lanetti/oma/oma_read_dns

Markdown
[![Glimind reliability](https://glimind.com/v1/badge/mcp-registry%2Ffi.lanetti%2Foma%2Foma_read_dns.svg)](https://glimind.com/tool/mcp-registry%2Ffi.lanetti%2Foma%2Foma_read_dns?ref=badge)
HTML
<a href="https://glimind.com/tool/mcp-registry%2Ffi.lanetti%2Foma%2Foma_read_dns?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Ffi.lanetti%2Foma%2Foma_read_dns.svg" alt="Glimind reliability"></a>
reStructuredText
.. image:: https://glimind.com/v1/badge/mcp-registry%2Ffi.lanetti%2Foma%2Foma_read_dns.svg
   :target: https://glimind.com/tool/mcp-registry%2Ffi.lanetti%2Foma%2Foma_read_dns?ref=badge
   :alt: Glimind reliability

Operator of fi.lanetti/oma?

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%2Ffi.lanetti%2Foma%2Foma_read_dns. 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-11-22T16:21:48.223Z.

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.

Feedback
Help us improve