@t2000/mcp
MCP server for AI agent bank accounts on Sui — 29 tools, 15 prompts, stdio transport. Drop-in for Claude Desktop, Cursor, Cline, Continue, or any MCP-compatible client.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/bin.js | AI (source-diff): Long hex strings are EVM bytecode constants from bundled viem library; not malicious encoding. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Same viem EVM bytecode constants; stable false positive for this package. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Package has 219 versions and coordinates releases with @t2000/sdk at matching versions — rapid publishes reflect an automated monorepo CI pipeline, not malicious activity. | ai | |
| provenance | no-provenance | AI (provenance): Package consistently lacks Sigstore provenance; this is a best-practice gap, not a security threat, and is stable across versions for this package. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @t2000/mcp is a scoped MCP server for Sui blockchain — no plausible impersonation of 'yup' (a schema validation library). Levenshtein match is coincidental. | ai |
Versions (showing 51 of 348)
| Version | Deps | Published |
|---|---|---|
| 10.13.4 | 0 / 9 | |
| 10.13.3 | 0 / 9 | |
| 10.13.2 | 0 / 9 | |
| 10.13.1 | 0 / 9 | |
| 10.13.0 | 0 / 9 | |
| 10.12.0 | 0 / 9 | |
| 10.11.1 | 0 / 9 | |
| 10.9.0 | 0 / 9 | |
| 10.8.0 | 0 / 9 | |
| 10.7.0 | 0 / 9 | |
| 10.6.0 | 0 / 9 | |
| 10.5.0 | 0 / 9 | |
| 10.3.1 | 0 / 9 | |
| 10.3.0 | 0 / 9 | |
| 10.2.0 | 0 / 9 | |
| 10.1.2 | 0 / 9 | |
| 10.1.1 | 0 / 9 | |
| 10.1.0 | 0 / 9 | |
| 10.0.0 | 0 / 9 | |
| 9.14.0 | 0 / 9 | |
| 9.13.0 | 0 / 9 | |
| 9.12.0 | 0 / 9 | |
| 9.11.0 | 0 / 9 | |
| 9.10.0 | 0 / 9 | |
| 9.9.1 | 0 / 9 | |
| 9.9.0 | 0 / 9 | |
| 9.8.0 | 0 / 9 | |
| 9.7.1 | 0 / 9 | |
| 9.7.0 | 0 / 9 | |
| 9.6.0 | 0 / 9 | |
| 9.5.0 | 0 / 9 | |
| 9.4.0 | 0 / 9 | |
| 9.3.1 | 0 / 9 | |
| 9.3.0 | 0 / 9 | |
| 9.2.0 | 0 / 9 | |
| 9.1.0 | 0 / 9 | |
| 9.0.0 | 0 / 9 | |
| 8.2.0 | 0 / 9 | |
| 8.1.0 | 0 / 9 | |
| 8.0.2 | 0 / 9 | |
| 8.0.1 | 0 / 9 | |
| 8.0.0 | 0 / 9 | |
| 7.0.0 | 0 / 9 | |
| 6.0.0 | 0 / 9 | |
| 5.32.0 | 0 / 9 | |
| 5.31.0 | 0 / 9 | |
| 5.30.0 | 0 / 9 | |
| 5.29.0 | 0 / 9 | |
| 5.28.0 | 0 / 9 | |
| 5.27.0 | 0 / 9 | |
| 5.26.0 | 0 / 9 |
v10.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.