Skip to content
Back to search

sugar

MarketplaceWorks with Claude CodeGitHub

Sugar's plugin marketplace, currently offering the Sugar MCP server.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday

Check it deeper on your machine

It has changed since its scan on 19 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/SugarCasino/ts-sdks with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/SugarCasino/ts-sdks'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sugarcasino--ts-sdks/badge.svg)](/listings/sugarcasino--ts-sdks)

HTML

<a href="/listings/sugarcasino--ts-sdks"><img src="/api/listings/sugarcasino--ts-sdks/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install Sugar MCP for all detected coding agents with [add-mcp](https://www.npmjs.com/package/add-mcp):

npx add-mcp @sugarcasino/mcp@latest --name sugar

Add `-y` to skip the installer prompts. Restart or reload your MCP client after installation.

To configure an MCP client manually, use:

{
	"mcpServers": {
		"sugar": {
			"command": "npx",
			"args": ["-y", "@sugarcasino/mcp@latest"]
		}
	}
}

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 53 lines
  1. {
  2. "name": "sugar",
  3. "owner": {
  4. "name": "Sugar",
  5. "email": "contact@sugar.win",
  6. "url": "https://github.com/SugarCasino"
  7. },
  8. "description": "Sugar's plugin marketplace, currently offering the Sugar MCP server.",
  9. "plugins": [
  10. {
  11. "name": "sugar-mcp",
  12. "displayName": "Sugar MCP",
  13. "source": "./packages/mcp/plugin",
  14. "description": "AI agent MCP tools for Sugar provably fair on-chain Sui casino game, NFT, referral transactions.",
  15. "category": "Developer Tools",
  16. "tags": [
  17. "sugar",
  18. "sui",
  19. "mcp",
  20. "mcp-server",
  21. "agent",
  22. "ai-agent",
  23. "dapp",
  24. "sui-blockchain",
  25. "web3-gaming",
  26. "games",
  27. "casino",
  28. "casino-games",
  29. "sui-casino",
  30. "crypto-casino",
  31. "provably-fair",
  32. "on-chain",
  33. "gamblefi",
  34. "betting",
  35. "coinflip",
  36. "pvp-coinflip",
  37. "limbo",
  38. "plinko",
  39. "range",
  40. "wheel",
  41. "soccer",
  42. "pvp",
  43. "nft",
  44. "referral",
  45. "wallet",
  46. "dry-run",
  47. "unsigned-transactions",
  48. "transaction-builder",
  49. "transactions"
  50. ]
  51. }
  52. ]
  53. }
README.md · README · 125 lines
  1. # Sugar TypeScript SDKs
  2. Build Sugar transactions on Sui with the TypeScript SDK or MCP server, and render Suifrens with the React display library.
  3. ## Documentation
  4. - [Sugar SDK documentation](packages/sdk/README.md)
  5. - [Sugar MCP documentation](packages/mcp/README.md)
  6. - [Suifrens documentation](packages/suifrens-display-system/README.md)
  7. - [Sui TypeScript SDK documentation](https://sdk.mystenlabs.com/)
  8. ## Install the MCP server
  9. Install Sugar MCP for all detected coding agents with [add-mcp](https://www.npmjs.com/package/add-mcp):
  10. ```bash
  11. npx add-mcp @sugarcasino/mcp@latest --name sugar
  12. ```
  13. Add `-y` to skip the installer prompts. Restart or reload your MCP client after installation.
  14. To configure an MCP client manually, use:
  15. ```json
  16. {
  17. "mcpServers": {
  18. "sugar": {
  19. "command": "npx",
  20. "args": ["-y", "@sugarcasino/mcp@latest"]
  21. }
  22. }
  23. }
  24. ```
  25. ## Agent skills
  26. Each public npm package includes an entry under `skills/`: `sugar-sdk`, `sugar-mcp`, or `suifrens-display-system`. Compatible agents discover these entries and fetch the full instructions and references they need from `main` in the skills repository. Agent skills are not versioned with the packages. Packing the entries needs no install hook or network access.
  27. Sugar agent skills live in `SugarCasino/agent-skills`. The MCP skill explains how to install and configure `@sugarcasino/mcp`, read Sugar config, game metadata, NFTs and claimable referral amounts, and build and simulate unsigned transactions, including SweetHouse transactions.
  28. Install all Sugar skills with:
  29. ```bash
  30. npx skills add SugarCasino/agent-skills --global --yes
  31. ```
  32. Install only the MCP skill with:
  33. ```bash
  34. npx skills add SugarCasino/agent-skills --skill sugar-mcp --global --yes
  35. ```
  36. ## Packages
  37. The npm scope is `@sugarcasino`. Use it for package installation and all public imports, including subpaths. The client extension remains `sugar()` and `client.sugar`.
  38. - [`@sugarcasino/sdk`](packages/sdk/README.md) in `packages/sdk`: ESM-only TypeScript SDK for transactions involving Sugar's provably fair casino games on Sui, SweetHouse, NFTs and referrals.
  39. - [`@sugarcasino/mcp`](packages/mcp/README.md) in `packages/mcp`: MCP stdio server and MCP App for reading Sugar config, game metadata, NFTs, and referral claim amounts, plus building unsigned Sugar and SweetHouse transactions through the SDK.
  40. - [`@sugarcasino/suifrens-display-system`](packages/suifrens-display-system/README.md) in `packages/suifrens-display-system`: React components for rendering Suifrens.
  41. ## Development
  42. Run these commands from the repository root.
  43. Use `turbo` when a task needs generated files or build output. It runs the prerequisite tasks first.
  44. ### Setup
  45. Use the Node.js version specified in [`.node-version`](.node-version). GitHub Actions reads the same file through the shared pnpm setup action.
  46. ```bash
  47. pnpm install
  48. pnpm run build
  49. ```
  50. Dependency install scripts are disabled by default in `pnpm-workspace.yaml`. Review any new dependency's install or build script before approving it with `pnpm approve-builds`. Transitive dependencies cannot resolve untrusted git or tarball URLs.
  51. ### Building
  52. ```bash
  53. pnpm run build
  54. # or
  55. pnpm turbo run build
  56. ```
  57. ### Unit tests
  58. ```bash
  59. pnpm run test
  60. # or
  61. pnpm turbo run test
  62. ```
  63. ### Type checking
  64. Workspace packages inherit the strict checks in `tsconfig.shared.json`. It disables `isolatedDeclarations` because generated SDK bindings lack the required annotations and MCP relies on Zod to infer schema and handler types. SDK and MCP keep the other shared strict checks.
  65. ```bash
  66. pnpm run typecheck
  67. # or
  68. pnpm turbo run typecheck
  69. ```
  70. ### Linting
  71. This repo uses Oxlint and Oxfmt for linting and formatting.
  72. ```bash
  73. pnpm run lint
  74. ```
  75. Apply automatic fixes with:
  76. ```bash
  77. pnpm run lint:fix
  78. ```
  79. To run Oxlint and Oxfmt individually, use:
  80. ```bash
  81. pnpm run oxlint
  82. pnpm run oxfmt
  83. pnpm run oxlint:fix
  84. pnpm run oxfmt:fix
  85. ```

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.