# Wikipedia (npm · @pipeworx/mcp-wikipedia) Wikipedia MCP — wraps Wikipedia REST API (free, no auth) - Trust score: 82/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-wikipedia/wikipedia-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-wikipedia/wikipedia-mcp) - npm · `@pipeworx/mcp-wikipedia`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-wikipedia/pipeworx-mcp-wikipedia.md), [page](https://verifymcp.io/servers/pipeworx-io-wikipedia/pipeworx-mcp-wikipedia) ## Channel facts - Registry: `npm` - Package: `@pipeworx/mcp-wikipedia` - Version: `0.2.0` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 100/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - No production dependencies, so there is no dependency health to assess. - **Provenance & Transparency**: 97/100 - Source repository is publicly reachable at the declared URL. - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-wikipedia). - Clear OSI-approved license (MIT). - Actively maintained (last published 7 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 64/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 1100 tokens (~220/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 23/100 - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the Wikipedia MCP server? Wikipedia runs locally as an npm package, launched with npx -y @pipeworx/mcp-wikipedia. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add pipeworx-io-wikipedia -- npx -y @pipeworx/mcp-wikipedia ``` ### Cursor ```json { "mcpServers": { "pipeworx-io-wikipedia": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-wikipedia" ] } } } ``` ### VS Code ```json { "servers": { "pipeworx-io-wikipedia": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-wikipedia" ] } } } ``` ### Codex ```bash codex mcp add pipeworx-io-wikipedia -- npx -y @pipeworx/mcp-wikipedia ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "pipeworx-io-wikipedia": { "type": "local", "command": [ "npx", "-y", "@pipeworx/mcp-wikipedia" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add pipeworx-io-wikipedia --command npx --arg -y --arg @pipeworx/mcp-wikipedia ``` ### Hermes ```yaml mcp_servers: pipeworx-io-wikipedia: command: "npx" args: ["-y", "@pipeworx/mcp-wikipedia"] ``` ### Netclaw ```json { "McpServers": { "pipeworx-io-wikipedia": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "@pipeworx/mcp-wikipedia" ] } } } ``` ### Vellum ```bash assistant mcp add pipeworx-io-wikipedia -t stdio -c npx -a -y @pipeworx/mcp-wikipedia ``` ### Other ```json { "mcpServers": { "pipeworx-io-wikipedia": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-wikipedia" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 82, +1) No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-02 (score 81, +1) No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-31 (score 80, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-29 (score 79) First indexed and scored. ## MCP tools (5) ### `search_wikipedia` (~373 tokens) Search Wikipedia for encyclopedic facts, sports event schedules, medal tables, officeholder rosters and biographies. Covers multi-sport games and tournaments edition by edition — Olympics, Asian Games, Commonwealth Games, Pan American Games, SEA Games, World Cup — with per-sport competition schedules, session dates, venues, results and medal tables, each on its own article ("Table tennis at the 2026 Asian Games", "Athletics at the 2028 Summer Olympics"). Use it when the article title is NOT predictable from the question, to find the exact title, then read the article body with get_article_extract; when the title IS predictable ("Table tennis at the 2026 Asian Games") skip straight to get_article_extract, since a search snippet is one truncated line. Also the right tool for government composition and officeholder rosters — "current cabinet members of Japan", "list of ministers and their positions", "who is in the German government", "cabinet of 2025" — Wikipedia keeps cabinet, ministry, and government lists current for every country. And for general knowledge: "who is X", "what is Y", "history of Z", definitions. Returns matching article titles, snippets, page IDs, word counts. Chain with get_article_extract for the full text or a single section. Cheaper + more structured than scraping web search results; covers ~7M English articles updated continuously by the Wikipedia community. Input parameters: - `limit` (number): Number of results to return (1-50, default 10) - `query` (string, required): Search query, in ENGLISH — this searches the English Wikipedia, and a query in another language returns 0 hits. Translate non-English questions into English keywords first ("日本现任内阁成员名单" → "current Ja… ### `get_article_summary` (~123 tokens) AUTHORITATIVE summary of a Wikipedia article by exact title — typically faster + cheaper than search_wikipedia + get_article_sections + scrape. Returns the article's lead paragraph (the editorial overview), one-line description, thumbnail image, and a few related-content links. Use when you already have the canonical title (got it from search_wikipedia, or it's a well-known entity) and need the standard "what is X" prose answer. For the full section breakdown use get_article_sections. Input parameters: - `title` (string, required): Wikipedia article title (e.g., "Albert Einstein") ### `get_article_sections` (~104 tokens) Section outline of a Wikipedia article by title — the table-of-contents. Returns all headings + hierarchy (H2, H3, etc.) without the prose. Use when the article is long (history, science topics, biographies) and you want to navigate to a specific section vs reading the entire summary. Chain with get_article_summary for the lead text. Cheap, structural-only. Input parameters: - `title` (string, required): Wikipedia article title (e.g., "World War II") ### `get_random_articles` (~51 tokens) Discover random Wikipedia articles for serendipitous learning. Returns title, introduction text, and page ID. Input parameters: - `count` (number): Number of random articles to fetch (1-10, default 5) ### `get_article_extract` (~398 tokens) Full text of a Wikipedia article by title — the ACTUAL prose AND its tables, not just the lead paragraph. This is how you read a competition schedule, fixture list, medal table, results grid or roster: get_article_extract({title: "Table tennis at the 2026 Asian Games"}) returns the venue, the dates and the day-by-day event schedule. Answers "when is at ", "what are the dates", "who won ", "explain X in detail", "what does the article say about ", reading the history/methods/etc. CALL IT DIRECTLY when the title is predictable from the question — Wikipedia titles are regular, so "when is table tennis at the Asian Games" is the article "Table tennis at the 2026 Asian Games", and the same pattern gives "Athletics at the 2028 Summer Olympics", "India at the 2026 Asian Games", "2026 FIFA World Cup". Constructing the title and reading the article beats searching first, because the search snippet is one truncated line and this returns the whole thing. Titles are exact: on a miss you get a user_error naming search_wikipedia as the recovery. PREFER OVER get_article_summary whenever the lead paragraph is not enough. Omit section for the whole article (capped by max_chars); pass a section number (from get_article_sections) for just that one. Returns plain text with headings marked == like this == and table rows one per line, cells separated by | . Input parameters: - `max_chars` (number): Cap on characters returned (1000-100000, default 40000). - `section` (number): OPTIONAL section number (from get_article_sections) to return just that section. Omit for the full article. - `title` (string, required): Wikipedia article title (e.g. "CRISPR", "Albert Einstein"). ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-wikipedia/pipeworx-mcp-wikipedia#diagnostics ## Score history - 2026-11-05: 82 - 2026-11-04: 82 - 2026-11-03: 81 - 2026-11-02: 81 - 2026-11-01: 80 - 2026-10-31: 80 - 2026-10-30: 79 - 2026-10-29: 79 ## Common questions ### What is the Wikipedia MCP server? Wikipedia is an MCP server listed in the public MCP registry as io.github.pipeworx-io/wikipedia. Wikipedia MCP, wraps Wikipedia REST API (free, no auth). This page covers its npm package (@pipeworx/mcp-wikipedia). ### Is the Wikipedia MCP server safe to use? Wikipedia scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Wikipedia MCP server expose? Wikipedia exposes 5 tools: search_wikipedia, get_article_summary, get_article_sections, get_random_articles, get_article_extract. Their descriptions and schemas cost roughly 1,049 tokens of context every time the server is loaded. ### Is the Wikipedia MCP server still maintained? Wikipedia 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. ### What licence is the Wikipedia MCP server under? Wikipedia declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - npm package: https://www.npmjs.com/package/@pipeworx/mcp-wikipedia - Socket report: https://socket.dev/npm/package/@pipeworx/mcp-wikipedia - Repository: https://github.com/pipeworx-io/mcp-wikipedia - Website: https://pipeworx.io/packs/wikipedia - Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-wikipedia/pipeworx-mcp-wikipedia.xml - Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-wikipedia/pipeworx-mcp-wikipedia.json - HTML version of this page: https://verifymcp.io/servers/pipeworx-io-wikipedia/pipeworx-mcp-wikipedia