Wikimedia Enterprise docs MCP server
com.wikimedia.enterprise/docsenterprise.wikimedia.comstreamable-httpv1.2.6Scanned
Wikimedia Enterprise API docs: search the guides, read every endpoint. Read-only, no account needed.
4 tools: 4 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Wikimedia Enterprise docs MCP server can do
The Wikimedia Enterprise docs MCP server is published by enterprise.wikimedia.com, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (fetch).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.2.6.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
fetchFull 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/<…Reads private dataNo findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
What it can reach
- private-dataThe description's first sentence says "doc": it reads documents.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_endpointThe exact request and response shape of one endpoint, dereferenced from the OpenAPI definition (the source of truth), as structured JSON plus a markdown rendering.No findings
Why it is in this group
- The name "get_endpoint" says "get": a word for reading.
Description, as the server wrote it 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`.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_endpointsEvery endpoint in the Wikimedia Enterprise OpenAPI definition, in reference order, with its technical title, its plain-language line and a link into the reference.No findings
Why it is in this group
- The name "list_endpoints" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
searchFull-text search over the Wikimedia Enterprise API documentation: guide sections, the changelog, pricing, endpoints and response models.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it 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`.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:50 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.6. Values in angle brackets are yours to fill in.
claude mcp add --transport http docs https://enterprise.wikimedia.com/mcpclaude mcp add --transport http docs https://enterprise.wikimedia.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__docs__search",
"mcp__docs__fetch",
"mcp__docs__list_endpoints",
"mcp__docs__get_endpoint"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as docs. Review it before you use it.
Capability tags behind 1 rule
- mcp__docs__fetch private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.wikimedia.enterprise/docs/verify?hash=c8442b8d98799c9c4d1a02e29ccca987187e5a44924e63aa3cc6043ebc94deee" | jq -e '.changed == false'Pinned hash c8442b8d9879, from Nov 17, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.wikimedia.enterprise/docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.wikimedia.enterprise/docs)Source: MCP Registry. Synced Nov 17, 2026, 17:17 UTC.
Wikimedia Enterprise docs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Wikimedia Enterprise docs MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Wikimedia Enterprise docs MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Wikimedia Enterprise docs MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Wikimedia Enterprise docs MCP server have?
- 4 tools: 4 read. search, fetch, list_endpoints and get_endpoint.
Does the Wikimedia Enterprise docs MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Wikimedia Enterprise docs MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Wikimedia Enterprise docs MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.