mcp-registry/io.github.kuhumcst/dannet · v1.13.1
As of 2026-10-26 17:13 UTC, the Kuhumcst Dannet MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 7 minutes.
DanNet - Danish WordNet with rich lexical relationships and SPARQL access.
Point your MCP client at this streamable-http endpoint: https://wordnet.dk/mcp
11 parameter(s) across 6 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.kuhumcst%2Fdannet/fixes
{
"name": "fetch_ddo_definition",
"description": "The full definitions of `synset_id` from DDO (ordnet.dk), where DanNet's\nown skos:definition may be truncated. Follows the dns:source of each sense.\nReturns the DanNet definition, the DDO definitions found and any errors;\nDDO and DanNet have drifted apart, so some source URLs no longer resolve.",
"inputSchema": {
"type": "object",
"title": "fetch_ddo_definitionArguments",
"required": [
"synset_id"
],
"properties": {
"synset_id": {
"type": "string",
"title": "Synset Id"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_entity_info",
"description": "Full JSON-LD of a DanNet resource: a synset (\"synset-3047\"), word\n(\"word-11021628\") or sense (\"sense-21033604\"), given bare or prefixed\n(\"dn:synset-3047\"), or an external resource by prefix (\"ili:i76470\",\n\"ontolex:LexicalConcept\"). Properties use prefixed names (wn:hypernym,\nontolex:isEvokedBy, ...); language-tagged values are\n{\"@value\": ..., \"@language\": ...}.",
"inputSchema": {
"type": "object",
"title": "get_entity_infoArguments",
"required": [
"identifier"
],
"properties": {
"identifier": {
"type": "string",
"title": "Identifier"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_word_overview",
"description": "Every sense of the Danish `word` in one call: a list with synset_id,\nlabel, definition, lexfile, ontological_types, synonyms (words sharing the\nsynset) and hypernym ({synset_id, label} or null) per synset. Only synsets\nwhere the word itself has a sense count, not multi-word expressions\ncontaining it.",
"inputSchema": {
"type": "object",
"title": "get_word_overviewArguments",
"required": [
"word"
],
"properties": {
"word": {
"type": "string",
"title": "Word"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.kuhumcst/dannet"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.kuhumcst/dannet"}) over MCP.
sparql_query ~274 tokensget_entity_info ~164 tokensfetch_ddo_definition ~142 tokensget_word_overview ~138 tokensautocomplete_danish_word ~137 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.kuhumcst%2Fdannet?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.kuhumcst%2Fdannet?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kuhumcst%2Fdannet.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kuhumcst%2Fdannet.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.kuhumcst%2Fdannet?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:59e27cfd75250e41…, first seen 2026-10-17, included at leaf 12120 of 74,339. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable database servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 17:13 UTC, the Kuhumcst Dannet MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 7 minutes.
Kuhumcst Dannet MCP server advertises 7 tools, including autocomplete_danish_word, fetch_ddo_definition, get_entity_info, get_word_overview, get_word_synsets.
Point your MCP client at this streamable-http endpoint: https://wordnet.dk/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.