Wikimedia Rest
NPM · @PIPEWORX/MCP-WIKIMEDIA-REST · 2 COMPONENTS
Wikimedia REST API v1 MCP.
Available components
Last scanned (14 hours ago)
Scores higher than 69% of npm servers
Category Search and Retrieval
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-wikimedia-rest). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1086 tokens (~98/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 11% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 77
First indexed and scored.
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 · Analysed npm/@pipeworx/mcp-wikimedia-rest@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-wikimedia-rest |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-wikimedia-rest/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3561105504 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:70a4186a54a7925062e6f0fcd0be7d37afa98f5aa68283c165f2194a32ff8679feb900ffc8f8614129ae0953c228debfd9bcf872fcc18837244096eb0 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
featured ~100
Wikipedia's "today's featured" content for a specific date — featured article, most-read, picture of the day, on-this-day events. Use for "what's on Wikipedia today", "featured article on 2026-05-21", or to seed daily-roundup content.
| Name | Type | Req | Description |
|---|---|---|---|
| day | number | yes | – |
| lang | string | – | – |
| month | number | yes | – |
| project | string | – | – |
| year | number | yes | – |
No output schema declared.
No examples provided.
onthisday ~145
"What happened on this day" / "events that happened on May 21" / "historical events on a date" — births, deaths, events, holidays, and selected occurrences from history for any month+day. Pass type="all" for everything, or filter to "births" / "deaths" / "events" / "holidays" / "selected".
| Name | Type | Req | Description |
|---|---|---|---|
| day | number | yes | – |
| lang | string | – | – |
| month | number | yes | – |
| project | string | – | – |
| type | string | yes | One of "all", "births", "deaths", "events", "holidays", "selected". |
No output schema declared.
No examples provided.
page_html ~79
Full Wikipedia article HTML (Parsoid output) — use when page_summary's extract isn't enough and you need the complete article body, infoboxes, tables, and embedded content. Returns rendered HTML you can scrape/parse for full-text questions.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| project | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
page_media ~73
Images, videos, and other media embedded in a Wikipedia article. Use for "show me pictures of X", "what images are on the X Wikipedia page", or to find Commons-hosted media tied to a topic.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| project | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
page_metadata ~72
Wikipedia article metadata: categories, inter-language links, content_urls (desktop/mobile), page_id, and namespace (ns). Use to get canonical IDs, discover language versions, or check which categories an article belongs to.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| project | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
page_pdf ~75
Returns a Mapbox static-tile image URL for a Wikipedia article as a PDF download. Caller fetches the binary PDF directly from the returned URL via browser or curl. Pass title plus optional project/lang for non-English Wikimedia projects.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| project | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
page_references ~71
Citations / references / sources cited by a Wikipedia article. Use for "what sources back the claim that…", "where does Wikipedia cite this from", or to harvest authoritative external links on a topic.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| project | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
page_related ~78
"What's related to X" / "see also" — Wikipedia's related-articles graph for any topic. Returns up to ~12 related pages with summaries. Use for "what should I read next", topic exploration, or finding adjacent concepts.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| project | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
page_revisions ~70
Recent edit history for a Wikipedia article — editor usernames, timestamps, revision sizes, and edit comments. Use to check when an article was last updated, spot recent disputes, or assess reliability before quoting.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| project | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
page_summary ~206
"What is X" / "who is X" / "tell me about X" / "Wikipedia summary of X" / "biography of X" / "history of X" — fetches the Wikipedia article extract (title, description, thumbnail, lead-paragraph extract) for any topic, person, place, event, or concept. Use whenever an agent needs a quick encyclopedic reference. Defaults to en.wikipedia.org; pass project/lang for other Wikimedia projects or languages. Example: page_summary({ title: "Albert Einstein" }).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language code. Default "en". Examples: "es", "fr", "de", "ja". |
| project | string | – | Wikimedia project. Default "wikipedia". Other: "wiktionary", "wikiquote", "wikibooks", etc. |
| title | string | yes | Wikipedia article title, e.g. "Albert Einstein", "Python (programming language)", "World War II". |
No output schema declared.
No examples provided.
random ~62
Random Wikipedia article summary — pick a random article from the encyclopedia. Use for "give me a random Wikipedia article", "surprise me", or seeding exploration. Returns the same shape as page_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| project | string | – | – |
No output schema declared.
No examples provided.
How do I install the Wikimedia Rest MCP server?
Wikimedia Rest runs locally as an npm package, launched with npx -y @pipeworx/mcp-wikimedia-rest. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-wikimedia-rest
claude mcp add pipeworx-io-wikimedia-rest -- npx -y @pipeworx/mcp-wikimedia-rest
What is the Wikimedia Rest MCP server?
Wikimedia Rest is an MCP server listed in the public MCP registry as io.github.pipeworx-io/wikimedia-rest. Wikimedia REST API v1 MCP. This page covers its npm package (@pipeworx/mcp-wikimedia-rest).
Is the Wikimedia Rest MCP server safe to use?
Wikimedia Rest scores 81 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 Wikimedia Rest MCP server expose?
Wikimedia Rest exposes 11 tools: page_summary, page_html, page_metadata, page_references, page_media, and 6 more. Their descriptions and schemas cost roughly 1,031 tokens of context every time the server is loaded.
Is the Wikimedia Rest MCP server still maintained?
Wikimedia Rest 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 Wikimedia Rest MCP server under?
Wikimedia Rest declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.