Wikimedia Enterprise docs
REMOTE · ENTERPRISE.WIKIMEDIA.COM · SCANNED SEP 20
Wikimedia Enterprise API docs: search the guides, read every endpoint. Read-only, no account needed.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1153 tokens (~57/item across 20 items; 4 tools + 16 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · enterprise.wikimedia.com
claude mcp add --transport http com-wikimedia-enterprise-docs 'https://enterprise.wikimedia.com/mcp'
{
"mcpServers": {
"com-wikimedia-enterprise-docs": {
"url": "https://enterprise.wikimedia.com/mcp"
}
}
} {
"servers": {
"com-wikimedia-enterprise-docs": {
"type": "http",
"url": "https://enterprise.wikimedia.com/mcp"
}
}
} [mcp_servers.com-wikimedia-enterprise-docs] url = "https://enterprise.wikimedia.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-wikimedia-enterprise-docs": {
"type": "remote",
"url": "https://enterprise.wikimedia.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-wikimedia-enterprise-docs --url 'https://enterprise.wikimedia.com/mcp' --transport streamable-http
mcp_servers:
com-wikimedia-enterprise-docs:
url: "https://enterprise.wikimedia.com/mcp" {
"McpServers": {
"com-wikimedia-enterprise-docs": {
"Transport": "http",
"Url": "https://enterprise.wikimedia.com/mcp"
}
}
} assistant mcp add com-wikimedia-enterprise-docs -t streamable-http -u 'https://enterprise.wikimedia.com/mcp'
{
"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.
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.
- 19 Sept 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.
- 18 Sept 26 0
- 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 security
- New resource “docs-pricing” functional
- Server version: 1.1.0 → 1.1.2 functional
- Server version: 1.0.8 → 1.1.0 functional
- 17 Sept 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.
- 16 Sept 26 0
- Server version: 1.0.5 → 1.0.8 functional
- 15 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.2 → 1.0.5 functional
- 14 Sept 26 68
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 20 Sept 2026 · Probed https://enterprise.wikimedia.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=enterprise.wikimedia.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 14 Sept 2026 | 30 Mar 2027 | RSA 2048 | SHA256-RSA | 5d22861b3abd23cb1cad32f8f3a05db |
| SANs: enterprise.wikimedia.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of enterprise.wikimedia.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| wikimedia.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' https://cdn.usefathom.com 'sha256-Cai4UlFF9qPYFZTSBWo9eZSpnbBMHe3yGEjAmVzSsJg=' 'sha256-Kt4uTNYfxI9d3T73nZIUGKIgfGfGvnJxjqPXC1HjbeQ=' 'sha256-QzWFZi+FLIx23tnm9SBU4aEgx4x8DsuASP07mfqol/c=' 'sha256-UAnd7MEQKcA4FUGEjo1/lh5mUWlj+vq9uhGHf/vfKXg=' 'sha256-Ya0pUYrC7nM5Cn/056TyVuEiz6dFGrzmkWzgON0pF0U=' 'sha256-ePtmoC2w0wOKHKnEF/XaQ/u6I074ltaMDE/yaMkjHJY=' 'sha256-mVQGGcUiD0kgh1X6V3v7csnyYMe0y9uy8gAguaJCaoc=' 'sha256-noz7GF4/P88UZRk9gPH0/L5g6fcNy9QRRAdJdVnRyzo='; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://cdn.usefathom.com; font-src 'self'; connect-src 'self' https://cdn.usefathom.com; media-src 'self'; object-src 'none'; frame-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://enterprise.wikimedia.com/mcp | Verified | 200 | |
| http (plaintext) | http://enterprise.wikimedia.com/mcp | HTTPS enforced | 301 | https://enterprise.wikimedia.com/mcp |
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 →
fetch Fetch a docs page, endpoint or model ~95
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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | An id returned by `search`. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_endpoint Get one endpoint ~111
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| 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}` |
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | – |
| operation | object | yes | – |
| operationId | string | yes | – |
| path | string | yes | – |
| tag | string | yes | – |
| url | string | yes | – |
No examples provided.
list_endpoints List API endpoints ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tag | string | – | An OpenAPI tag; omit for all endpoints. |
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | array | yes | – |
No examples provided.
search Search the Wikimedia Enterprise docs ~145
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
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.