Is security_txt_security_txt_get working right now?

io.cohereon.manifold/imperium-manifold · mcp-registry/io.cohereon.manifold/imperium-manifold/security_txt_security_txt_get

healthy
Recommendation: proceed
uptime (30d probes)
99.9%
checks observed
3,609
p50 latency
2.6s
data basis
probe-history (3609 checks, 99.9% up)

Recovery track record: 4 outages in 90 days, median time-to-recovery 8 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 security_txt_security_txt_get →

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

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

FAQ

Is security_txt_security_txt_get working right now?

As of the latest check, security_txt_security_txt_get (mcp-registry/io.cohereon.manifold/imperium-manifold/security_txt_security_txt_get) has a Glimind reliability score of 89/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 security_txt_security_txt_get?

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

What should I do if security_txt_security_txt_get is down or failing?

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

What are the best alternatives to security_txt_security_txt_get?

Glimind surfaces live, capability-matched alternatives the moment security_txt_security_txt_get degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fio.cohereon.manifold%2Fimperium-manifold%2Fsecurity_txt_security_txt_get.

How do I call security_txt_security_txt_get reliably?

Before calling, check security_txt_security_txt_get with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.cohereon.manifold%2Fimperium-manifold%2Fsecurity_txt_security_txt_get) to get a known-good input shape, the expected output, a suggested timeout (~7803ms), 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/io.cohereon.manifold/imperium-manifold/security_txt_security_txt_get

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

Operator of io.cohereon.manifold/imperium-manifold?

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.cohereon.manifold%2Fimperium-manifold%2Fsecurity_txt_security_txt_get. 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-10-16T20:03:52.725Z.

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.