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.zktx-mcp/say-ur-intent

NPM · @ZKTX.IO/SAY-UR-INTENT · SCANNED SEP 27

Local-first Sui DeFi evidence and review for AI clients before wallet signing.

Available components

npm · @zktx.io/say-ur-intent 46
46 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 Security88
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects mermaid 11.12.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 400 of 409 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to zktx-mcp/say-ur-intent). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks 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 we can run it. How we score packages →

Install

How do I install the io.github.zktx-mcp/say-ur-intent server?

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

npm · @zktx.io/say-ur-intent

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

  • 27 Sept 26 +8
    • CVE-2026-71437 affects this package: medium ▼ security
    • CVE-2021-23337 affects this package: medium ▼ security
    • CVE-2026-50159 affects this package: medium ▼ security
    • CVE-2026-41149 affects this package: medium ▼ security
    • CVE-2026-41148 affects this package: medium ▼ security
    • CVE-2026-71436 affects this package: medium ▼ security
    • CVE-2025-13465 affects this package: medium ▼ security
    • CVE-2026-71439 affects this package: medium ▼ security
    • CVE-2026-41159 affects this package: medium ▼ security
    • CVE-2026-71438 affects this package: medium ▼ security
    • CVE-2026-41150 affects this package: medium ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Dependency health: unverified → partial ▲ functional
  • 26 Sept 26 38

    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 27 Sept 2026 · Analysed npm/@zktx.io/say-ur-intent@0.4.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 zktx-mcp/say-ur-intent
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/zktx-mcp/say-ur-intent/.github/workflows/publish.yml@refs/tags/v0.4.2
Rekor log index 2969355841
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:e218e2beec0d1c075dbb49827d516e32509426ea53f52a7dc75f7e1a1a4b07bb42f3ada804754b22ce5bfe8a0b99429a36025cb3cac5884359d7e12e5

Background: How many MCP packages publish verified provenance →

Vulnerabilities 12 findings
ID CVE Severity Vector Fix available
GHSA-f23m-r3pf-42rh CVE-2025-13465 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-r5fr-rjxr-66jc CVE-2021-23337 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-xxjr-mmjv-4gpg CVE-2025-13465 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-2v8p-3f2j-5mp7 CVE-2026-71436 medium yes
GHSA-3rrr-jr9j-h3q3 CVE-2026-71437 medium yes
GHSA-6m6c-36f7-fhxh CVE-2026-41150 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-6x64-9x62-f2gx CVE-2026-50159 medium yes
GHSA-87f9-hvmw-gh4p CVE-2026-41159 medium yes
GHSA-c4c3-pg64-4m4v CVE-2026-71438 low yes
GHSA-ghcm-xqfw-q4vr CVE-2026-41149 medium yes
GHSA-rhh3-jpg6-66xh CVE-2026-71439 medium yes
GHSA-xcj9-5m2h-648r CVE-2026-41148 medium yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 400 packages
Packages resolved 400
Deprecated 1
Stale 162
No linked repository 2
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

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

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.

Common questions

What is the io.github.zktx-mcp/say-ur-intent server?

io.github.zktx-mcp/say-ur-intent is listed in the public MCP registry as io.github.zktx-mcp/say-ur-intent. Local-first Sui DeFi evidence and review for AI clients before wallet signing. This page covers its npm package (@zktx.io/say-ur-intent).

Is the io.github.zktx-mcp/say-ur-intent server safe to use?

io.github.zktx-mcp/say-ur-intent scores 46 out of 100 on VerifyMCP. We recorded 12 known advisories against it as of 27 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.

Is the io.github.zktx-mcp/say-ur-intent server still maintained?

io.github.zktx-mcp/say-ur-intent is still listed as active in the MCP registry. We last reached this channel on 27 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.zktx-mcp/say-ur-intent server under?

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