# Wikimedia Enterprise docs (remote · enterprise.wikimedia.com)

Wikimedia Enterprise API docs: search the guides, read every endpoint. Read-only, no account needed.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `enterprise.wikimedia.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-wikimedia-enterprise-docs/enterprise.md), [page](https://verifymcp.io/servers/com-wikimedia-enterprise-docs/enterprise)

## Channel facts

- Endpoint: `https://enterprise.wikimedia.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1153 tokens (~57/item across 20 items; 4 tools + 16 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 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 current MCP spec version (2026-07-28).

## Install

### How do I install the Wikimedia Enterprise docs MCP server?

Wikimedia Enterprise docs is a hosted endpoint at https://enterprise.wikimedia.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.

### Claude

```bash
claude mcp add --transport http com-wikimedia-enterprise-docs 'https://enterprise.wikimedia.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-wikimedia-enterprise-docs": {
      "url": "https://enterprise.wikimedia.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-wikimedia-enterprise-docs": {
      "type": "http",
      "url": "https://enterprise.wikimedia.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-wikimedia-enterprise-docs]
url = "https://enterprise.wikimedia.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-wikimedia-enterprise-docs": {
      "type": "remote",
      "url": "https://enterprise.wikimedia.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-wikimedia-enterprise-docs --url 'https://enterprise.wikimedia.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-wikimedia-enterprise-docs:
    url: "https://enterprise.wikimedia.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-wikimedia-enterprise-docs": {
      "Transport": "http",
      "Url": "https://enterprise.wikimedia.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-wikimedia-enterprise-docs -t streamable-http -u 'https://enterprise.wikimedia.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-wikimedia-enterprise-docs": {
      "type": "http",
      "url": "https://enterprise.wikimedia.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-19 (score 71, +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-09-18 (score 70, 0)

- [security] Tool “fetch” rewrote its description, which is the text the model reads
- [security] Tool “search” rewrote its description, which is the text the model reads
- [functional] New resource “docs-pricing”
- [functional] Server version: 1.1.0 → 1.1.2
- [functional] Server version: 1.0.8 → 1.1.0

### 2026-09-17 (score 70, +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-09-16 (score 69, 0)

- [functional] Server version: 1.0.5 → 1.0.8

### 2026-09-15 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.2 → 1.0.5

### 2026-09-14 (score 68)

First indexed and scored.

## MCP tools (4)

### `search` (~145 tokens)

Search the Wikimedia Enterprise docs

Full-text search over the Wikimedia Enterprise API documentation: guide sections, the changelog, pricing, endpoints and response models. Exact tokens work best (a field name such as `reference_risk_score`, a status code such as `429`, or a path such as `/v2/snapshots/{identifier}/download`); plain questions work too. Returns ids to pass to `fetch`.

Input parameters:

- `limit` (integer)
- `query` (string, required): What to look for. Field names, endpoint paths, status codes and plain questions all work.
- `scope` (string): `docs` for the prose guides, `reference` for endpoints and models, `all` for both.

Output parameters:

- `results` (array)

### `fetch` (~95 tokens)

Fetch a docs page, endpoint or model

Full text for one id from `search`: `docs/<slug>` (a guide, as markdown; a `#section` suffix is accepted; `docs/changelog` is the release notes and `docs/pricing` the plans), `op/<operationId>` (one endpoint rendered from the OpenAPI definition) or `schema/<name>` (one response model).

Input parameters:

- `id` (string, required): An id returned by `search`.

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

### `list_endpoints` (~108 tokens)

List API endpoints

Every endpoint in the Wikimedia Enterprise OpenAPI definition, in reference order, with its technical title, its plain-language line and a link into the reference. Filter with a tag: authentication, codes, languages, projects, namespaces, batches, wikidata-batches, snapshots, wikidata-snapshots, structured-snapshots, articles, structured-contents, wikidata, realtime-articles, realtime-wikidata.

Input parameters:

- `tag` (string): An OpenAPI tag; omit for all endpoints.

Output parameters:

- `endpoints` (array)

### `get_endpoint` (~111 tokens)

Get one endpoint

The exact request and response shape of one endpoint, dereferenced from the OpenAPI definition (the source of truth), as structured JSON plus a markdown rendering. Identify it by `operationId`, or by `method` and `path`.

Input parameters:

- `method` (string): GET, HEAD or POST
- `operationId` (string): e.g. `getSnapshotsByIdentifier`
- `path` (string): Templated path as written in the reference, e.g. `/v2/snapshots/{identifier}`

Output parameters:

- `method` (string)
- `operation` (object)
- `operationId` (string)
- `path` (string)
- `tag` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-wikimedia-enterprise-docs/enterprise#diagnostics

## Score history

- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 68

## Common questions

### What is the Wikimedia Enterprise docs MCP server?

Wikimedia Enterprise docs is an MCP server listed in the public MCP registry as com.wikimedia.enterprise/docs. Wikimedia Enterprise API docs: search the guides, read every endpoint. Read-only, no account needed. This page covers its hosted endpoint (https://enterprise.wikimedia.com/mcp).

### Is the Wikimedia Enterprise docs MCP server safe to use?

Wikimedia Enterprise docs scores 71 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 Wikimedia Enterprise docs MCP server expose?

Wikimedia Enterprise docs exposes 4 tools: search, fetch, list_endpoints, get_endpoint. Their descriptions and schemas cost roughly 459 tokens of context every time the server is loaded.

### Does the Wikimedia Enterprise docs MCP server require authentication?

No. We connected to Wikimedia Enterprise docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Wikimedia Enterprise docs MCP server still maintained?

Wikimedia Enterprise docs is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://enterprise.wikimedia.com/mcp
- Website: https://enterprise.wikimedia.com/docs/agents/
- Changelog RSS feed: https://verifymcp.io/servers/com-wikimedia-enterprise-docs/enterprise.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-wikimedia-enterprise-docs/enterprise.json
- HTML version of this page: https://verifymcp.io/servers/com-wikimedia-enterprise-docs/enterprise