Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Wikidata

NPM · @PIPEWORX/MCP-WIKIDATA · 2 COMPONENTS

Wikidata MCP — wraps Wikidata API (wikidata.org/w/api.php)

+3 this week 82 Trust /100

Last scanned (3 hours ago)

Scores higher than 72% of npm servers

Category Education and Research

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-wikidata). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1500 tokens (~300/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 79

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-wikidata@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-wikidata
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-wikidata/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3561097139
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:b529dc373727529f3f3da5a4fd9262f062cef55f4f54e713112bdc25b7118517859a438e5c480f764e1d65ed4ebee30d05a90005679d09810d39e637f

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~1,447 tokens

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 →

Tool Tokens
get_entities ~358

Batch version of get_entity — resolve up to 50 Wikidata Q-ids in ONE call instead of looping single get_entity calls. Same fields as get_entity per entity (labels, descriptions, aliases, claims, sitelinks, revision info), keyed by Q-id. Any id that does not resolve (bad format, deleted, or genuinely unknown) is reported in "not_found" rather than failing the whole batch — the other ids still resolve. Pass "language" (comma/pipe-joined for several) the same as get_entity to get multilingual labels for every entity in the batch.

NameTypeReqDescription
ids–yesWikidata Q-ids to resolve, up to 50 — either an array of strings (e.g. ["Q162887","Q1326165","Q3493773"]) or a single comma/pipe-joined string (e.g. "Q162887,Q1326165,Q3493773").
languagestring–Language code(s) for labels/descriptions/aliases — a single code (e.g. "ka") or a comma/pipe-joined list to compare several at once (e.g. "ka,ru,en"), which returns every requested language's label s…

No output schema declared.

No examples provided.

get_entity ~320

Get full Wikidata entity by ID (e.g., "Q42" for Douglas Adams, "Q5" for human, "Q1764" for Budapest). Returns labels, descriptions, aliases, claims/statements (properties and values), sitelinks, and the revision the data came from — lastrevid plus the modified timestamp — so live statements can be pinned to a specific edit. Pass "language" (comma/pipe-joined for several) to get labels/descriptions in languages other than English, side by side. For checking several ids at once, use get_entities instead of looping this.

NameTypeReqDescription
idstringyesWikidata entity ID (e.g., "Q42", "Q937", "P31")
languagestring–Language code(s) for labels/descriptions/aliases — a single code (e.g. "ka") or a comma/pipe-joined list to compare several at once (e.g. "ka,ru,en"), which returns every requested language's label s…

No output schema declared.

No examples provided.

get_wikidata_facts ~355

Structured facts about a Wikidata entity in HUMAN-READABLE form — property names and values resolved to labels, not raw P/Q codes. PREFER OVER get_entity for "what is X's <attribute>", "facts about X", "X's date of birth / capital / population". E.g. Q42 (Douglas Adams) -> {"date of birth":["1952-03-11..."],"occupation":["writer",...],"place of birth":["Cambridge"]}. Also returns lastrevid and modified, the revision these statements were read at, for questions asking about an item's state after its latest edit. Pass "language" (comma/pipe-joined for several) for facts and labels in languages other than English. Pass a Q-id from search_entities.

NameTypeReqDescription
idstringyesWikidata entity Q-id (e.g. "Q42"). Find it with search_entities.
languagestring–Language code(s) for labels/descriptions/aliases — a single code (e.g. "ka") or a comma/pipe-joined list to compare several at once (e.g. "ka,ru,en"), which returns every requested language's label s…

No output schema declared.

No examples provided.

search_entities ~126

Search Wikidata entities by label or alias (e.g., "Albert Einstein", "Python programming language", "Tokyo"). Returns entity IDs, labels, descriptions, and aliases. Useful for finding the Wikidata ID of any concept.

NameTypeReqDescription
languagestring–Language code for labels (default "en"). E.g., "fr", "de", "ja"
limitnumber–Max results to return (1-50, default 10)
querystringyesSearch query (e.g., "Marie Curie", "Bitcoin", "Great Wall of China")

No output schema declared.

No examples provided.

wikidata_recent_changes ~288

Newest items created or edited on Wikidata right now, from the live MediaWiki recent-changes feed. Answers "which Wikidata item was created most recently", "what QIDs were created today", "what changed on Wikidata in the last hour", "recent edits to Wikidata items". Returns each change newest-first with its Q-id, revision id, previous revision id, UTC timestamp, editing user, edit comment and byte size, plus a cursor for paging further back.

NameTypeReqDescription
cursorstring–Continue token from a previous call's "cursor" field, to page further back in time.
limitnumber–Max changes to return (1-50, default 10).
namespacenumber–Wikidata namespace: 0 = items/Q-ids (default), 120 = properties/P-ids, 146 = lexemes.
sincestring–Stop at this UTC timestamp, ISO 8601 (e.g. "2026-08-22T00:00:00Z"). Listing runs newest-first back to this point.
typestring–Which changes to list: "new" for freshly created items (default), "edit" for edits to existing items, "all" for both.
userstring–Only changes made by this Wikidata username (e.g. "Dsp13").

No output schema declared.

No examples provided.

Install

How do I install the Wikidata MCP server?

Wikidata runs locally as an npm package, launched with npx -y @pipeworx/mcp-wikidata. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-wikidata

# add to Claude Code
claude mcp add pipeworx-io-wikidata -- npx -y @pipeworx/mcp-wikidata
Common questions

What is the Wikidata MCP server?

Wikidata is an MCP server listed in the public MCP registry as io.github.pipeworx-io/wikidata. Wikidata MCP, wraps Wikidata API (wikidata.org/w/api.php). This page covers its npm package (@pipeworx/mcp-wikidata).

Is the Wikidata MCP server safe to use?

Wikidata scores 82 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 Wikidata MCP server expose?

Wikidata exposes 5 tools: search_entities, get_entity, get_entities, get_wikidata_facts, wikidata_recent_changes. Their descriptions and schemas cost roughly 1,447 tokens of context every time the server is loaded.

Is the Wikidata MCP server still maintained?

Wikidata 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 Wikidata MCP server under?

Wikidata declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.