Wikexa Knowledge
REMOTE · WIKEXA.COM
Wikipedia, Wikidata and Wiktionary as clean JSON, not HTML. 1.9M searchable. Free, no auth.
Available components
Last scanned (1 hour ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1281 tokens (~213/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Aug 26 0
- Stability: 0.97 → pass security
- 28 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1007 → 1241 ▼ functional
- New tool “papers” functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Tool “article” rewrote its description, which is the text the model reads security
- Tool “define” rewrote its description, which is the text the model reads security
- Tool “lookup” rewrote its description, which is the text the model reads security
- Tool “recent” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Schema quality: 168 → 201 ▼ functional
- Server version: 1.1.0 → 1.1.1 functional
- 4 Aug 26 0
- Server version: 1.0.0 → 1.1.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://wikexa.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wikexa.com | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8878c60b93b4ddb913f41c9670448d1c |
| SANs: wikexa.com, *.wikexa.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wikexa.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| wikexa.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wikexa.com/mcp | Verified | 200 | |
| http (plaintext) | http://wikexa.com/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
article ~160
The full text of an article, for when lookup()'s summary is not enough — sections as a JSON array, infobox as key/value facts, no HTML or wikitext to parse. Pass `sections` to pull only the parts you need (e.g. ["Early life"]) and `max_chars` to cap the payload; both exist because a long article will otherwise flood your context.
| Name | Type | Req | Description |
|---|---|---|---|
| corpus | string | – | Which corpus to read from. Defaults to wikipedia. |
| max_chars | integer | – | Optional cap on total section text returned. |
| sections | array | – | Optional section names to include (substring match, case-insensitive). Omit for the whole article. |
| title | string | yes | Article title, alias, or Q-id. |
No output schema declared.
No examples provided.
define ~213
What a word means, in thousands of languages — 8.15M dictionary entries with senses, part of speech, etymology and pronunciation. Covers what a general model is weakest at: historical languages (Old English, Gothic, Ancient Greek, Middle French) and hundreds of regional and indigenous ones. A single spelling often has entries in many languages and you get all of them — `hund` returns Danish, Gothic, Icelandic, Middle English and more — or pass `language` to narrow, `pos` for one part of speech. Use this for words and lookup() for things: define("java") gives the word in eight languages, lookup("Java") gives the island.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Optional language name as Wiktionary spells it, e.g. "English", "Latin", "Spanish". |
| pos | string | – | Optional part of speech filter, e.g. "Noun", "Verb", "Adjective". |
| word | string | yes | The word or phrase to define. |
No output schema declared.
No examples provided.
lookup ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| corpus | string | – | Which corpus to look in. Defaults to wikipedia. Use wikivoyage for travel guides, wikiquote for quotations, wikibooks for textbooks, wikiversity for course material. |
| entity | string | yes | Entity name, Wikipedia title, alias, or Wikidata Q-id (e.g. "Tim Cook", "Q312"). |
No output schema declared.
No examples provided.
papers ~248
Academic paper metadata from 57M+ works — title, abstract, authors, citations, DOI and open access URL. Covers every field: CS, medicine, physics, economics, biology, and more. Search by keywords (e.g. "transformer attention"), by topic name (e.g. "machine learning"), or by OpenAlex topic ID. Returns papers sorted by citation count. Source: OpenAlex (CC0 metadata). Use this when the user needs scholarly references, citation counts, or research context that Wikipedia does not cover.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum papers to return, 1-20 (default 5). |
| query | string | – | Keywords to search for. Matches topic names to find the right research area, then filters by title and abstract. Example: "transformer attention", "CRISPR gene editing". |
| topic | string | – | Topic name or OpenAlex topic ID. Names are resolved automatically (e.g. "machine learning" → T10135). Use an ID like "T10135" if you already know it. Optional — query alone works. |
| year | integer | – | Publication year to filter on, e.g. 2023. |
No output schema declared.
No examples provided.
recent ~143
What changed in the last hours or days — the escape hatch for facts newer than your training cutoff. Reach for this whenever the answer could have moved since you were trained: elections, appointments, acquisitions, releases, deaths, records. Returns titles with timestamps and edit comments; resolve any of them with lookup(). Pass `topic` to filter and `hours` to widen the window up to a week.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Look-back window in hours, 1-168 (default 24). |
| limit | integer | – | Maximum changes, 1-100 (default 25). |
| topic | string | – | Optional case-insensitive filter on title or edit comment. |
No output schema declared.
No examples provided.
search ~184
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 text.
| Name | Type | Req | Description |
|---|---|---|---|
| corpus | string | – | 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. |
| limit | integer | – | Maximum results, 1-50 (default 10). |
| query | string | yes | Free-text search query. |
No output schema declared.
No examples provided.
How do I install the Wikexa Knowledge MCP server?
Wikexa Knowledge is a hosted endpoint at https://wikexa.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · wikexa.com
claude mcp add --transport http com-wikexa-knowledge 'https://wikexa.com/mcp'
What is the Wikexa Knowledge MCP server?
Wikexa Knowledge is an MCP server listed in the public MCP registry as com.wikexa/knowledge. Wikipedia, Wikidata and Wiktionary as clean JSON, not HTML. 1.9M searchable. Free, no auth. This page covers its hosted endpoint (https://wikexa.com/mcp).
Is the Wikexa Knowledge MCP server safe to use?
Wikexa Knowledge scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Wikexa Knowledge MCP server expose?
Wikexa Knowledge exposes 6 tools: lookup, article, define, search, recent, papers. Their descriptions and schemas cost roughly 1,131 tokens of context every time the server is loaded.
Does the Wikexa Knowledge MCP server require authentication?
No. We connected to Wikexa Knowledge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Wikexa Knowledge MCP server still maintained?
Wikexa Knowledge is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.