Sign In

@decantr/mcp-server

Package Overview
Dependencies
Maintainers
1
Versions
50
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@decantr/mcp-server - npm Package Compare versions

Comparing version
3.11.2
 to
3.11.3
dist/chunk-URUS2237.js

Sorry, the diff of this file is too big to display

+1
-1
dist/bin.js
#!/usr/bin/env node
import "./chunk-7CEFKAIJ.js";
import "./chunk-URUS2237.js";
import "./chunk-CZ7CSFO4.js";
+1
-1
dist/index.js

@@ -1,2 +0,2 @@

import "./chunk-7CEFKAIJ.js";
import "./chunk-URUS2237.js";
import "./chunk-CZ7CSFO4.js";
+2
-2
package.json

@@ -13,3 +13,3 @@ {

"@decantr/essence-spec": "3.8.1",
"@decantr/verifier": "3.11.2"
"@decantr/verifier": "3.11.3"
},

@@ -69,3 +69,3 @@ "description": "Eight-tool Decantr MCP server for changed-UI assurance, authority-aware context, and verification evidence",

"types": "dist/index.d.ts",
"version": "3.11.2"
"version": "3.11.3"
}
+12
-12
README.md

@@ -11,7 +11,7 @@ # @decantr/mcp-server

Stable Decantr 3.11.2 MCP integration for Changed-UI Assurance, local project state, authority-aware route and non-route task context, graph and evidence reads, and repair prompts.
Stable Decantr 3.11.3 MCP integration for Changed-UI Assurance, local project state, authority-aware route and non-route task context, graph and evidence reads, and repair prompts.
## Release Boundary
The published npm package is 3.11.2. Its eight tool IDs, route-backed `TaskCapsuleV1` path, authority-aware target discovery, verification actions, and compatibility envelopes are stable. The existing `decantr_verify` tool adds action `changes`, which returns the same `change-assurance-report.v1` used by bare CLI verify and explicit CI v3. No ninth tool is added.
The published npm package is 3.11.3. Its eight tool IDs, route-backed `TaskCapsuleV1` path, authority-aware target discovery, verification actions, and compatibility envelopes are stable. The existing `decantr_verify` tool adds action `changes`, which returns the same `change-assurance-report.v1` used by bare CLI verify and explicit CI v3. No ninth tool is added.

@@ -38,3 +38,3 @@ ![Decantr MCP demo](https://raw.githubusercontent.com/decantr-ai/decantr/main/packages/mcp-server/assets/decantr-demo.gif)

"command": "npx",
"args": ["@decantr/mcp-server@3.11.2"]
"args": ["@decantr/mcp-server@3.11.3"]
}

@@ -52,3 +52,3 @@ }

```bash
npx @decantr/cli@3.11.2 connect cursor
npx @decantr/cli@3.11.3 connect cursor
```

@@ -69,3 +69,3 @@

"command": "npx",
"args": ["-y", "@decantr/mcp-server@3.11.2"]
"args": ["-y", "@decantr/mcp-server@3.11.3"]
}

@@ -87,3 +87,3 @@ }

"command": "npx",
"args": ["@decantr/mcp-server@3.11.2"]
"args": ["@decantr/mcp-server@3.11.3"]
}

@@ -103,3 +103,3 @@ }

"command": "npx",
"args": ["-y", "@decantr/mcp-server@3.11.2"]
"args": ["-y", "@decantr/mcp-server@3.11.3"]
}

@@ -121,3 +121,3 @@ }

"command": "npx",
"args": ["-y", "@decantr/mcp-server@3.11.2"],
"args": ["-y", "@decantr/mcp-server@3.11.3"],
"env": {}

@@ -143,3 +143,3 @@ }

- "-y"
- "@decantr/mcp-server@3.11.2"
- "@decantr/mcp-server@3.11.3"
```

@@ -164,3 +164,3 @@

For an attached route, pass `route` or the compatible `page_id` to the `task` action. Compact mode projects the verifier-owned `TaskCapsuleV1` into the existing response fields and remains within 12,000 canonical UTF-8 bytes / 4,000 estimated tokens. Missing or stale graph evidence reports `blocked_missing_graph`; incomplete Angular production-route authority reports `DISCOVERY_NOT_PROVEN`. Neither condition selects an implementation source by guess.
For an attached route, pass `route` or the compatible `page_id` to the `task` action. Compact mode projects the verifier-owned `TaskCapsuleV1` into the existing response fields and remains within 12,000 canonical UTF-8 bytes / 4,000 estimated tokens. SvelteKit route reads keep `+page.svelte` first and colocated page-data modules as supporting authority. Missing or stale graph evidence reports `blocked_missing_graph`; incomplete Angular production-route authority reports `DISCOVERY_NOT_PROVEN`. Neither condition selects an implementation source by guess.

@@ -177,3 +177,3 @@ Local scaffold, page, and section paths selected by `pack-manifest.json` are read or emitted as task read targets only when they resolve to real files contained under the selected project's `.decantr/context` directory. Missing, escaped, directory, and symlink-escaped references are ignored; existing `scaffold.md` and `section-<id>.md` narrative context remains the local fallback. In Greenfield `style-bridge` adoption, the accepted bridge maps onto the host project's tokens, classes, and styling runtime; it does not activate `@decantr/css`.

Next file routes that are hidden by statically resolved middleware/proxy non-success policy are valid discovery surfaces but non-taskable MCP targets. If that policy is path-dependent and cannot be resolved, task preparation returns blocked authority instead of selecting a route by convention alone. TanStack generated metadata may corroborate an authored route's public path but is advisory evidence, never the implementation target. Astro response endpoints and TanStack/Angular layouts or fallbacks remain non-taskable. Angular task reads include statically resolved external templates, component styles, and workspace secondary-entry source. Ranked style reads retain production CSS import order, including workspace package exports. Attached route compatibility responses include the same verifier-ranked read set as CLI, exclude generated governance churn from changed-source impact, and shed compatibility-only detail before exceeding the task-capsule budget.
Next file routes that are hidden by statically resolved middleware/proxy non-success policy are valid discovery surfaces but non-taskable MCP targets. If that policy is path-dependent and cannot be resolved, task preparation returns blocked authority instead of selecting a route by convention alone. TanStack generated metadata may corroborate an authored route's public path but is advisory evidence, never the implementation target. Astro response endpoints and TanStack/Angular layouts or fallbacks remain non-taskable. SvelteKit page-data modules remain non-taskable and can support only the colocated `+page.svelte` implementation. Angular task reads include statically resolved external templates, component styles, and workspace secondary-entry source. Ranked style reads retain production CSS import order, including workspace package exports. Attached route compatibility responses include the same verifier-ranked read set as CLI, exclude generated governance churn from changed-source impact, and shed compatibility-only detail before exceeding the task-capsule budget.

@@ -219,3 +219,3 @@ Authoritative non-route and unadopted targets return the separate `ui-surface-task-context.v1` discovery envelope with bounded reads and explicit limitations. A standalone component or story remains project-reference evidence rather than proof of runtime reachability. An adopted route continues to use the compatible `TaskCapsuleV1` contract.

Published 3.11.2 reads project-owned evidence: the Git change, application source and framework configuration, directly referenced workspace components, accepted local rules, `decantr.essence.json` when present, graph artifacts, baselines, and verification findings. In Brownfield, production source remains first authority and accepted Essence is project law beneath it. MCP clients can request Changed-UI Assurance with no adoption, request bounded task context before an edit, and inspect verification evidence after the edit. Decantr reports evidence and limitations; the coding agent remains responsible for the code change.
Published 3.11.3 reads project-owned evidence: the Git change, application source and framework configuration, directly referenced workspace components, accepted local rules, `decantr.essence.json` when present, graph artifacts, baselines, and verification findings. In Brownfield, production source remains first authority and accepted Essence is project law beneath it. MCP clients can request Changed-UI Assurance with no adoption, request bounded task context before an edit, and inspect verification evidence after the edit. Decantr reports evidence and limitations; the coding agent remains responsible for the code change.

@@ -222,0 +222,0 @@ ## Example Workflow

+2
-2
server.json

@@ -9,3 +9,3 @@ {

},
"version": "3.11.2",
"version": "3.11.3",
"packages": [

@@ -15,3 +15,3 @@ {

"identifier": "@decantr/mcp-server",
"version": "3.11.2",
"version": "3.11.3",
"transport": {

@@ -18,0 +18,0 @@ "type": "stdio"

dist/chunk-7CEFKAIJ.js

Sorry, the diff of this file is too big to display