Is search working right now?

com.wikexa/knowledge · mcp-registry/com.wikexa/knowledge/search

Recovery track record: 21 outages in 90 days, median time-to-recovery 25.4 h.

Recent contract changes

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

• schema_changed — papers (2026-10-07)
• added — papers (2026-08-27)
• schema_changed — lookup (2026-07-31)
• schema_changed — article (2026-07-31)
• added — define (2026-07-31)

Working alternatives

• search_articles io.github.lazymac2x/blog
• search io.github.privatelawattorneys/wiki-private-law
• search_items dev.nichedb/nichedb
• wikipedia_search_articles io.github.cyanheads/wikipedia-mcp-server

See all live alternatives to search →

claude mcp add --transport http glimind https://glimind.com/mcp

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

FAQ

Is search working right now?

As of the latest check, search (mcp-registry/com.wikexa/knowledge/search) has a Glimind reliability score of 38/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 search?

search scores 38/100 (grade F) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if search 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: search_articles, search, search_items, wikipedia_search_articles.

What are the best alternatives to search?

Working alternatives ranked by capability similarity and live health: search_articles, search, search_items, wikipedia_search_articles. See each one's live status on Glimind.

How do I call search reliably?

Before calling, check search with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fcom.wikexa%2Fknowledge%2Fsearch) 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%2Fcom.wikexa%2Fknowledge%2Fsearch.svg)](https://glimind.com/tool/mcp-registry%2Fcom.wikexa%2Fknowledge%2Fsearch?ref=badge)

<a href="https://glimind.com/tool/mcp-registry%2Fcom.wikexa%2Fknowledge%2Fsearch?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fcom.wikexa%2Fknowledge%2Fsearch.svg" alt="Glimind reliability"></a>

.. image:: https://glimind.com/v1/badge/mcp-registry%2Fcom.wikexa%2Fknowledge%2Fsearch.svg
   :target: https://glimind.com/tool/mcp-registry%2Fcom.wikexa%2Fknowledge%2Fsearch?ref=badge
   :alt: Glimind reliability

Operator of com.wikexa/knowledge?

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%2Fcom.wikexa%2Fknowledge%2Fsearch. 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-18T23:46:17.950Z.

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.