Bragproof

← Reports

@cyanheads/wikidata-mcp-server

Starts with no setup0.4.0npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Contacts while installing and starting: nothing

7tools listed
0hosts contacted
0files written
0.3 sto start
36dependencies

Its tool definitions changed since version 0.3.0. If you approved the earlier ones, read them again.

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @cyanheads/wikidata-mcp-server@0.4.0

Installing a package runs its code. Use a sandbox for anything you have not read.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

wikidata_search_entities query, type, language, limit, offset
Search Wikidata for items or properties by text query. Returns QIDs or PIDs with labels, descriptions, and match metadata indicating whether the hit was on a label or alias. Use type="item" for real-world concepts (people, places, works) and type="property" to find predicate P-IDs. The endpoint returns no total count: page by sending each page's nextOffset as offset until a page returns no results or no nextOffset. Only the first 10,000 results are reachable.
wikidata_get_entity id, fields, languages
Fetch a Wikidata entity (item or property) by QID or PID. The fields parameter narrows the upstream fetch, not just the response — asking for labels alone costs a fraction of the whole entity, so name the fields you need. Omit fields for all data; a well-connected item is large enough to overflow, and an oversized entity returns kind: "outline" — the field categories with their byte sizes — instead of the data. Follow its retrieval_notice literally rather than picking from sections yourself — it names a fields set already measured to fit, since category sizes are additive and requesting them all would overflow again; for a category too large to deliver whole (statements or sitelinks on a major item) it names the sibling tool that can narrow it. Q-IDs (e.g. Q76) fetch items; P-IDs (e.g. P31) fetch properties from the correct endpoint automatically. Use wikidata_get_statements for deep claim traversal with label resolution, and whenever an entity's statements are large — its properties parameter selects individual P-IDs, granularity fields does not carry.
wikidata_get_labels ids, languages
Resolve QIDs or PIDs to their human-readable labels and descriptions, with no claim data. Resolves up to 500 distinct IDs per call, batched automatically; distinct IDs past the first 500 come back in deferredIds to send in a follow-up call. Accepts bare IDs (Q76), entity URIs (http://www.wikidata.org/entity/Q76), and wd:Q76 — the forms wikidata_sparql_query returns — so its results can be humanized as they are.
wikidata_get_statements id, properties, language, resolve_labels, rank, limit, offset
Fetch property claims for a Wikidata entity with qualifier and reference detail. Item QIDs and quantity units — in values, qualifiers, and references — are resolved to human-readable labels by default, and every P-ID the statements name comes back labelled in propertyLabels. Each property returns up to limit statements (default 10) starting at offset, in upstream order; propertyTotals counts every statement each property holds, and nextOffset, present while any property holds more, continues every property at once. Use the properties parameter to fetch only specific P-IDs — omitting it returns every property, and a well-connected item (a country, a major city) carries hundreds of them: more than fits inline. A page of several properties over 24,000 bytes before labels comes back as kind: "outline" — every P-ID on the page with its byte size, largest first — instead of the statements; re-call with the same id, limit, offset, and rank plus properties:[...] naming P-IDs whose sizes sum to 24,000 or less (the retrieval_notice names one such set). Labels are added after that check, so a returned page can run past 24,000 bytes by their size, and a single property is never outlined: it returns its window whatever the size. Designed for fact verification: "what does Wikidata say about this entity's {property}?". For a current value, rank: "best" keeps each property's preferred statements, or its normal ones when none is preferred, and never deprecated ones — the statements SPARQL's wdt: reads. Check qualifiers and references for temporal scope and evidence.
wikidata_get_sitelinks id, sites, wikis_only
Fetch Wikipedia and other Wikimedia project article URLs for a Wikidata item. A sitelink maps a site code (e.g., "enwiki", "commonswiki") to an article title and URL. Major items can have 300+ sitelinks across languages. Use sites to filter to specific site codes, or wikis_only to return only Wikipedia editions. Only Q-IDs (items) have sitelinks — properties (P-IDs) do not.
wikidata_sparql_query query, language, timeout
Execute a SPARQL SELECT query against the Wikidata Query Service. Full graph power: multi-hop traversals, aggregations, subqueries, OPTIONAL, FILTER, UNION, BIND. Standard Wikidata prefixes (wd:, wdt:, p:, ps:, pq:, wikibase:, bd:, rdfs:, schema:) are auto-injected. The wikibase:label SERVICE is also auto-injected when the query references a ?<var>Label, ?<var>Description, or ?<var>AltLabel variable and declares no label SERVICE of its own — so you can use ?itemLabel without writing the boilerplate. Scholarly articles, and every triple they own (DOI, PMID, authorship), live in a separate graph reachable only inside SERVICE wdsubgraph:scholarly_articles { … } (wdsubgraph: is predeclared). The injected label SERVICE runs on the main graph, so read a scholarly article's label inside that block, with BIND(?paperLabel AS ?paperLabel) and a label SERVICE there; a query that writes a label SERVICE gets none injected, so add a top-level one for main-graph labels. Hard server timeout is 60s; use LIMIT to keep queries fast. Each call returns at most 4,000 rows; a larger result returns its first rows with truncated, shown, and cap in place of totalCount — narrow the WHERE clause or aggregate in the query, or, for a result not much larger than that, page with ORDER BY plus LIMIT and OFFSET. Bindings use the SPARQL 1.1 JSON format: each value is { type, value, "xml:lang"?, datatype? }. Use wikidata_get_labels to humanize QID results from this tool.
wikidata_resolve_external_id property, value, language
Look up a Wikidata entity by an external identifier such as a DOI, PubMed ID, ORCID iD, OpenAlex ID, or IMDb ID. Returns match=<entity> on success, match=null when not found, and match=null with multipleMatches populated when a Wikidata data integrity issue causes more than one entity to claim the same external ID. The identifier matches through statements of every rank — entities holding it at best rank first, then at another non-deprecated rank, then deprecated — and each match reports the rank of the statement it was found through. The lookup searches both the main Wikidata graph and the scholarly-article graph, where scholarly articles and the DOIs and PubMed IDs on them live; when one does not answer, the result covers the other, with unavailableGraphs naming the one missed. Common cross-server join use cases: CrossRef DOI → Wikidata paper QID (P356), PubMed PMID → Wikidata paper QID (P698), ORCID → author QID (P496), OpenAlex ID → entity QID (P10283). The property must be one whose Wikidata data type is external-id — item-valued or media properties (e.g. P31 instance-of, P18 image) are rejected rather than returning an empty match. Known value forms are normalized automatically. Surrounding whitespace is trimmed. Resolver prefixes are stripped, in any case and with https://, http://, or no scheme: doi.org/, dx.doi.org/, www.doi.org/, and doi: for DOIs; pubmed.ncbi.nlm.nih.gov/, www.ncbi.nlm.nih.gov/pubmed/, and PMID: for PubMed IDs; orcid.org/, www.orcid.org/, and orcid: for ORCID iDs; openalex.org/ and api.openalex.org/ with an optional entity path for OpenAlex IDs; and the title, name, company, and event pages of imdb.com, www.imdb.com, and m.imdb.com for IMDb IDs. DOIs are uppercased, ORCID iDs regrouped with hyphens and an uppercase X check character, and IMDb IDs lowercased. An OpenAlex ID is stored with its entity letter in either case, so it is tried as given and then with that letter in the other case.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseApache-2.0
Needsnode >=24.0.0
Sourcegithub.com/cyanheads/wikidata-mcp-server
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-44n4zh/Hv2O6I4DHB1IlDHok0vMn4Hyy1JbpgoFLdsqKZPPZN0JJ7Rcu4j2nGRHH5gmONMJQs1/TDqd+WzjZ7g==

Versions reported

VersionRunResultTools
0.4.02026-11-16Starts with no setup7
0.3.02026-11-12Starts with no setup7

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@cyanheads/wikidata-mcp-server.svg)](https://bragproof.smaverk.com/r/%40cyanheads/wikidata-mcp-server)

New version out? Ask for a fresh report.