Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
OpenZeppelin Contracts (Solidity) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Generate secure, audited Solidity smart contracts from OpenZeppelin Contracts.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http openzeppelin-contracts-solidity-mcp https://mcp.openzeppelin.com/contracts/solidity/mcp
# 2 — ask your agent for something these tools do
# solidity-erc20, solidity-erc721, solidity-erc1155 and 5 more
OpenZeppelin Contracts (Solidity) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, read from the address; if the publisher says otherwise, swap that one word.
claude mcp add --scope user --transport http openzeppelin-contracts-solidity-mcp https://mcp.openzeppelin.com/contracts/solidity/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name of the contract |
| symbol | string | yes | The short symbol for the token |
| decimals | string | no | The number of decimals used to represent token amounts. Defaults to 18. |
| burnable | boolean | no | Whether token holders will be able to destroy their tokens |
| pausable | boolean | no | Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response. |
| premint | string | no | The number of tokens to premint for the deployer. |
| premintChainId | string | no | The chain ID of the network on which to premint tokens. |
| mintable | boolean | no | Whether privileged accounts will be able to create more supply or emit more tokens |
| callback | boolean | no | Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction. |
| permit | boolean | no | Whether without paying gas, token holders will be able to allow third parties to transfer from their account. |
| votes | no | Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps. | |
| flashmint | boolean | no | Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they're returned in the same transaction. |
| crossChainBridging | no | Whether to allow authorized bridge contracts to mint and burn tokens for crosschain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token c | |
| crossChainLinkAllowOverride | boolean | no | Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to "erc7786native". |
| namespacePrefix | string | no | The prefix for ERC-7201 namespace identifiers. It should be derived from the project name or a unique naming convention specific to the project. Used only if the contract includes storage variables an |
| access | no | The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileg | |
| upgradeable | no | Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with | |
| info | object | no | Metadata about the contract and author |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name of the contract |
| symbol | string | yes | The short symbol for the token |
| baseUri | string | no | A base uri for the token |
| enumerable | boolean | no | Whether to allow on-chain enumeration of all tokens or those owned by an account. Increases gas cost of transfers. |
| uriStorage | boolean | no | Allows updating token URIs for individual token IDs |
| burnable | boolean | no | Whether token holders will be able to destroy their tokens |
| pausable | boolean | no | Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response. |
| mintable | boolean | no | Whether privileged accounts will be able to create more supply or emit more tokens |
| incremental | boolean | no | Whether new tokens will be automatically assigned an incremental id |
| votes | no | Whether to keep track of individual units for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps (defaulting to block number if not specified). | |
| crossChainBridging | string | no | Whether to embed an ERC-7786 based bridge directly in the token contract, making it natively crosschain. Crosschain transfers with registered counterparts burn the token on the source chain and mint i |
| crossChainLinkAllowOverride | boolean | no | Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to "erc7786native". |
| access | no | The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileg | |
| upgradeable | no | Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with | |
| info | object | no | Metadata about the contract and author |
| namespacePrefix | string | no | The prefix for ERC-7201 namespace identifiers. It should be derived from the project name or a unique naming convention specific to the project. Used only if the contract includes storage variables an |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name of the contract |
| uri | string | yes | The location of the metadata for the token. Clients will replace any instance of {id} in this string with the tokenId. |
| burnable | boolean | no | Whether token holders will be able to destroy their tokens |
| pausable | boolean | no | Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response. |
| mintable | boolean | no | Whether privileged accounts will be able to create more supply or emit more tokens |
| supply | boolean | no | Whether to keep track of total supply of tokens |
| updatableUri | boolean | no | Whether privileged accounts will be able to set a new URI for all token types |
| crossChainBridging | string | no | Whether to embed an ERC-7786 based bridge directly in the token contract, making it natively crosschain. Crosschain transfers with registered counterparts burn the tokens on the source chain and mint |
| crossChainLinkAllowOverride | boolean | no | Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to "erc7786native". |
| access | no | The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileg | |
| upgradeable | no | Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with | |
| info | object | no | Metadata about the contract and author |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name of the contract |
| symbol | string | yes | The short symbol for the token |
| decimals | string | no | The number of decimals used to represent token amounts. Defaults to 18. |
| burnable | boolean | no | Whether token holders will be able to destroy their tokens |
| pausable | boolean | no | Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response. |
| premint | string | no | The number of tokens to premint for the deployer. |
| premintChainId | string | no | The chain ID of the network on which to premint tokens. |
| mintable | boolean | no | Whether privileged accounts will be able to create more supply or emit more tokens |
| callback | boolean | no | Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction. |
| permit | boolean | no | Whether without paying gas, token holders will be able to allow third parties to transfer from their account. |
| votes | no | Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps. | |
| flashmint | boolean | no | Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they're returned in the same transaction. |
| crossChainBridging | no | Whether to allow authorized bridge contracts to mint and burn tokens for crosschain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token c | |
| crossChainLinkAllowOverride | boolean | no | Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to "erc7786native". |
| namespacePrefix | string | no | The prefix for ERC-7201 namespace identifiers. It should be derived from the project name or a unique naming convention specific to the project. Used only if the contract includes storage variables an |
| access | no | The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileg | |
| info | object | no | Metadata about the contract and author |
| restrictions | no | Whether to restrict certain users from transferring tokens, either via allowing or blocking them. This feature is experimental, not audited and is subject to change. | |
| freezable | boolean | no | Whether authorized accounts can freeze and unfreeze accounts for regulatory or security purposes. This feature is experimental, not audited and is subject to change. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name of the contract |
| symbol | string | yes | The short symbol for the token |
| decimals | string | no | The number of decimals used to represent token amounts. Defaults to 18. |
| burnable | boolean | no | Whether token holders will be able to destroy their tokens |
| pausable | boolean | no | Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response. |
| premint | string | no | The number of tokens to premint for the deployer. |
| premintChainId | string | no | The chain ID of the network on which to premint tokens. |
| mintable | boolean | no | Whether privileged accounts will be able to create more supply or emit more tokens |
| callback | boolean | no | Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction. |
| permit | boolean | no | Whether without paying gas, token holders will be able to allow third parties to transfer from their account. |
| votes | no | Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps. | |
| flashmint | boolean | no | Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they're returned in the same transaction. |
| crossChainBridging | no | Whether to allow authorized bridge contracts to mint and burn tokens for crosschain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token c | |
| crossChainLinkAllowOverride | boolean | no | Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to "erc7786native". |
| namespacePrefix | string | no | The prefix for ERC-7201 namespace identifiers. It should be derived from the project name or a unique naming convention specific to the project. Used only if the contract includes storage variables an |
| access | no | The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileg | |
| info | object | no | Metadata about the contract and author |
| restrictions | no | Whether to restrict certain users from transferring tokens, either via allowing or blocking them. This feature is experimental, not audited and is subject to change. | |
| freezable | boolean | no | Whether authorized accounts can freeze and unfreeze accounts for regulatory or security purposes. This feature is experimental, not audited and is subject to change. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name of the account contract |
| signatureValidation | no | Whether to implement the ERC-1271 standard for validating signatures. This is useful for the account to verify signatures. | |
| ERC721Holder | boolean | no | Whether to implement the onERC721Received function to allow the account to receive ERC721 tokens. |
| ERC1155Holder | boolean | no | Whether to implement the onERC1155Received function to allow the account to receive ERC1155 tokens. |
| signer | no | Defines the signature verification algorithm used by the account to verify user operations. Options: - ECDSA: Standard Ethereum signature validation using secp256k1, validates signatures again | |
| batchedExecution | boolean | no | Whether to implement a minimal batching interface for the account to allow multiple operations to be executed in a single transaction following the ERC-7821 standard. |
| ERC7579Modules | no | Whether to implement the ERC-7579 compatibility to enable functionality on the account with modules. | |
| info | object | no | Metadata about the contract and author |
| upgradeable | no | Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name of the contract |
| delay | string | yes | The delay since proposal is created until voting starts, default is "1 day" |
| period | string | yes | The length of period during which people can cast their vote, default is "1 week" |
| votes | no | The type of voting to use | |
| clockMode | no | The clock mode used by the voting token. For Governor, this must be chosen to match what the ERC20 or ERC721 voting token uses. | |
| timelock | no | The type of timelock to use | |
| blockTime | number | no | The block time of the chain in seconds, default is 12 |
| decimals | number | no | The number of decimals to use for the contract, default is 18 for ERC20Votes and 0 for ERC721Votes (because it does not apply to ERC721Votes) |
| proposalThreshold | string | no | Minimum number of votes an account must have to create a proposal, default is 0. |
| quorumMode | no | The type of quorum mode to use | |
| quorumPercent | number | no | The percent required, in cases of quorumMode equals percent |
| quorumAbsolute | string | no | The absolute quorum required, in cases of quorumMode equals absolute |
| storage | boolean | no | Enable storage of proposal details and enumerability of proposals |
| settings | boolean | no | Allow governance to update voting settings (delay, period, proposal threshold) |
| crossChainExecution | boolean | no | Whether passed proposals can relay execution to other chains through ERC-7786 gateways. Requires a CrosschainRemoteExecutor contract, controlled by this governor, deployed on each target chain. The ga |
| upgradeable | no | Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with | |
| info | object | no | Metadata about the contract and author |
Make a custom smart contract. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name of the contract |
| pausable | boolean | no | Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response. |
| access | no | The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileg | |
| upgradeable | no | Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with | |
| info | object | no | Metadata about the contract and author |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OpenZeppelin Contracts (Solidity) or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.6.4.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish OpenZeppelin Contracts (Solidity) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.