io.github.kuhumcst/dannet
REMOTE · WORDNET.DK
DanNet - Danish WordNet with rich lexical relationships and SPARQL access.
Available components
Last scanned (19 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
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 Security57
- 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 6 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
- 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 Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1682 tokens (~186/item across 9 items; 6 tools + 3 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 Coverage71
- 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
- Structured output schemas are declared (33% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Oct 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Stability: fail → 0.27 functional
- 3 Sept 26 0
- Stability: unverified → fail ▼ security
- Tool “analyze_namespace_usage” was removed ▼ security
- Tool “extract_semantic_data” was removed ▼ security
- Tool “get_cache_stats” was removed ▼ security
- Tool “get_current_dannet_server” was removed ▼ security
- Tool “get_sense_info” was removed ▼ security
- Tool “get_synset_info” was removed ▼ security
- Tool “get_word_info” was removed ▼ security
- Tool “get_word_synonyms” was removed ▼ security
- Tool “switch_dannet_server” was removed ▼ security
- Tool “validate_synset_structure” was removed ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “autocomplete_danish_word” rewrote its description, which is the text the model reads security
- Tool “fetch_ddo_definition” rewrote its description, which is the text the model reads security
- Tool “get_entity_info” rewrote its description, which is the text the model reads security
- Tool “get_word_overview” rewrote its description, which is the text the model reads security
- Tool “get_word_synsets” rewrote its description, which is the text the model reads security
- Tool “sparql_query” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 33% ▼ functional
- MCP protocol: unverified → fail ▼ functional
- “get_word_synsets” added a required parameter “word”, so existing callers break ▼ functional
- “get_word_synsets” dropped the required parameter “query” ▼ functional
- Resource “get_dannet_schema” was removed ▼ functional
- Resource “get_namespace_documentation” was removed ▼ functional
- Resource “get_ontological_types_schema” was removed ▼ functional
- Resource “get_wordnet_schema” was removed ▼ functional
- Resource “list_available_schemas” was removed ▼ functional
- Tool “autocomplete_danish_word” dropped its output schema ▼ functional
- Tool “fetch_ddo_definition” dropped its output schema ▼ functional
- Tool “get_entity_info” dropped its output schema ▼ functional
- Tool “sparql_query” dropped its output schema ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Schema quality: 404 → 186 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Destructive annotations: pass functional
- Schema quality: excellent → good functional
- MCP protocol version: 2025-11-25 → 2025-06-18 functional
- New resource “dannet_schema” functional
- New resource “ontological_types” functional
- New resource “wordnet_schema” functional
- Server version: 1.28.1 → 1.13.1 functional
- “get_entity_info” dropped the optional parameter “namespace” cosmetic
- “get_word_synsets” dropped the optional parameter “language” cosmetic
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 21 Nov 2026 · Probed https://wordnet.dk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wordnet.dk | CN=YE1,O=Let's Encrypt,C=US | 18 Nov 2026 | 16 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6838fc2aedb4c96e64d674b33643ab001ff |
| SANs: wordnet.dk | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wordnet.dk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dk. | DS published | 16874 | 13 | Verified |
| wordnet.dk. | No DS | 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://wordnet.dk/mcp | Verified | 200 | |
| http (plaintext) | http://wordnet.dk/mcp | HTTPS enforced | 308 | https://wordnet.dk/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 →
autocomplete_danish_word ~78
Danish words starting with `prefix` (at least 3 characters), at most `max_results`, as {"autocompletions": [...]} where lemmas are plain strings and inflected forms of a matching lemma are [lemma, form] pairs.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | – |
| prefix | string | yes | – |
No output schema declared.
No examples provided.
fetch_ddo_definition ~92
The full definitions of `synset_id` from DDO (ordnet.dk), where DanNet's own skos:definition may be truncated. Follows the dns:source of each sense. Returns the DanNet definition, the DDO definitions found and any errors; DDO and DanNet have drifted apart, so some source URLs no longer resolve.
| Name | Type | Req | Description |
|---|---|---|---|
| synset_id | string | yes | – |
No output schema declared.
No examples provided.
get_entity_info ~127
Full JSON-LD of a DanNet resource: a synset ("synset-3047"), word ("word-11021628") or sense ("sense-21033604"), given bare or prefixed ("dn:synset-3047"), or an external resource by prefix ("ili:i76470", "ontolex:LexicalConcept"). Properties use prefixed names (wn:hypernym, ontolex:isEvokedBy, ...); language-tagged values are {"@value": ..., "@language": ...}.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
No output schema declared.
No examples provided.
get_word_overview ~95
Every sense of the Danish `word` in one call: a list with synset_id, label, definition, lexfile, ontological_types, synonyms (words sharing the synset) and hypernym ({synset_id, label} or null) per synset. Only synsets where the word itself has a sense count, not multi-word expressions containing it.
| Name | Type | Req | Description |
|---|---|---|---|
| word | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_word_synsets ~94
The synsets (senses) of the Danish `word`, as JSON-LD entries with @id (e.g. "dn:synset-3047" for get_entity_info), skos:definition, dns:ontologicalType and wn:lexfile. A word with a single synset gives that synset's full JSON-LD as the only entry.
| Name | Type | Req | Description |
|---|---|---|---|
| word | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
sparql_query ~655
Run a SPARQL SELECT `query` against DanNet and return standard SPARQL JSON results ({"head": ..., "results": {"bindings": [...]}}). The common prefixes (dn, dns, dnc, dnf, wn, ontolex, lexinfo, skos, rdfs, rdf, owl, marl, dc, ili, en, enl, cor) are declared automatically. `timeout` is in ms (max 15000), `max_results` at most 100, `distinct` adds DISTINCT, and `inference` selects the model: None tries the base model and retries with inference on an empty result; True forces inference, which inverse relations like wn:hyponym and wn:holo_* need; False forces the base model. Performance rules: anchor every query on a known URI or a word lookup (dn:synset-3047 wn:hypernym ?x, never ?x wn:hypernym ?y alone); never FILTER(CONTAINS(...)) over all labels, look the word up first; make every triple pattern share a variable with another; add LIMIT; prefer VALUES over FILTER for several known URIs; the store also holds the English WordNet (en:), so anchor on dn: or "..."@da to stay in Danish. Templates: Synsets of a word: SELECT DISTINCT ?synset ?label WHERE { ?entry ontolex:canonicalForm/ontolex:writtenRep "hund"@da . ?entry ontolex:sense/ontolex:isLexicalizedSenseOf ?synset . ?synset rdfs:label ?label } Taxonomic ancestors: SELECT DISTINCT ?ancestor ?label WHERE { dn:synset-3047 wn:hypernym+ ?ancestor . ?ancestor rdfs:label ?label } Hyponyms (needs inference=True, or query the inverse wn:hypernym): SELECT DISTINCT ?hyponym ?label WHERE { ?hyponym wn:hypernym dn:synset-3047 . ?hyponym rdfs:label ?label } Ontological types (an RDF bag): SELECT ?type WHERE { dn:synset-3047 dns:ontologicalType/?pos ?type . FILTER(STRSTARTS(STR(?pos), STR(rdf:_))) } Taxonomic similarity (dnf:path, dnf:lch, dnf:wup score two synsets of the same language and part of speech, 1.0 for identical): SELECT ?synset ?score WHERE { ?synset a ontolex:LexicalConcept . FILTER(STRSTARTS(STR(?synset), STR(dn:))) BIND(dnf…
| Name | Type | Req | Description |
|---|---|---|---|
| distinct | boolean | – | – |
| inference | – | – | – |
| max_results | integer | – | – |
| query | string | yes | – |
| timeout | integer | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.kuhumcst/dannet MCP server?
io.github.kuhumcst/dannet is a hosted endpoint at https://wordnet.dk/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 · wordnet.dk
claude mcp add --transport http kuhumcst-dannet 'https://wordnet.dk/mcp'
What is the io.github.kuhumcst/dannet MCP server?
io.github.kuhumcst/dannet is an MCP server listed in the public MCP registry as io.github.kuhumcst/dannet. DanNet - Danish WordNet with rich lexical relationships and SPARQL access. This page covers its hosted endpoint (https://wordnet.dk/mcp).
Is the io.github.kuhumcst/dannet MCP server safe to use?
io.github.kuhumcst/dannet scores 74 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 io.github.kuhumcst/dannet MCP server expose?
io.github.kuhumcst/dannet exposes 6 tools: get_word_synsets, get_entity_info, get_word_overview, autocomplete_danish_word, fetch_ddo_definition, sparql_query. Their descriptions and schemas cost roughly 1,141 tokens of context every time the server is loaded.
Does the io.github.kuhumcst/dannet MCP server require authentication?
No. We connected to io.github.kuhumcst/dannet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.kuhumcst/dannet MCP server still maintained?
io.github.kuhumcst/dannet is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.kuhumcst/dannet MCP server?
VerifyMCP ran 12 checks on io.github.kuhumcst/dannet, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.kuhumcst/dannet: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.