mcpbeat

Wikexa Knowledge MCP Server

com.wikexa/knowledge
answering

Wikexa Knowledge is answering right now. Last checked 8 min ago. It exposes 5 tools.

Structured Wikipedia + Wikidata for AI agents. Clean JSON, not HTML. Free, no auth.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
137 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add knowledge --transport http https://wikexa.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "knowledge": {
      "url": "https://wikexa.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.knowledge]
url = "https://wikexa.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "knowledge": {
      "url": "https://wikexa.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "knowledge": {
      "url": "https://wikexa.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

article
article
Full Wikipedia article as clean structured JSON — sections as an array, infobox as key/value facts, no HTML or wikitext. Pass `sections` to fetch only the parts you need (e.g. ["History"]) and `max_chars` to cap the payload; both exist to keep long articles from flooding your context.
define
define
Dictionary lookup from Wiktionary: definitions, senses, part of speech, etymology and pronunciation, grouped by language. One word can be a noun in English and a verb in Latin, and you get both — pass `language` to narrow it, or `pos` to keep only one part of speech. Use this rather than lookup() for what a word means; lookup() is for entities.
lookup
lookup
Look up any entity (person, company, place, concept) and get structured facts plus a ~200-token summary. Resolves aliases and Wikidata Q-ids, so "Apple", "Apple Inc", and "Q312" all return the same entity. Use this instead of fetching a web page: a Wikipedia HTML fetch costs ~15,000 tokens to recover ~500 tokens of facts. Free and unlimited.
recent
recent
Articles changed recently, optionally filtered by topic. This is the freshness escape hatch for facts newer than your training cutoff — elections, appointments, releases, deaths. Returns titles with timestamps and edit comments; resolve any of them with lookup().
search
search
Find entities by fuzzy text match when you do not know the exact title. Returns ranked {title, wikidata_id, description, summary_snippet} — ranking blends full-text relevance with monthly pageviews, so common meanings win ("apple" returns Apple Inc. and the fruit, not disambiguation pages). Follow up with lookup() or article().

Endpoints

URLTransportStateLatencyChecked
https://wikexa.com/mcp streamable-http answering 716 ms 8 min ago

Wikexa Knowledge — questions

Answers built from our own checks of this server.

What can Wikexa Knowledge do?
It exposes 5 tools, read directly from the server on our last check. Among them: article, define, lookup, recent, search. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Wikexa Knowledge working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 137 ms. The bar chart above shows every period we have measured.
How do I connect Wikexa Knowledge?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Wikexa Knowledge need an API key?
No. Wikexa Knowledge completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Wikexa Knowledge?
It answers our handshake in 137 ms on average, which is faster than 76% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.