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.

io.github.decantr-ai/mcp-server

NPM · @DECANTR/MCP-SERVER · SCANNED SEP 20

Stable eight-tool MCP server for changed-UI assurance, authority-aware UI task context, and repair.

Available components

0 this week 94 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 Security99
  • 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
  • 3 of 11 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to decantr-ai/decantr). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 40 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 395 tokens (~49/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.decantr-ai/mcp-server server?

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

npm · @decantr/mcp-server

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

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 15 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 14 Sept 26 0
    • Stability: 0.97 → pass security
    • Package version: 3.11.1 → 3.11.2 functional
  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 10 Sept 26 0
    • Package version: 3.11.1 → 3.11.2 functional
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 20 Sept 2026 · Analysed npm/@decantr/mcp-server@3.11.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo decantr-ai/decantr
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/decantr-ai/decantr/.github/workflows/publish.yml@refs/heads/main
Rekor log index 2385579896
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:d1c0c6891136a1d6a00b1fb32984db07080b02c6049bda7da61561e03fc1084f8e4afbe75a27f14f941a6c12a7efd433fc8b74059e322b7b20b0796b1

Background: How many MCP packages publish verified provenance →

Dependencies 11 packages
Packages resolved 11
Stale 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~395 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
decantr_context ~55

Prepare discovery-backed UI surface task context, preserve authoritative route capsules, or read existing scaffold, section, page, and execution-pack context.

NameTypeReqDescription
actionstringyesSelect one of this compatibility-stable tool's existing actions.

No output schema declared.

No examples provided.

decantr_contract ~49

Read and validate the project-owned Decantr contract, inspect drift, or create a compatibility contract skeleton.

NameTypeReqDescription
actionstringyesSelect one of this compatibility-stable tool's existing actions.

No output schema declared.

No examples provided.

decantr_contract_write ~45

Explicit workspace-contained write surface for accepting drift or updating the Essence v4 contract.

NameTypeReqDescription
actionstringyesSelect one of this compatibility-stable tool's existing actions.

No output schema declared.

No examples provided.

decantr_graph ~47

Read, query, and traverse local graph and source evidence that supports route-scoped UI work.

NameTypeReqDescription
actionstringyesSelect one of this compatibility-stable tool's existing actions.

No output schema declared.

No examples provided.

decantr_project ~47

Observe local project authority, selected-app discovery, adoption truth, and workspace health without uploading source.

NameTypeReqDescription
actionstringyesSelect one of this compatibility-stable tool's existing actions.

No output schema declared.

No examples provided.

decantr_registry ~54

Legacy-named compatibility access to the official Decantr content corpus, benchmark metadata, and execution packs; not a public registry.

NameTypeReqDescription
actionstringyesSelect one of this compatibility-stable tool's existing actions.

No output schema declared.

No examples provided.

decantr_repair ~45

Turn typed verification findings into scoped repair plans, prompts, and health-loop guidance.

NameTypeReqDescription
actionstringyesSelect one of this compatibility-stable tool's existing actions.

No output schema declared.

No examples provided.

decantr_verify ~53

Verify local UI diffs with changed-UI assurance, or return deeper critique, findings, health state, and evidence bundles.

NameTypeReqDescription
actionstringyesSelect one of this compatibility-stable tool's existing actions.

No output schema declared.

No examples provided.

Common questions

What is the io.github.decantr-ai/mcp-server server?

io.github.decantr-ai/mcp-server is listed in the public MCP registry as io.github.decantr-ai/mcp-server. Stable eight-tool MCP server for changed-UI assurance, authority-aware UI task context, and repair. This page covers its npm package (@decantr/mcp-server).

Is the io.github.decantr-ai/mcp-server server safe to use?

io.github.decantr-ai/mcp-server scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.decantr-ai/mcp-server server expose?

io.github.decantr-ai/mcp-server exposes 8 tools: decantr_project, decantr_contract, decantr_context, decantr_graph, decantr_registry, and 3 more. Their descriptions and schemas cost roughly 395 tokens of context every time the server is loaded.

Is the io.github.decantr-ai/mcp-server server still maintained?

io.github.decantr-ai/mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 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 io.github.decantr-ai/mcp-server server under?

io.github.decantr-ai/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.