Smeltr Token 2022

What Smeltr Token-2022 MCP server does

Smeltr Token-2022 MCP server exposes the project's Token-2022 validation engine to MCP-compatible AI assistants. Its purpose is configuration review rather than transaction execution or wallet management. The provided description identifies it as read-only and states that it does not require private keys or an RPC connection.

The validator covers configuration areas associated with several Token-2022 extensions: transfer fees, non-transferability, permanent delegates, and Arweave metadata. In practical terms, it is intended for checking whether a proposed token setup matches the supported rules before continuing with a deployment workflow.

Smeltr itself is described as non-custodial deployment infrastructure for Solana. Its broader deployment flow builds transaction instructions for a wallet to sign. The MCP portion is specifically presented as the validation interface, so it should not be treated as a signing service or a replacement for a wallet.

How it works

The server runs as an MCP process and makes Smeltr's validation functionality available to clients such as Claude Desktop and Cursor. An assistant can send a Token-2022 configuration for validation and use the returned result during planning or review. The supplied material does not document the individual MCP tool names, input schema, output schema, or validation error format.

Because validation is read-only, the server can be used before a transaction is constructed or signed. No Solana RPC endpoint is needed for the stated validation use case, and the supplied description does not identify any credential or key requirement.

Setup and configuration

The repository documents the MCP launch command as:

npx -y @smeltr/mcp-server

The -y flag allows non-interactive execution through npm's package runner. The README separately documents environment variables for the full Smeltr web application, including database and session settings, but it does not state that those values are required by the MCP validation server. Do not assume the web application's database configuration is needed for this read-only MCP use case.

Tools and capabilities

The Smeltr Token-2022 MCP server supports validation for:

• Transfer fee configurations
• Non-transferable, or soulbound, token configurations
• Permanent delegate configurations
• Arweave metadata configurations

These capabilities make the server relevant to agents that need to review Solana token settings before deployment. The available material does not support claims about mint creation, transaction submission, wallet signing, account lookup, balances, or live-chain inspection.

Limitations and notes

Smeltr Token-2022 MCP server is described as read-only. It does not hold signing keys, sign transactions, or use an RPC endpoint according to the supplied description. Any deployment action remains outside the documented MCP validation role and requires the broader Smeltr workflow or another Solana tool.

The README names Claude Desktop, Cursor, and other assistants as supported MCP clients, but it does not provide client-specific configuration snippets. It also does not list a license, detailed API schema, version compatibility requirements, or a complete catalog of validation rules. Those details should be confirmed in the project's MCP documentation before building a client integration.