# Wikimedia Enterprise docs

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

- name: com.wikimedia.enterprise/docs
- version: 1.1.14
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 94/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.wikimedia.enterprise%2Fdocs
- tools: https://api.protogrid.dev/v1/servers/com.wikimedia.enterprise%2Fdocs/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-1d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 94/100 (strong)

### protocol: 100 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- pass `protocol.list_ttl`: tool list is cacheable (ttlMs 3600000)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 4 of 4 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: fetch (destructiveHint); list_endpoints (destructiveHint); get_endpoint (destructiveHint); …
- pass `tools.token_cost`: about 696 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 4, about 696 tokens to load them all
- tool set hash: 70b1c589f8cec60ebed3aa96ea2985b0
- badge: [![protogrid quality](https://protogrid.dev/badge/com.wikimedia.enterprise/docs.svg)](https://protogrid.dev/servers/com.wikimedia.enterprise/docs)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://enterprise.wikimedia.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (4)

- `fetch`: 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).
- `get_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`.
- `list_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.
- `search`: 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`.