Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Dannet

by kuhumcstversion 1.0.2i★ –iRuns in the cloud
Registry nameio.github.kuhumcst/dannet

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://wordnet.dk/mcp

Run this in your terminal

claude mcp add --transport http dannet https://wordnet.dk/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://wordnet.dk/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account kuhumcst, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 18348 servers in this category
  • Published to the registry more recently than 1% of the other 18348 servers in this category
  • Basic checks equal to or better than 100% of the other 18348 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Dannet safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 10 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, 好縮 Short

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

好縮 Short

by gooonamee

Smart URL shortener: create, tag and track short links on s.gooo.name.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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
  • Companion Datasets
  • Standards
  • LLM Integration (AI)
  • Implementation
  • Setup
  • Deployment
  • Database Release Workflow

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
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
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.

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/ / (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/ 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:
   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):

# From the docker/ directory

docker compose up --build

Or manually:

shadow-cljs --aliases :frontend release app

clojure -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
python3 -m venv examples/venv

source examples/venv/bin/activate python3 -m pip install wn python -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:

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
cp system/dannet.service /etc/systemd/system/dannet.service

systemctl enable dannet systemctl start dannet

Updating the Web Service

To update the web service software without changing the database:

# From the docker/ directory

docker 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 ne

Only the beginning is shown; read the rest in the repo

Ask PopNx