Wikidata + Google Knowledge Graph MCP
REMOTE · WIKIDATA-KNOWLEDGE-MCP.REVANALEX.WORKERS.DEV · 2 COMPONENTS
Read-only Wikidata tools and identity evidence. Local optional Google KG; bounded public remote.
Last scanned (5 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability57
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 980 tokens (~122/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “kg_audit_identity” rewrote its description, which is the text the model reads security
- Tool “kg_related” rewrote its description, which is the text the model reads security
- Tool “kg_resolve” rewrote its description, which is the text the model reads security
- Tool “kg_search” rewrote its description, which is the text the model reads security
- Tool “kg_entity” rewrote its description, which is the text the model reads security
- Tool “kg_discover_identity” rewrote its description, which is the text the model reads security
- Tool “kg_lookup_entities” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
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 · Probed https://wikidata-knowledge-mcp.revanalex.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=revanalex.workers.dev | CN=WE1,O=Google Trust Services,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f6278e9fde34f3121380b63495c75dd1 |
| SANs: revanalex.workers.dev, *.revanalex.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wikidata-knowledge-mcp.revanalex.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wikidata-knowledge-mcp.revanalex.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://wikidata-knowledge-mcp.revanalex.workers.dev/mcp | Inconclusive | 405 |
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 →
kg_audit_identity ~110
Canonical audit of one existing Wikidata QID against one local identity envelope. Returns contradictions, evidence and uncertainty. Provider agreement is not local identity proof. Google crosscheck is disabled remotely. New entities use bounded direct-record admission without recursive content certification. Identity evidence and uncertainty remain separate. Public prose, aliases, external links and media are withheld.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | – |
| google_crosscheck | boolean | – | – |
| max_candidates | integer | – | – |
| refresh | boolean | – | – |
No output schema declared.
No examples provided.
kg_discover_identity ~115
Canonical discovery of one identity from a local evidence envelope. Default 3, maximum 5 candidates. Returns ambiguity and insufficient-evidence states; sameAs candidates are unapproved. Google crosscheck is disabled remotely. New entities use bounded direct-record admission without recursive content certification. Identity evidence and uncertainty remain separate. Public prose, aliases, external links and media are withheld.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | – |
| google_crosscheck | boolean | – | – |
| max_candidates | integer | – | – |
| refresh | boolean | – | – |
No output schema declared.
No examples provided.
kg_entity ~89
Bounded structured facts for one Wikidata QID. Arbitrary source prose, aliases, URLs, media and references are withheld. New entities use bounded direct-record admission without recursive content certification. Identity evidence and uncertainty remain separate. Public prose, aliases, external links and media are withheld.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | – | – | – |
| id | string | yes | – |
| lang | string | – | – |
| props | – | – | – |
No output schema declared.
No examples provided.
kg_lookup_entities ~89
Compact selected Wikidata facts for at most 10 supplied QIDs. Fact lookup does not establish local identity. New entities use bounded direct-record admission without recursive content certification. Identity evidence and uncertainty remain separate. Public prose, aliases, external links and media are withheld.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | – |
| lang | string | – | – |
| qids | array | yes | – |
| refresh | boolean | – | – |
No output schema declared.
No examples provided.
kg_related ~106
Bounded outgoing, inverse or hierarchy relationships for one Wikidata QID. Maximum depth 2 and 10 results. New entities use bounded direct-record admission without recursive content certification. Identity evidence and uncertainty remain separate. Public prose, aliases, external links and media are withheld.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | – | – | – |
| hierarchy | boolean | – | – |
| id | string | yes | – |
| inverse | boolean | – | – |
| lang | string | – | – |
| limit | – | – | – |
| prop | – | – | – |
No output schema declared.
No examples provided.
kg_resolve ~194
Canonical deterministic resolution of one identity from supplied local facts and Wikidata evidence. Returns identity verdicts and reason codes, including uncertainty. Google is disabled remotely. New entities use bounded direct-record admission without recursive content certification. Identity evidence and uncertainty remain separate. Public prose, aliases, external links and media are withheld.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | – |
| affiliation | – | – | – |
| aliases | – | – | – |
| city | – | – | – |
| country | – | – | – |
| creator | – | – | – |
| event_date | – | – | – |
| existing_google_kg_id | – | – | – |
| existing_wikidata_qid | – | – | – |
| explain | boolean | – | – |
| kind | – | – | – |
| lang | string | – | – |
| latitude | – | – | – |
| longitude | – | – | – |
| name | string | yes | – |
| occupation | – | – | – |
| official_url | – | – | – |
| organizer | – | – | – |
| role | – | – | – |
| venue | – | – | – |
| year | – | – | – |
No output schema declared.
No examples provided.
kg_search ~111
Wikidata entity candidates by name, with local place/type filtering. Default 3, maximum 5 candidates. Google and fallback are disabled remotely. New entities use bounded direct-record admission without recursive content certification. Identity evidence and uncertainty remain separate. Public prose, aliases, external links and media are withheld.
| Name | Type | Req | Description |
|---|---|---|---|
| fallback | boolean | – | – |
| lang | string | – | – |
| limit | – | – | – |
| place | – | – | – |
| provider | string | – | – |
| query | string | yes | – |
| type | – | – | – |
No output schema declared.
No examples provided.
kg_status ~32
Public remote provider configuration and operational limits. No external provider calls. Wikidata is available; Google Knowledge Graph is disabled.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Wikidata + Google Knowledge Graph MCP server?
Wikidata + Google Knowledge Graph MCP is a hosted endpoint at https://wikidata-knowledge-mcp.revanalex.workers.dev/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 · wikidata-knowledge-mcp.revanalex.workers.dev
claude mcp add --transport http com-dondego-wikidata-google-knowledge-mcp 'https://wikidata-knowledge-mcp.revanalex.workers.dev/mcp'
What is the Wikidata + Google Knowledge Graph MCP server?
Wikidata + Google Knowledge Graph MCP is listed in the public MCP registry as com.dondego/wikidata-google-knowledge-mcp. Read-only Wikidata tools and identity evidence. Local optional Google KG; bounded public remote. This page covers its hosted endpoint (https://wikidata-knowledge-mcp.revanalex.workers.dev/mcp).
Is the Wikidata + Google Knowledge Graph MCP server safe to use?
Wikidata + Google Knowledge Graph MCP scores 75 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 Wikidata + Google Knowledge Graph MCP server expose?
Wikidata + Google Knowledge Graph MCP exposes 8 tools: kg_search, kg_entity, kg_related, kg_resolve, kg_audit_identity, and 3 more. Their descriptions and schemas cost roughly 846 tokens of context every time the server is loaded.
Does the Wikidata + Google Knowledge Graph MCP server require authentication?
No. We connected to Wikidata + Google Knowledge Graph MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Wikidata + Google Knowledge Graph MCP server still maintained?
Wikidata + Google Knowledge Graph MCP 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.