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.Kind-ling/twig

NPM · @KIND-LING/TWIG · SCANNED AUG 10

MCP server quality scoring and optimization for the agent economy.

Available components

npm · @kind-ling/twig 36
+3 this week 36 Trust /100
Trust breakdown (6 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 →

Supply Chain Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects path-to-regexp 0.1.12, reached via express > path-to-regexp. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 27 of 83 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @kind-ling/twig

# add to Claude Code
claude mcp add kind-ling-twig -- npx -y @kind-ling/twig
# add to Codex CLI
codex mcp add kind-ling-twig -- npx -y @kind-ling/twig
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kind-ling-twig": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@kind-ling/twig"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add kind-ling-twig --command npx --arg -y --arg @kind-ling/twig
# ~/.hermes/config.yaml
mcp_servers:
  kind-ling-twig:
    command: "npx"
    args: ["-y", "@kind-ling/twig"]
// mcp.json
{
  "mcpServers": {
    "kind-ling-twig": {
      "command": "npx",
      "args": [
        "-y",
        "@kind-ling/twig"
      ]
    }
  }
}
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.

  • 10 Aug 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 9 Aug 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 7 Aug 26 +3
    • Dependency health: partial → 0.83 functional
  • 3 Aug 26 −3

    No change was recorded against any check on this day. Supply Chain Security went from 89 to 79.

  • 2 Aug 26 +31
    • CVE-2026-2391 affects this package: high ▼ security
    • CVE-2025-15284 affects this package: high ▼ security
    • CVE-2026-8723 affects this package: high ▼ security
    • CVE-2026-12590 affects this package: high ▼ security
    • CVE-2024-45296 affects this package: high ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Provenance: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • License: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • Licence: MIT functional
  • 1 Aug 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified ▼ security
  • 27 Jul 26 24

    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 10 Aug 2026 · Analysed npm/@kind-ling/[email protected]

Provenance No attestation

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

Result No attestation
Ecosystem npm
Vulnerabilities 5 findings
ID CVE Severity Vector Fix available
GHSA-v422-hmwv-36x6 CVE-2026-12590 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-37ch-88jc-xwx2 CVE-2024-45296 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6rw7-vpxm-498p CVE-2025-15284 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-q8mj-m7cp-5q26 CVE-2026-8723 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-w7fw-mjwx-w883 CVE-2026-2391 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
Dependencies 83 packages
Packages resolved 83
Stale 27
Tree resolution Complete
MCP tools

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.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.