24 tools from the Contracts MCP Server, categorised by risk level.
View the Contracts policy →cairo-custom Make a custom smart contract.
Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk. 2/5 cairo-erc1155 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 n... 2/5 cairo-erc20 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 wri... 2/5 cairo-erc721 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 no... 2/5 cairo-governor 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.... 2/5 cairo-vesting Make a vesting smart contract that manages the gradual release of ERC-20 tokens to a designated beneficiary based on a predefined vesting schedule.... 2/5 erc7984 Make a confidential fungible token in Solidity according to the ERC-7984 standard, similar to ERC-20 but with confidentiality.
Returns the source ... 2/5 solidity-account Make an account contract that follows the ERC-4337 standard.
Returns the source code of the generated contract, formatted in a Markdown code block... 2/5 solidity-custom Make a custom smart contract.
Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk. 2/5 solidity-erc1155 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 n... 3/5 solidity-erc20 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 wri... 2/5 solidity-erc721 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 no... 2/5 solidity-governor 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.... 2/5 solidity-rwa 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 so... 2/5 solidity-stablecoin Make a stablecoin token that uses the ERC-20 standard. Experimental, some features are not audited and are subject to change.
Returns the source c... 2/5 stellar-fungible Make a fungible token per the Fungible Token Standard, compatible with SEP-41, similar to ERC-20.
Returns the source code of the generated contrac... 2/5 stellar-non-fungible 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 generate... 2/5 stellar-stablecoin Make a stablecoin that uses Fungible Token Standard, compatible with SEP-41.
Returns the source code of the generated contract, formatted in a Mar... 2/5 stylus-erc1155 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 n... 2/5 stylus-erc20 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 wri... 2/5 stylus-erc721 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 no... 2/5 uniswap-hooks Make a Uniswap v4 hook contract using the OpenZeppelin Uniswap Hooks library.
Returns the source code of the generated contract, formatted in a Ma... 3/5 cairo-account Make a custom smart contract that represents an account that can be deployed and interacted with other contracts, and can be extended to implement ... 3/5 cairo-multisig Make a multi-signature smart contract, requiring a quorum of registered signers to approve and collectively execute transactions.
Returns the sour... 3/5 The Contracts MCP server exposes 24 tools across 2 categories: Write, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Contracts server.
Contracts tools are categorised as Write (22), Execute (2). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept