Dannet

io.github.kuhumcstPublished by GitHub account kuhumcstv1.0.2Updated Nov 2, 2026

DanNet - Danish WordNet with rich lexical relationships and SPARQL access.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryData & Analytics

Overview

AI-generated overview

Remote MCP access to DanNet, the Danish WordNet, letting an assistant look up Danish words, senses and synsets and run SPARQL queries over the lexical graph.

What you can do
  • Look up Danish words: list their synsets with definitions, lexfiles and ontological types, or get a compact overview of every sense with synonyms and hypernyms
  • Fetch full JSON-LD records for synsets, words, senses and external resources by identifier
  • Autocomplete Danish words from a prefix, including inflected forms
  • Retrieve full DDO definitions from ordnet.dk for a synset
  • Run SPARQL SELECT queries against DanNet with common prefixes declared automatically
When to use it
Useful when an assistant needs Danish lexical semantics: definitions, synonyms, hypernyms, sense disambiguation or structured queries over a wordnet, for language work, NLP prototyping or Danish terminology research.
Requirements
A remote MCP endpoint at wordnet.dk; no package, account, API key or environment variable is declared. Network access to the endpoint is needed.
Before you install
Queries and lookups are sent to a third-party server at wordnet.dk. SPARQL queries run against the remote dataset with a timeout, so avoid heavy or repeated queries. DDO definitions are fetched from ordnet.dk and some source links no longer resolve.

Installation

In SourceWeft

  1. Open Dannet in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.kuhumcst%2Fdannet/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "dannet": {
      "type": "http",
      "url": "https://wordnet.dk/mcp"
    }
  }
}

README

[DanNet logo]

DanNet is a WordNet for the Danish language. DanNet uses RDF as its native representation at both the database level, in the application space, and as its primary serialisation format.

Table of Contents

Dataset Formats

DanNet is available in multiple formats to maximise compatibility:

FormatDescription
RDF (Turtle)Native representation. Load into any RDF graph database (such as Apache Jena) and query with SPARQL.
CSVPublished with column metadata as CSVW.
WN-LMFXML format compatible with Python libraries like wn.
DMLexOASIS DMLex 1.0 representation as both XML and JSON, in a Danish and an English variant. The DMLex browser shows it as a dictionary.

Example: Using DanNet with Python

python
import wn
wn.add("dannet-wn-lmf.xml.gz")
for synset in wn.synsets('kage'):    print((synset.lexfile() or "?") + ": " + (synset.definition() or "?"))

Differences Between Formats

While every format includes all synsets/senses/words, the CSV, WN-LMF and DMLex variants do not include every data point:

  • CSV: Some data is lost when converting from an open graph to fixed tables.
  • WN-LMF: Only official GWA relations are included per the standard (proprietary DanNet relations from the DanNet schema are excluded).
  • DMLex: Combines DanNet with COR, DDS and COR.SEM in one file. Relations to other datasets are not included. See doc/dmlex/plan.md for the conversion rules.

For the complete dataset, use the RDF format or browse at wordnet.dk.

Companion Datasets

Several companion datasets expand the RDF graph with additional data:

DatasetDescription
CORLinks DanNet resources to IDs from the COR project.
DDSAdds sentiment data to DanNet resources.
OEWN extensionProvides DanNet-style labels for the Open English WordNet to facilitate browsing connections between the two datasets.

Inferred Data

Additional data is implicitly inferred from the base dataset, companion datasets, and ontological metadata. These inferences can be browsed at wordnet.dk. Releases containing fully inferred graphs are specifically marked as such.

Standards

DanNet is based on the Ontolex-lemon standard combined with relations defined by the Global Wordnet Association as used in the official GWA RDF standard.

Ontolex-lemon classRepresents
ontolex:LexicalConceptSynsets
ontolex:LexicalSenseWord senses
ontolex:LexicalEntryWords
ontolex:FormForms

[Ontolex-lemon representation]

URI Prefixes

PrefixURIPurpose
dnhttps://wordnet.dk/dannet/data/Dataset instances
dnchttps://wordnet.dk/dannet/concepts/Ontological type members
dnshttps://wordnet.dk/dannet/schema/Schema definitions
dnfhttps://wordnet.dk/dannet/function/Custom SPARQL functions (dnf:path, dnf:lch, dnf:wup synset similarity)

All DanNet URIs resolve to HTTP resources. Accessing one of these URIs via a GET request returns the data for that resource.

Schemas

DanNet has proprietary relations defined in the DanNet schema in an Ontolex-compatible way. There is also a schema for EuroWordNet concepts. Both schemas follow the RDF conventions listed by Philippe Martin.

LLM Integration

DanNet can be connected to AI tools like Claude via MCP (Model Context Protocol).

  • MCP server URL: https://wordnet.dk/mcp
  • Registry ID: io.github.kuhumcst/dannet

To connect in e.g. Claude Desktop: go to Settings > Connectors > Browse Connectors, click "add a custom one", enter a name (e.g., "DanNet") and the MCP server URL.

[Claude Desktop setup]

Once connected, you can query DanNet's semantic relations directly through Claude.

Implementation

The database backend is Apache Jena, a mature RDF triplestore with OWL inference support. When represented in Jena, DanNet's relations form a queryable knowledge graph. DanNet is developed in Clojure, using Theophrastus, our fork of Aristotle, to interact with Jena.

See rationale.md for more on the design decisions.

Full Production Setup

The production deployment at wordnet.dk consists of three services managed via Docker Compose:

  • DanNet — the Clojure/ClojureScript web application
  • MCP server — a Python-based MCP server providing LLM access to DanNet
  • Caddy — reverse proxy handling HTTPS and routing

Clojure Support

DanNet can be queried in various ways from Clojure (see queries.md). Apache Jena transactions are built-in and enable persistence via the TDB 2 layer.

Web Application

The frontend is written in ClojureScript using Rum, served by Pedestal. The app works both as a single-page application (with JavaScript) and as a regular HTML website (without). Content negotiation serves different representations (HTML, RDF, Transit+JSON) based on the request.

See doc/web.md for details.

Bootstrap Process

New releases are bootstrapped from the preceding release. The process (in dk.cst.dannet.db.bootstrap):

  1. Load and clean the previous version's RDF data
  2. Convert to triples using the current schema
  3. Import into Apache Jena graphs and apply release changes (only when cutting a release, i.e. when to differs from from)
  4. Infer additional triples via OWL/RDFS schemas
  5. Export the final RDF dataset (see Database Release Workflow)

Bootstrap data lives under ./bootstrap relative to the execution directory: the DanNet release assets in ./bootstrap/from/<version>/ (named after the release being bootstrapped from, so several can coexist) and the shared English datasets in ./bootstrap/other/english/. Missing files are downloaded automatically, so manual placement is only needed when working offline.

The rest of ./bootstrap/other/ holds files curated by hand, which aren't downloaded. If the COR files (cor*.tsv, *.cordiff and cor.sem.*.tsv) go missing, you can download them again from ordregister.dk.

If a database build fails partway, delete the half-built db/tdb2/<name> directory before you start again; the build error gives its path. A build only checks that the directory exists, so it would otherwise reuse the incomplete database.

Setup

DanNet requires Java and Clojure's official CLI tools. Dependencies are specified in deps.edn.

Development

  1. Start an nREPL on port 7888 with clojure -M:nrepl
  2. Start the web service using (restart) in dk.cst.dannet.web.service — available at localhost:3456
  3. Run the frontend with shadow-cljs:
    shell
    npx shadow-cljs watch app
    It serves the app at localhost:7777, in front of the web service.

Most changes can be tried in the REPL without restarting the web service. Run the tests with clojure -X:validate:test, where the :validate alias adds the validators that the DMLex tests need.

Testing a Release Build

Using Docker (requires Docker daemon running):

shell
# From the docker/ directorydocker compose up --build

Or manually:

shell
shadow-cljs --aliases :frontend release appclojure -T:build org.corfield.build/uber :lib dk.cst/dannet :main dk.cst.dannet.web.service :uber-file "\"dannet.jar\""java -jar -Xmx4g dannet.jar

Memory Requirements

The system uses ~1.5 GB when idle and ~3 GB when rebuilding the database. A server should have at least 4 GB of available RAM.

Validating RDF (SHACL)

The dn: dataset is validated against SHACL shapes located in resources/schemas/internal/shapes/ (see dk.cst.dannet.db.shapes). This happens in several ways:

  • a non-fatal check of the asserted graph runs asynchronously at every boot, logging violations and comparing counts to a known baseline,
  • RDF exports of the dn: dataset are gated: a baseline regression aborts the export, and
  • fixture-based tests run via clojure -X:validate:test, which is also executed by the GitHub Actions workflow in .github/workflows/test.yml.

Validating WN-LMF

shell
python3 -m venv examples/venvsource examples/venv/bin/activatepython3 -m pip install wnpython -m wn validate --output-file examples/wn-lmf-validation.json export/wn-lmf/dannet-wn-lmf.xml

Validating DMLex

The validator in dk.cst.dannet.db.export.dmlex-validate checks both serializations of a variant against the official DMLex schemas. It needs the :validate alias:

shell
clojure -M:validate -e "((requiring-resolve 'dk.cst.dannet.db.export.dmlex-validate/validate-dmlex!) \"export/dmlex/\" \"da\")"

Deployment

The production server at wordnet.dk runs as a systemd service delegating to Docker.

Service Setup

shell
cp system/dannet.service /etc/systemd/system/dannet.servicesystemctl enable dannetsystemctl start dannet

Updating the Web Service

To update the web service software without changing the database:

shell
# From the docker/ directorydocker compose up -d dannet --build

Database Release Workflow

When releasing a new version of the database:

  1. Set to in dk.cst.dannet.release to the new version, leaving from on the release being bootstrapped from. The release-specific changes in make-release-changes! only run once the two differ.

  2. Build the database via REPL in dk.cst.dannet.web.service:

    clojure
    (restart)
  3. Generate the export artifacts. The web service loads only some of the export namespaces, so require them all first:

    clojure
    (require 'dk.cst.dannet.db.export.rdf         'dk.cst.dannet.db.export.csv         'dk.cst.dannet.db.export.wn-lmf         'dk.cst.dannet.db.export.dmlex)(dk.cst.dannet.db.export.rdf/export-rdf! @dk.cst.dannet.web.instance/db)(dk.cst.dannet.db.export.csv/export-csv! @dk.cst.dannet.web.instance/db)(dk.cst.dannet.db.export.wn-lmf/export-wn-lmf! @dk.cst.dannet.web.instance/db "export/wn-lmf/")(dk.cst.dannet.db.export.dmlex/export-dmlex-variants! @dk.cst.dannet.web.instance/db "export/dmlex/");; ~6 minutes(dk.cst.dannet.db.query/save-synset-indegrees!  (:inference @dk.cst.dannet.web.instance/db))

    This writes export/rdf/ (dannet.zip, cor.zip, cor-sem.zip, framenet.zip, dds.zip, oewn-extension.zip), export/csv/dannet-csv.zip, export/wn-lmf/dannet-wn-lmf.xml.gz, export/dmlex/ (dannet-dmlex-da.zip, dannet-dmlex-en.zip) and export/synset-indegree.edn. These ship to production (step 7) and become the GitHub release assets that the next cycle bootstraps from (step 4).

  4. Publish a GitHub release tagged v<version> and attach the bootstrap assets listed by bootstrap-files in dk.cst.dannet.db.bootstrap.downloads: dannet.zip, cor.zip, cor-sem.zip, dds.zip, oewn-extension.zip and synset-indegree.edn. The next cycle fetches these from GitHub.

  5. Compact the database, then zip it on the dev machine, ready for transfer:

    clojure
    (dk.cst.theophrastus.tdb2/compact! (:dataset @dk.cst.dannet.web.instance/db))

    TDB2 only reclaims the space left by in-place updates when compacted, and writes a new Data-000N generation, so restart the service afterwards. Before transferring, check that the database size divided by the triple count is in the hundreds of bytes, not the thousands.

  6. Stop the service on production:

    shell
    docker compose stop dannet
  7. Transfer database and export files via SFTP, then:

    shell
    unzip -o tdb2.zip -d /dannet/db/mv cor.zip cor-sem.zip framenet.zip dannet.zip dds.zip oewn-extension.zip /dannet/export/rdf/mv dannet-csv.zip /dannet/export/csv/mv dannet-wn-lmf.xml.gz /dannet/export/wn-lmf/mv dannet-dmlex-da.zip dannet-dmlex-en.zip /dannet/export/dmlex/
  8. Ship the export/synset-indegree.edn generated in step 3. Production runs with --no-bootstrap and so never downloads it, but it is read at query time to rank search results and entity relations, and it should describe the database actually being shipped. Either location works, the first taking precedence (see indegrees-files in dk.cst.dannet.db.query):

    shell
    mv synset-indegree.edn /dannet/db/                      # legacy locationmv synset-indegree.edn /dannet/bootstrap/from/2026-08-03/   # alongside the bootstrap inputs

    If neither exists the service still starts and search still works, but results come back unranked and a :dannet.query/indegrees-unavailable error is logged.

  9. Restart:

    shell
    docker compose up -d dannet --build
  10. Bump from to the new version and set to to "SNAPSHOT". Clear out the release-specific block in make-release-changes!: its changes have now shipped. This readies the next cycle.

Source: README.md at commit 18d026b

Tools

6

get_word_synsets

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.

Parameterswordrequired

get_entity_info

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": ...}.

Parametersidentifierrequired

get_word_overview

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.

Parameterswordrequired

autocomplete_danish_word

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.

Parametersprefixrequiredmax_results

fetch_ddo_definition

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.

Parameterssynset_idrequired

sparql_query

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:

Parametersqueryrequiredtimeoutdistinctinferencemax_results

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts