Make a stablecoin token that uses the ERC-20 standard. Experimental, some features are not audited and are subject to change.
Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
Connector
458,314 tools. Updated 2026-08-16 06:47
"OpenZeppelin" matching MCP tools:
- Design a non-security token strategy for an autonomous agent. Returns a deployable spec: symbol, supply, distribution allocations summing to 100, OpenZeppelin contract templates (ERC20, ERC4626, ERC721), fair-launch defaults, a six-criterion non-security checklist, an estimated Base deploy cost, and a curated risks list covering Sybil, LP rug, and key-compromise vectors.Connector
- 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 contract to implement governance, such as for a DAO. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector
- 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
Matching MCP Servers
- Alicense-qualityDmaintenanceEnables users to generate and retrieve secure, audited smart contract templates from OpenZeppelin including ERC20, ERC721, ERC1155 tokens, access control, governance, and finance contracts through natural language prompts.MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol (MCP) server that allows AI agents to generate smart contracts using OpenZeppelin Contracts libraries.26358293AGPL 3.0
Matching MCP Connectors
The OpenZeppelin Stylus Contracts MCP server generates secure smart contracts for the Arbitrum Stylus environment using OpenZeppelin templates, including ERC-20, ERC-721, and ERC-1155 standards. It automatically validates generated code against OpenZeppelin's security and style rules, enforcing best practices for imports, modifiers, naming conventions, and security checks to prevent common vulnerabilities. The server integrates with AI development tools like Cursor, Claude, Gemini, Windsurf, and VS Code to enable AI-assisted, production-ready smart contract development.
The OpenZeppelin Solidity Contracts MCP server integrates OpenZeppelin's security and style rules into AI-driven development workflows, enabling AI assistants to generate safe, correct, and production-ready smart contracts. It automatically validates generated code against OpenZeppelin standards (including imports, modifiers, naming conventions, and security checks) and supports various contract types including ERC-20, ERC-721, ERC-1155, Stablecoins, RWA, Governor, and Account contracts through prompt-driven workflows.
- 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
- Make a non-fungible token per the Non-Fungible Token Standard, compatible with SEP-50, similar to ERC-721. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector
- Make a tokenized vault that issues Fungible Token shares for an underlying asset, similar to ERC-4626. 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 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-721 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector
- Make a real-world asset token that uses the ERC-20 standard. Experimental, some features are not audited and are subject to change. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector
- Make an account contract that follows the ERC-4337 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector
- Make a custom smart contract. 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 multi-signature smart contract, requiring a quorum of registered signers to approve and collectively execute transactions. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector
- Make a contract to implement governance, such as for a DAO. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector
- Make a vesting smart contract that manages the gradual release of ERC-20 tokens to a designated beneficiary based on a predefined vesting schedule. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector
- Make a fungible token per the Fungible Token Standard, compatible with SEP-41, similar to ERC-20. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.Connector