Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

datuma_k

NPM · @MARTHVON/DATUMA-K-MCP · SCANNED SEP 24

Query, validate, preview, and generate source from *.dtct data contracts and *.ngin templates.

+6 this week 77 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability82
  • 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
  • Tool/resource definitions use about 519 tokens (~39/item across 13 items; 7 tools + 6 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 62% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the datuma_k MCP server?

datuma_k runs locally as an npm package, launched with npx -y @marthvon/datuma-k-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @marthvon/datuma-k-mcp

# add to Claude Code
claude mcp add marthvon-datuma-k -- npx -y @marthvon/datuma-k-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "marthvon-datuma-k": {
      "command": "npx",
      "args": [
        "-y",
        "@marthvon/datuma-k-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "marthvon-datuma-k": {
      "command": "npx",
      "args": [
        "-y",
        "@marthvon/datuma-k-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add marthvon-datuma-k -- npx -y @marthvon/datuma-k-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marthvon-datuma-k": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@marthvon/datuma-k-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add marthvon-datuma-k --command npx --arg -y --arg @marthvon/datuma-k-mcp
# ~/.hermes/config.yaml
mcp_servers:
  marthvon-datuma-k:
    command: "npx"
    args: ["-y", "@marthvon/datuma-k-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "marthvon-datuma-k": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@marthvon/datuma-k-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add marthvon-datuma-k -t stdio -c npx -a -y @marthvon/datuma-k-mcp
// mcp.json
{
  "mcpServers": {
    "marthvon-datuma-k": {
      "command": "npx",
      "args": [
        "-y",
        "@marthvon/datuma-k-mcp"
      ]
    }
  }
}
Changelog

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.

  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +3
    • Stability: unverified → 0.23 ▲ functional
  • 12 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Sept 26 56

    First indexed and scored.

Diagnostics

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 24 Sept 2026 · Analysed npm/@marthvon/datuma-k-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~456 tokens

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 →

Tool Tokens
advise_ngin ~74

Decide whether a coding task should use the ngin template engine or stay handwritten. Use ngin when two or more platforms must stay in sync on contract-derived types, validation, or UI.

NameTypeReqDescription
platformsarrayyesWhere the result will ship
taskstringyesWhat the agent wants to add or generate

No output schema declared.

No examples provided.

generate ~48

Run datuma_k run: commit planned files through dkcache. Overwrites text inside generated spans; keeps text between spans.

NameTypeReqDescription
rootstring–Project directory (defaults to the MCP process cwd)

No output schema declared.

No examples provided.

infer_patterns ~81

Suggest shared Data/Enum traits, field attributes, and UI widgets from the contract. Flag unusual default-vocabulary pairings as association_suggestions (review notes, not errors). Flag single-platform sync risks. Map aliases like text_type to string. Does not write files or reject contracts.

NameTypeReqDescription
rootstring–Project directory (defaults to the MCP process cwd)

No output schema declared.

No examples provided.

list_project ~52

List .env directories and *.dtct, *.ngin, *.def.ngin, and keywords.md for a datuma_k project.

NameTypeReqDescription
rootstring–Project directory (defaults to the MCP process cwd)

No output schema declared.

No examples provided.

preview ~43

Plan generated files from ngin without committing. Returns planned paths and content. Does not write disk.

NameTypeReqDescription
rootstring–Project directory (defaults to the MCP process cwd)

No output schema declared.

No examples provided.

query_contracts ~95

JSON catalog of dtct models, fields, traits, types, and attributes. Optional filters match dk.trait / dk.model / dk.field / dk.attribute / dk.type.

NameTypeReqDescription
attributestring––
fieldstring––
modelstring––
rootstring–Project directory (defaults to the MCP process cwd)
traitstring––
typestring––

No output schema declared.

No examples provided.

validate ~63

Parse *.dtct / *.ngin / *.def.ngin and require a data/keywords.md table (kind, description, purpose, platforms) for every contract name. Does not write files.

NameTypeReqDescription
rootstring–Project directory (defaults to the MCP process cwd)

No output schema declared.

No examples provided.

Common questions

What is the datuma_k MCP server?

datuma_k is an MCP server listed in the public MCP registry as io.github.marthvon/datuma-k. Query, validate, preview, and generate source from *.dtct data contracts and *.ngin templates. This page covers its npm package (@marthvon/datuma-k-mcp).

Is the datuma_k MCP server safe to use?

datuma_k scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 datuma_k MCP server expose?

datuma_k exposes 7 tools: list_project, query_contracts, validate, preview, generate, and 2 more. Their descriptions and schemas cost roughly 456 tokens of context every time the server is loaded.

Is the datuma_k MCP server still maintained?

datuma_k is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the datuma_k MCP server under?

datuma_k declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.