# Wikimedia Rest (npm · @pipeworx/mcp-wikimedia-rest)

Wikimedia REST API v1 MCP.

- Trust score: 81/100 (high trust)
- Change this week: +4
- 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-wikimedia-rest/wikimedia-rest-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-wikimedia-rest/wikimedia-rest-mcp)
- npm · `@pipeworx/mcp-wikimedia-rest`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-wikimedia-rest/pipeworx-mcp-wikimedia-rest.md), [page](https://verifymcp.io/servers/pipeworx-io-wikimedia-rest/pipeworx-mcp-wikimedia-rest)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-wikimedia-rest`
- 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-wikimedia-rest).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1086 tokens (~98/item across 11 items; 11 tools + 0 resources), lean.
  - 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**: 70/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 11% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 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.

### Claude

```bash
claude mcp add pipeworx-io-wikimedia-rest -- npx -y @pipeworx/mcp-wikimedia-rest
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-wikimedia-rest": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-wikimedia-rest"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-wikimedia-rest": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-wikimedia-rest"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-wikimedia-rest -- npx -y @pipeworx/mcp-wikimedia-rest
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-wikimedia-rest": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-wikimedia-rest"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-wikimedia-rest --command npx --arg -y --arg @pipeworx/mcp-wikimedia-rest
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-wikimedia-rest:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-wikimedia-rest"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-wikimedia-rest": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-wikimedia-rest"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-wikimedia-rest -t stdio -c npx -a -y @pipeworx/mcp-wikimedia-rest
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-wikimedia-rest": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-wikimedia-rest"
      ]
    }
  }
}
```

## 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-05 (score 81, +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.

### 2026-11-03 (score 80, +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.

### 2026-11-01 (score 79, +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.

### 2026-10-30 (score 78, +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.

### 2026-10-29 (score 77)

First indexed and scored.

## MCP tools (11)

### `page_summary` (~206 tokens)

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

Input parameters:

- `lang` (string): Language code. Default "en". Examples: "es", "fr", "de", "ja".
- `project` (string): Wikimedia project. Default "wikipedia". Other: "wiktionary", "wikiquote", "wikibooks", etc.
- `title` (string, required): Wikipedia article title, e.g. "Albert Einstein", "Python (programming language)", "World War II".

### `page_html` (~79 tokens)

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.

Input parameters:

- `lang` (string)
- `project` (string)
- `title` (string, required)

### `page_metadata` (~72 tokens)

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.

Input parameters:

- `lang` (string)
- `project` (string)
- `title` (string, required)

### `page_references` (~71 tokens)

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.

Input parameters:

- `lang` (string)
- `project` (string)
- `title` (string, required)

### `page_media` (~73 tokens)

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.

Input parameters:

- `lang` (string)
- `project` (string)
- `title` (string, required)

### `page_related` (~78 tokens)

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

Input parameters:

- `lang` (string)
- `project` (string)
- `title` (string, required)

### `page_revisions` (~70 tokens)

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.

Input parameters:

- `lang` (string)
- `project` (string)
- `title` (string, required)

### `page_pdf` (~75 tokens)

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.

Input parameters:

- `lang` (string)
- `project` (string)
- `title` (string, required)

### `featured` (~100 tokens)

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.

Input parameters:

- `day` (number, required)
- `lang` (string)
- `month` (number, required)
- `project` (string)
- `year` (number, required)

### `onthisday` (~145 tokens)

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

Input parameters:

- `day` (number, required)
- `lang` (string)
- `month` (number, required)
- `project` (string)
- `type` (string, required): One of "all", "births", "deaths", "events", "holidays", "selected".

### `random` (~62 tokens)

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.

Input parameters:

- `lang` (string)
- `project` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-wikimedia-rest/pipeworx-mcp-wikimedia-rest#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77

## Common questions

### 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.

### What did VerifyMCP test on the Wikimedia Rest MCP server?

VerifyMCP ran 16 checks on Wikimedia Rest, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-wikimedia-rest
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-wikimedia-rest
- Repository: https://github.com/pipeworx-io/mcp-wikimedia-rest
- Website: https://pipeworx.io/packs/wikimedia-rest
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-wikimedia-rest/pipeworx-mcp-wikimedia-rest.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-wikimedia-rest/pipeworx-mcp-wikimedia-rest/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-wikimedia-rest/pipeworx-mcp-wikimedia-rest.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-wikimedia-rest/pipeworx-mcp-wikimedia-rest