Developer Tools

waxcreator.com

Prepares unsigned WAX blockchain transactions for creating NFT collections, templates, and mints via the waxcreator protocol.

1 endpoint10 known toolsFirst detected October 21, 2026Last detected October 21, 2026

ENDPOINT 1

https://waxcreator.com/mcp

No auth detected

MCP server metadata

Name: waxcreator
Version: 1.0.0

Capabilities

tools

Server instructions

WAXCreator mints AtomicAssets NFTs on the WAX blockchain. This server is NON-CUSTODIAL: prepare tools return an UNSIGNED transaction; nothing is minted until the creator's own WAX key signs it. Typical flow: (1) waxcreator_upload_image if you only have bytes or a URL, (2) waxcreator_prepare_mint with creator/name/image, (3) have the user approve `actions` in their wallet, OR if you control a key for that account sign `signing_digest` and call waxcreator_push_transaction. Never ask a user to paste a private key into chat. Always show the user the prepare `summary` before they sign. Backed mints lock real WAX in escrow (redeemable 1:1 by burning) — confirm the amount with the user.

Known tools 10

waxcreator_get_config

Returns which WAX network this API targets and the contract accounts it builds transactions for.

Inferred read-only

waxcreator_check_account

Shows whether the creator's account-named collection and the `waxcreator` schema exist, and whether the escrow contract is wired for backed mints.

Inferred read-only

waxcreator_prepare_mint

Builds the unsigned transaction to mint a single unique NFT into the creator's own collection (named after their account), creating the collection and `waxcreator` schema first if needed — exactly what the waxcreator.com Create NFT wizard does.

Potential side effects

waxcreator_prepare_template

Builds the unsigned transaction to create a reusable template in the creator's collection.

Potential side effects

waxcreator_prepare_template_mint

Builds the unsigned transaction to mint 1–40 copies of a template in a collection where `minter` is an authorized account.

Inferred read-only

waxcreator_prepare_backed_mint

Builds the unsigned transaction that deposits WAX into the escrow contract, which mints one backed copy of the template.

Inferred read-only

waxcreator_get_drop

Reads a drop from the drops contract.

Potential side effects

waxcreator_prepare_drop_mint

Builds the unsigned payment transfer to the drops contract that mints one NFT from a live drop, after checking time window, whitelist, and per-wallet limit.

Potential side effects

waxcreator_upload_image

Pins a PNG/JPEG/GIF/WebP/SVG (≤4MB) to IPFS and returns its CID for the `image` field.

Inferred read-only

waxcreator_push_transaction

Relays a signed transaction to WAX.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.waxcreator]
url = "https://waxcreator.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "waxcreator": {
      "type": "http",
      "url": "https://waxcreator.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: waxcreator
Remote MCP URL: https://waxcreator.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "waxcreator": {
      "url": "https://waxcreator.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "waxcreator": {
      "type": "http",
      "url": "https://waxcreator.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "waxcreator",
  "transport": "streamable-http",
  "url": "https://waxcreator.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.