Generate a standard ERC-1155 non-fungible token contract, returning its source code as a Markdown block. Customize with name, supply, burnable, and license options.
AGPL 3.0
453,386 tools. Updated 2026-08-13 19:27
"Stylus" matching MCP tools:
- Create an ERC-721 NFT smart contract source code, ready for copy-paste, with configurable burnable and enumerable options.AGPL 3.0
- Generates ERC-20 fungible token contract source code, returned as Markdown, with configurable features like burnable, permit, and flashmint.AGPL 3.0
- Make a fungible token per the ERC-20 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector
- Make a non-fungible token per the ERC-1155 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector
- Make a non-fungible token per the ERC-721 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector
- Validate Stylus Rust code for smart contracts by running cargo check to detect compilation errors and provide structured fixes with line numbers and guidance.MIT
- Retrieve Stylus documentation and code examples from the knowledge base to support development with version-aware search capabilities.MIT
- Get answers to Stylus development questions, debug code issues, or understand concepts with version-specific guidance for smart contract creation.MIT
- Generate Stylus/Rust smart contract code for Arbitrum using RAG context and version-aware generation. Supports ERC standards and custom contracts with optional tests.MIT
- Generate test cases for Stylus smart contracts to validate functionality and security using specified frameworks and test types.MIT
- Retrieve the list of writing styles supported by the DeepL API for rephrasing text, helping you choose the appropriate style for your content.MIT
- Retrieve all brand styles for the authenticated user, returning a list with basic information.MIT
- Retrieve structured workflow information for Stylus development, including step-by-step commands for build, deploy, and test operations to guide development processes.MIT
- Generate Chainlink oracle integration code for Arbitrum dApps to implement price feeds, VRF, automation, or functions with optional Stylus and frontend components.MIT
- Inspect computed CSS properties of a specific element using a CSS selector and property list. Enables real-time style debugging within Vite's HMR workflow.MIT
- Retrieve and explore available Quran recitation styles using the quran-mcp-server, enabling users to access diverse audio formats for Quranic verses.MIT
- Open the FluxInk handwriting recognition canvas. The user draws freehand strokes with a stylus, finger, or mouse. The strokes are converted by one of two model families: general recognition for handwriting, math, and chemical formulas, or structure recognition for molecular structures. Use this when the user asks to handwrite, draw, sketch, ink, scribble, or scrawl something. Use this when the user wants to draw a math equation, chemical formula, or molecular structure rather than type it. Use this when the user asks for a canvas, drawing pad, handwriting input box, or whiteboard. Use this when the user wants to convert stylus or finger drawings into recognized text or markup. Do NOT use this when the user types a question, equation, or formula in chat and just wants an answer. Do NOT use this when the user uploads or references an existing image of handwriting (call recognize_image instead). Do NOT use this when the user wants a formatted document, study sheet, or layout PDF (call create_layout instead). Do NOT use this when the user wants text rendered in a personal handwriting style (call show_style_canvas instead). Do NOT use this for conversational or informational requests that need no ink input. Do NOT re-open if a FluxInk handwriting canvas is already visible from any earlier turn. Instead instruct the user to keep drawing on the existing canvas. Only set force_new=true when the user explicitly asks for a brand new, fresh, or blank canvas. Always pass the original chat message in the prompt parameter so context is preserved after recognition. After calling, write a single short acknowledgement and do NOT describe the canvas UI.Connector