SINAI STANDARD

MCP Server

Model Context Protocol server for AI-powered token management

MCP Server

The Sinai Standard MCP server exposes regulated token operations as tools that any Model Context Protocol-compatible AI agent can call — including Claude, GPT, and custom LLM agents.

Installation

npm install -g @sinai-standard/mcp-server

Claude Desktop Configuration

Add the following to your Claude Desktop config file (claude_desktop_config.json):

{
  "mcpServers": {
    "sinai-standard": {
      "command": "sinai-mcp",
      "args": ["--network", "devnet"],
      "env": {
        "SINAI_PRIVATE_KEY": "your-base58-private-key",
        "SINAI_RPC_URL": "https://api.devnet.solana.com"
      }
    }
  }
}

For mainnet, change --network to mainnet-beta and update SINAI_RPC_URL to your mainnet RPC endpoint.

Available Tools

The MCP server exposes the following tools to the AI agent:

Token Operations

ToolParametersDescription
create_tokenname, symbol, decimals, initialSupplyCreate a new compliant Token-2022 token with hooks
mint_tokensmint, destination, amountMint tokens to a KYC-approved wallet
transfer_tokensmint, from, to, amountTransfer tokens (enforces all hook rules)
burn_tokensmint, source, amountBurn tokens from a wallet
get_token_infomintGet token metadata, supply, and active hooks

Allowlist Management

ToolParametersDescription
add_to_allowlistmint, walletAdd a wallet to the token's KYC allowlist
remove_from_allowlistmint, walletRemove a wallet from the allowlist
check_allowlistmint, walletCheck if a wallet is on the allowlist
get_allowlistmintList all wallets on the allowlist

Compliance Queries

ToolParametersDescription
get_compliance_statusmint, walletFull compliance check: allowlist, hold period, balance cap
get_hold_periodmintGet the token's hold period configuration
get_tax_configmintGet the token's transfer tax configuration
get_max_balancemintGet the token's maximum balance cap

Available Resources

The server also exposes read-only resources that agents can query:

Resource URIDescription
sinai://token/{mint}Token metadata and configuration
sinai://allowlist/{mint}Current allowlist for a token
sinai://compliance/{mint}/{wallet}Compliance status for a specific wallet
sinai://networkCurrent network and connection info

Example Conversation

Once configured, an AI agent can manage tokens through natural language:

User: Create a new compliance token called "RegFund" with symbol RGF, 6 decimals, and an initial supply of 1,000,000.

Agent: I'll create the token with the specified parameters.

Tool call: create_token
  name: "RegFund"
  symbol: "RGF"
  decimals: 6
  initialSupply: 1000000

Agent: The token "RegFund" (RGF) has been created. Mint address: 7xKp...3mNq. It has KYC allowlist and transfer tax hooks enabled.

User: Add wallet 9aB4...xY2z to the allowlist.

Agent: Done — wallet 9aB4...xY2z is now on the KYC allowlist for RGF and can receive transfers.

Environment Variables

VariableRequiredDescription
SINAI_PRIVATE_KEYYesBase58-encoded private key for the issuer wallet
SINAI_RPC_URLNoCustom RPC endpoint (defaults to public devnet)
SINAI_NETWORKNoNetwork override: devnet or mainnet-beta
SINAI_LOG_LEVELNoLogging verbosity: error, warn, info, debug

Important: Never commit your private key to version control. Use environment variables or a secrets manager.

Troubleshooting

"Tool not found" errors

Ensure the MCP server is running and the config path is correct. Restart Claude Desktop after modifying the configuration.

Transaction failures

Most transaction failures are compliance-related — the on-chain hooks are working as intended:

  • "Wallet not on allowlist" — Call add_to_allowlist before transferring tokens
  • "Hold period not met" — The recipient's hold period has not elapsed since their last received transfer
  • "Balance would exceed maximum" — The transfer would push the recipient over the maxBalance cap
  • "Insufficient funds" — The source wallet does not have enough tokens

Connection issues

If the server cannot connect to the Solana network:

  1. Check that SINAI_RPC_URL is valid and reachable
  2. Ensure your RPC provider supports Token-2022 methods
  3. For mainnet, verify your RPC plan has sufficient rate limits

On this page