Is the Wikexa Knowledge MCP server down?

mcp-registry/com.wikexa/knowledge · v1.1.1

healthy
Last checked 2026-10-26 12:10 UTC · handshake 264ms

As of 2026-10-26 12:10 UTC, the Wikexa Knowledge MCP server is up with a Glimind reliability score of 74/100 (grade C). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 27 outages in 90 days, with a median recovery of 25.4 hours.

uptime (30d checks)
99%
checks observed
3,528
outages (90d)
27
tools
6

Wikipedia, Wikidata and Wiktionary as clean JSON, not HTML. 1.9M searchable. Free, no auth.

Install Wikexa Knowledge MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http wikexa-knowledge-mcp-server https://wikexa.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "wikexa-knowledge-mcp-server": {
      "type": "http",
      "url": "https://wikexa.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 6 tool(s); ~1,597 tokens of tool definitions.
Scores higher than 36% of 15,748 MCP servers Glimind has audited.
Its tool list costs an agent ~1,597 tokens per session — lighter than 60% of servers.
83 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability75
Stability96

What to fix (4)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: article, define, lookup, papers, recent and 1 more

Reachable 99.0% of the time over the last 30 days; median recovery 1526 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.wikexa%2Fknowledge/fixes

lookup 1 change
{
  "name": "lookup",
  "description": "Facts about any named thing — person, company, place, species, event, concept. Returns structured fields (dates, identifiers, relationships) plus a ~200-token summary, drawn from 10.2M entity records. Prefer this over fetching an encyclopedia page: the HTML costs ~15,000 tokens to recover ~500 tokens of fact. Resolves aliases and Wikidata Q-ids, so \"Apple\", \"Apple Inc\" and \"Q312\" all reach the same entity. Free, no key.",
  "inputSchema": {
    "type": "object",
    "required": [
      "entity"
    ],
    "properties": {
      "corpus": {
        "enum": [
          "wikipedia",
          "wikiquote",
          "wikibooks",
          "wikivoyage",
          "wikiversity"
        ],
        "type": "string",
        "description": "Which corpus to look in. Defaults to wikipedia. Use wikivoyage for travel guides, wikiquote for quotations, wikibooks for textbooks, wikiversity for course material."
      },
      "entity": {
        "type": "string",
        "description": "Entity name, Wikipedia title, alias, or Wikidata Q-id (e.g. \"Tim Cook\", \"Q312\")."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
search 1 change
{
  "name": "search",
  "description": "Find the right title when you only have a partial name or a rough description. Returns ranked {title, wikidata_id, description, summary_snippet}; ranking blends text relevance with monthly pageviews and follows redirects, so abbreviations land on the real article — \"usa\" returns United States, \"jfk\" returns John F. Kennedy, \"apple\" returns Apple Inc. rather than a disambiguation page. Searches every corpus at once unless you pass `corpus`. Follow up with lookup() for facts or article() for the t",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "description": "Maximum results, 1-50 (default 10)."
      },
      "query": {
        "type": "string",
        "description": "Free-text search query."
      },
      "corpus": {
        "enum": [
          "wikipedia",
          "wiktionary",
          "wikiquote",
          "wikibooks",
          "wikivoyage",
          "wikiversity"
        ],
        "type": "string",
        "description": "Restrict to one corpus. Omit to search all of them at once, which is usually what you want when you do not know where the answer is."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.wikexa/knowledge"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.wikexa/knowledge"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.wikexa%2Fknowledge.svg)](https://glimind.com/server/mcp-registry%2Fcom.wikexa%2Fknowledge?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.wikexa%2Fknowledge?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.wikexa%2Fknowledge.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.wikexa%2Fknowledge.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.wikexa%2Fknowledge?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e4b3e98bc68aa0a8…, first seen 2026-10-17, included at leaf 2002 of 72,700. Version history · verify what your client received.

Tools (6)

Compare: most reliable knowledge servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

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"
    }
  }
}

FAQ

Is the Wikexa Knowledge MCP server down right now?

As of 2026-10-26 12:10 UTC, the Wikexa Knowledge MCP server is up with a Glimind reliability score of 74/100 (grade C). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 27 outages in 90 days, with a median recovery of 25.4 hours.

How many tools does Wikexa Knowledge MCP server provide?

Wikexa Knowledge MCP server advertises 6 tools, including article, define, lookup, papers, recent.

How do I install Wikexa Knowledge MCP server?

Point your MCP client at this streamable-http endpoint: https://wikexa.com/mcp

Is the Wikexa Knowledge MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Wikexa Knowledge MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve