OpenZeppelin Solidity Contracts MCP · OpenZeppelin

Operational

Unclaimed — claim this pagedeveloper-tools Streamable HTTP2025-06-18Open — no auth

https://mcp.openzeppelin.com/contracts/solidity/mcp Docs

Badge

100%

Availability · 30 days · 1107 checks

109 ms

Latency (last observation)

rev 1

Contract

42days

Schema stable

0

Incidents · 30 days

Aug 6, 2026

Observed since

Availability — last 30 days

No failures Some failures Mostly failing Auth required No observations

Last observed 24 min ago by MCP Tools Edge Scanner · scheduled every 30 min

Server version changed Informational Sep 9, 2026 — 3:20 PM

Server reports version 0.7.1 (was 0.7.0).

Verifiedinitialize returned serverInfo.version 0.7.1.

InterpretationVersion changes often accompany contract or behavior changes; drift detection will confirm.

Observed by MCP Tools Edge Scanner

Latency recovered below 1,000 ms Informational Sep 6, 2026 — 11:45 PM

Latest observation: 784 ms.

VerifiedObserved initialization latency: 784 ms.

Observed by MCP Tools Edge Scanner

Latency crossed above 1,000 ms Informational Sep 6, 2026 — 7:25 AM

Three consecutive observations exceeded 1,000 ms (latest: 1117 ms).

VerifiedObserved initialization latency: 1117 ms.

InterpretationClients may experience slow tool discovery and responses.

Observed by MCP Tools Edge Scanner

Latency recovered below 1,000 ms Informational Sep 4, 2026 — 3:50 PM

Latest observation: 413 ms.

VerifiedObserved initialization latency: 413 ms.

Observed by MCP Tools Edge Scanner

Latency crossed above 1,000 ms Informational Sep 3, 2026 — 3:20 PM

Three consecutive observations exceeded 1,000 ms (latest: 1016 ms).

VerifiedObserved initialization latency: 1016 ms.

InterpretationClients may experience slow tool discovery and responses.

Observed by MCP Tools Edge Scanner

Latency recovered below 1,000 ms Informational Sep 2, 2026 — 1:00 AM

Latest observation: 409 ms.

VerifiedObserved initialization latency: 409 ms.

Observed by MCP Tools Edge Scanner

Server version changed Informational Sep 1, 2026 — 6:05 PM

Server reports version 0.7.0 (was 0.6.5).

Verifiedinitialize returned serverInfo.version 0.7.0.

InterpretationVersion changes often accompany contract or behavior changes; drift detection will confirm.

Observed by MCP Tools Edge Scanner

Latency crossed above 1,000 ms Informational Sep 1, 2026 — 12:45 PM

Three consecutive observations exceeded 1,000 ms (latest: 1421 ms).

VerifiedObserved initialization latency: 1421 ms.

InterpretationClients may experience slow tool discovery and responses.

Observed by MCP Tools Edge Scanner

Latency recovered below 1,000 ms Informational Aug 30, 2026 — 8:40 AM

Latest observation: 464 ms.

VerifiedObserved initialization latency: 464 ms.

Observed by MCP Tools Edge Scanner

Latency crossed above 1,000 ms Informational Aug 29, 2026 — 4:40 AM

Three consecutive observations exceeded 1,000 ms (latest: 1103 ms).

VerifiedObserved initialization latency: 1103 ms.

InterpretationClients may experience slow tool discovery and responses.

Observed by MCP Tools Edge Scanner

Latency recovered below 1,000 ms Informational Aug 27, 2026 — 6:15 AM

Latest observation: 316 ms.

VerifiedObserved initialization latency: 316 ms.

Observed by MCP Tools Edge Scanner

Server version changed Informational Aug 25, 2026 — 9:25 PM

Server reports version 0.6.5 (was 0.6.4).

Verifiedinitialize returned serverInfo.version 0.6.5.

InterpretationVersion changes often accompany contract or behavior changes; drift detection will confirm.

Observed by MCP Tools Edge Scanner

Latency crossed above 1,000 ms Informational Aug 25, 2026 — 1:10 PM

Three consecutive observations exceeded 1,000 ms (latest: 1267 ms).

VerifiedObserved initialization latency: 1267 ms.

InterpretationClients may experience slow tool discovery and responses.

Observed by MCP Tools Edge Scanner

Latency recovered below 1,000 ms Informational Aug 24, 2026 — 6:25 PM

Latest observation: 789 ms.

VerifiedObserved initialization latency: 789 ms.

Observed by MCP Tools Edge Scanner

Latency crossed above 1,000 ms Informational Aug 24, 2026 — 1:10 AM

Three consecutive observations exceeded 1,000 ms (latest: 1257 ms).

VerifiedObserved initialization latency: 1257 ms.

InterpretationClients may experience slow tool discovery and responses.

Observed by MCP Tools Edge Scanner

Latency recovered below 1,000 ms Informational Aug 23, 2026 — 4:45 AM

Latest observation: 795 ms.

VerifiedObserved initialization latency: 795 ms.

Observed by MCP Tools Edge Scanner

Latency crossed above 1,000 ms Informational Aug 22, 2026 — 1:35 PM

Three consecutive observations exceeded 1,000 ms (latest: 1022 ms).

VerifiedObserved initialization latency: 1022 ms.

InterpretationClients may experience slow tool discovery and responses.

Observed by MCP Tools Edge Scanner

Server version changed Informational Aug 17, 2026 — 11:15 PM

Server reports version 0.6.4 (was 0.6.3).

Verifiedinitialize returned serverInfo.version 0.6.4.

InterpretationVersion changes often accompany contract or behavior changes; drift detection will confirm.

Observed by MCP Tools Edge Scanner

Server version changed Informational Aug 10, 2026 — 4:25 PM

Server reports version 0.6.3 (was 0.6.2).

Verifiedinitialize returned serverInfo.version 0.6.3.

InterpretationVersion changes often accompany contract or behavior changes; drift detection will confirm.

Observed by MCP Tools Edge Scanner

Descriptions or metadata changed Informational Aug 10, 2026 — 4:25 PM

5 description/metadata changes; the functional contract is unchanged (hash sha256:9c303d7088cd1e3f…).

VerifiedDescriptions or metadata for solidity-erc1155 changed.

InterpretationNo structural change. Wording changes can still influence model tool selection.

Path	Change	Classification	Detail
tools.solidity-erc1155	description changed	Informational	Descriptions or metadata for `solidity-erc1155` changed. No structural change. Wording changes can still influence model tool selection.
tools.solidity-erc20	description changed	Informational	Descriptions or metadata for `solidity-erc20` changed. No structural change. Wording changes can still influence model tool selection.
tools.solidity-erc721	description changed	Informational	Descriptions or metadata for `solidity-erc721` changed. No structural change. Wording changes can still influence model tool selection.
tools.solidity-rwa	description changed	Informational	Descriptions or metadata for `solidity-rwa` changed. No structural change. Wording changes can still influence model tool selection.
tools.solidity-stablecoin	description changed	Informational	Descriptions or metadata for `solidity-stablecoin` changed. No structural change. Wording changes can still influence model tool selection.

Observed by MCP Tools Edge Scanner

Server version changed Informational Aug 7, 2026 — 3:06 PM

Server reports version 0.6.2 (was 0.6.1).

Verifiedinitialize returned serverInfo.version 0.6.2.

InterpretationVersion changes often accompany contract or behavior changes; drift detection will confirm.

Observed by MCP Tools Edge Scanner

Server version changed Informational Aug 6, 2026 — 2:40 PM

Server reports version 0.6.1 (was 0.6.0).

Verifiedinitialize returned serverInfo.version 0.6.1.

InterpretationVersion changes often accompany contract or behavior changes; drift detection will confirm.

Observed by MCP Tools Edge Scanner

Baseline captured Aug 6, 2026 — 5:10 AM

8 tools, 8 resources, 0 prompts observed. Future observations will identify outages, recoveries, protocol changes, and contract drift from this state.

VerifiedCanonical contract hash sha256:9c303d7088cd1e3f… computed from the normalized capability inventory.

Raw event details

{
  "contractHash": "sha256:9c303d7088cd1e3f50ab0fcc1ab901079fdeae55449c86a4820074df5a17911c"
}

Observed by MCP Tools Edge Scanner

Advertised capabilities

Tools · 8 Resources · 8 Prompts Logging Completions Experimental

Tools 8

solidity-erc20 18 params · 2 required Make a fungible token per the ERC-20 standard. Returns the source code of the generated contract, formatted i…

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.

Input schema

Parameter	Type	Description & constraints
name*	string	The name of the contract
symbol*	string	The short symbol for the token
decimals	string	The number of decimals used to represent token amounts. Defaults to 18.
burnable	boolean	Whether token holders will be able to destroy their tokens
pausable	boolean	Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
premint	string	The number of tokens to premint for the deployer.
premintChainId	string	The chain ID of the network on which to premint tokens.
mintable	boolean	Whether privileged accounts will be able to create more supply or emit more tokens
callback	boolean	Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.
permit	boolean	Whether without paying gas, token holders will be able to allow third parties to transfer from their account.
votes	string \| string	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	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	string \| string \| string	Whether to allow authorized bridge contracts to mint and burn tokens for cross-chain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token contract, or to use the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.
crossChainLinkAllowOverride	boolean	Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to "erc7786native".
namespacePrefix	string	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 and upgradeability is enabled. Default is "myProject".
access	string \| string \| string	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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.
upgradeable	string \| string	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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.
info	object	Metadata about the contract and author
info.securityContact	string	Email where people can contact you to report security issues. Will only be visible if contract source code is verified.
info.license	string	The license used by the contract, default is "MIT"

Raw schema JSON

solidity-erc20 — raw

{
  "name": "solidity-erc20",
  "description": "Make a fungible token per the ERC-20 standard.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "symbol": {
        "type": "string",
        "description": "The short symbol for the token"
      },
      "decimals": {
        "description": "The number of decimals used to represent token amounts. Defaults to 18.",
        "type": "string"
      },
      "burnable": {
        "description": "Whether token holders will be able to destroy their tokens",
        "type": "boolean"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "premint": {
        "description": "The number of tokens to premint for the deployer.",
        "type": "string"
      },
      "premintChainId": {
        "description": "The chain ID of the network on which to premint tokens.",
        "type": "string"
      },
      "mintable": {
        "description": "Whether privileged accounts will be able to create more supply or emit more tokens",
        "type": "boolean"
      },
      "callback": {
        "description": "Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.",
        "type": "boolean"
      },
      "permit": {
        "description": "Whether without paying gas, token holders will be able to allow third parties to transfer from their account.",
        "type": "boolean"
      },
      "votes": {
        "description": "Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps.",
        "anyOf": [
          {
            "type": "string",
            "const": "blocknumber"
          },
          {
            "type": "string",
            "const": "timestamp"
          }
        ]
      },
      "flashmint": {
        "description": "Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they&#39;re returned in the same transaction.",
        "type": "boolean"
      },
      "crossChainBridging": {
        "description": "Whether to allow authorized bridge contracts to mint and burn tokens for cross-chain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token contract, or to use the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "custom"
              },
              {
                "type": "string",
                "const": "erc7786native"
              }
            ]
          },
          {
            "type": "string",
            "const": "superchain"
          }
        ]
      },
      "crossChainLinkAllowOverride": {
        "description": "Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to \"erc7786native\".",
        "type": "boolean"
      },
      "namespacePrefix": {
        "description": "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 and upgradeability is enabled. Default is \"myProject\".",
        "type": "string"
      },
      "access": {
        "description": "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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "upgradeable": {
        "description": "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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      }
    },
    "required": [
      "name",
      "symbol"
    ]
  }
}

solidity-erc721 16 params · 2 required Make a non-fungible token per the ERC-721 standard. Returns the source code of the generated contract, format…

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.

Input schema

Parameter	Type	Description & constraints
name*	string	The name of the contract
symbol*	string	The short symbol for the token
baseUri	string	A base uri for the token
enumerable	boolean	Whether to allow on-chain enumeration of all tokens or those owned by an account. Increases gas cost of transfers.
uriStorage	boolean	Allows updating token URIs for individual token IDs
burnable	boolean	Whether token holders will be able to destroy their tokens
pausable	boolean	Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
mintable	boolean	Whether privileged accounts will be able to create more supply or emit more tokens
incremental	boolean	Whether new tokens will be automatically assigned an incremental id
votes	string \| string	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	Whether to embed an ERC-7786 based bridge directly in the token contract, making it natively crosschain. Cross-chain transfers with registered counterparts burn the token on the source chain and mint it on the destination chain. If also using incremental token ids, mint only on a single chain and link counterparts without minting, otherwise colliding ids can strand bridged tokens.
crossChainLinkAllowOverride	boolean	Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to "erc7786native".
access	string \| string \| string	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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.
upgradeable	string \| string	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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.
info	object	Metadata about the contract and author
info.securityContact	string	Email where people can contact you to report security issues. Will only be visible if contract source code is verified.
info.license	string	The license used by the contract, default is "MIT"
namespacePrefix	string	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 and upgradeability is enabled. Default is "myProject".

Raw schema JSON

solidity-erc721 — raw

{
  "name": "solidity-erc721",
  "description": "Make a non-fungible token per the ERC-721 standard.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "symbol": {
        "type": "string",
        "description": "The short symbol for the token"
      },
      "baseUri": {
        "description": "A base uri for the token",
        "type": "string"
      },
      "enumerable": {
        "description": "Whether to allow on-chain enumeration of all tokens or those owned by an account. Increases gas cost of transfers.",
        "type": "boolean"
      },
      "uriStorage": {
        "description": "Allows updating token URIs for individual token IDs",
        "type": "boolean"
      },
      "burnable": {
        "description": "Whether token holders will be able to destroy their tokens",
        "type": "boolean"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "mintable": {
        "description": "Whether privileged accounts will be able to create more supply or emit more tokens",
        "type": "boolean"
      },
      "incremental": {
        "description": "Whether new tokens will be automatically assigned an incremental id",
        "type": "boolean"
      },
      "votes": {
        "description": "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).",
        "anyOf": [
          {
            "type": "string",
            "const": "blocknumber"
          },
          {
            "type": "string",
            "const": "timestamp"
          }
        ]
      },
      "crossChainBridging": {
        "description": "Whether to embed an ERC-7786 based bridge directly in the token contract, making it natively crosschain. Cross-chain transfers with registered counterparts burn the token on the source chain and mint it on the destination chain. If also using incremental token ids, mint only on a single chain and link counterparts without minting, otherwise colliding ids can strand bridged tokens.",
        "type": "string",
        "const": "erc7786native"
      },
      "crossChainLinkAllowOverride": {
        "description": "Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to \"erc7786native\".",
        "type": "boolean"
      },
      "access": {
        "description": "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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "upgradeable": {
        "description": "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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      },
      "namespacePrefix": {
        "description": "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 and upgradeability is enabled. Default is \"myProject\".",
        "type": "string"
      }
    },
    "required": [
      "name",
      "symbol"
    ]
  }
}

solidity-erc1155 12 params · 2 required Make a non-fungible token per the ERC-1155 standard. Returns the source code of the generated contract, forma…

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.

Input schema

Parameter	Type	Description & constraints
name*	string	The name of the contract
uri*	string	The location of the metadata for the token. Clients will replace any instance of {id} in this string with the tokenId.
burnable	boolean	Whether token holders will be able to destroy their tokens
pausable	boolean	Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
mintable	boolean	Whether privileged accounts will be able to create more supply or emit more tokens
supply	boolean	Whether to keep track of total supply of tokens
updatableUri	boolean	Whether privileged accounts will be able to set a new URI for all token types
crossChainBridging	string	Whether to embed an ERC-7786 based bridge directly in the token contract, making it natively crosschain. Cross-chain transfers with registered counterparts burn the tokens on the source chain and mint them on the destination chain.
crossChainLinkAllowOverride	boolean	Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to "erc7786native".
access	string \| string \| string	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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.
upgradeable	string \| string	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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.
info	object	Metadata about the contract and author
info.securityContact	string	Email where people can contact you to report security issues. Will only be visible if contract source code is verified.
info.license	string	The license used by the contract, default is "MIT"

Raw schema JSON

solidity-erc1155 — raw

{
  "name": "solidity-erc1155",
  "description": "Make a non-fungible token per the ERC-1155 standard.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "uri": {
        "type": "string",
        "description": "The location of the metadata for the token. Clients will replace any instance of {id} in this string with the tokenId."
      },
      "burnable": {
        "description": "Whether token holders will be able to destroy their tokens",
        "type": "boolean"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "mintable": {
        "description": "Whether privileged accounts will be able to create more supply or emit more tokens",
        "type": "boolean"
      },
      "supply": {
        "description": "Whether to keep track of total supply of tokens",
        "type": "boolean"
      },
      "updatableUri": {
        "description": "Whether privileged accounts will be able to set a new URI for all token types",
        "type": "boolean"
      },
      "crossChainBridging": {
        "description": "Whether to embed an ERC-7786 based bridge directly in the token contract, making it natively crosschain. Cross-chain transfers with registered counterparts burn the tokens on the source chain and mint them on the destination chain.",
        "type": "string",
        "const": "erc7786native"
      },
      "crossChainLinkAllowOverride": {
        "description": "Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to \"erc7786native\".",
        "type": "boolean"
      },
      "access": {
        "description": "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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "upgradeable": {
        "description": "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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      }
    },
    "required": [
      "name",
      "uri"
    ]
  }
}

solidity-stablecoin 19 params · 2 required Make a stablecoin token that uses the ERC-20 standard. Experimental, some features are not audited and are sub…

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.

Input schema

Parameter	Type	Description & constraints
name*	string	The name of the contract
symbol*	string	The short symbol for the token
decimals	string	The number of decimals used to represent token amounts. Defaults to 18.
burnable	boolean	Whether token holders will be able to destroy their tokens
pausable	boolean	Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
premint	string	The number of tokens to premint for the deployer.
premintChainId	string	The chain ID of the network on which to premint tokens.
mintable	boolean	Whether privileged accounts will be able to create more supply or emit more tokens
callback	boolean	Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.
permit	boolean	Whether without paying gas, token holders will be able to allow third parties to transfer from their account.
votes	string \| string	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	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	string \| string \| string	Whether to allow authorized bridge contracts to mint and burn tokens for cross-chain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token contract, or to use the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.
crossChainLinkAllowOverride	boolean	Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to "erc7786native".
namespacePrefix	string	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 and upgradeability is enabled. Default is "myProject".
access	string \| string \| string	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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.
info	object	Metadata about the contract and author
info.securityContact	string	Email where people can contact you to report security issues. Will only be visible if contract source code is verified.
info.license	string	The license used by the contract, default is "MIT"
restrictions	boolean \| string \| string	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	Whether authorized accounts can freeze and unfreeze accounts for regulatory or security purposes. This feature is experimental, not audited and is subject to change.

Raw schema JSON

solidity-stablecoin — raw

{
  "name": "solidity-stablecoin",
  "description": "Make a stablecoin token that uses the ERC-20 standard. Experimental, some features are not audited and are subject to change.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "symbol": {
        "type": "string",
        "description": "The short symbol for the token"
      },
      "decimals": {
        "description": "The number of decimals used to represent token amounts. Defaults to 18.",
        "type": "string"
      },
      "burnable": {
        "description": "Whether token holders will be able to destroy their tokens",
        "type": "boolean"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "premint": {
        "description": "The number of tokens to premint for the deployer.",
        "type": "string"
      },
      "premintChainId": {
        "description": "The chain ID of the network on which to premint tokens.",
        "type": "string"
      },
      "mintable": {
        "description": "Whether privileged accounts will be able to create more supply or emit more tokens",
        "type": "boolean"
      },
      "callback": {
        "description": "Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.",
        "type": "boolean"
      },
      "permit": {
        "description": "Whether without paying gas, token holders will be able to allow third parties to transfer from their account.",
        "type": "boolean"
      },
      "votes": {
        "description": "Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps.",
        "anyOf": [
          {
            "type": "string",
            "const": "blocknumber"
          },
          {
            "type": "string",
            "const": "timestamp"
          }
        ]
      },
      "flashmint": {
        "description": "Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they&#39;re returned in the same transaction.",
        "type": "boolean"
      },
      "crossChainBridging": {
        "description": "Whether to allow authorized bridge contracts to mint and burn tokens for cross-chain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token contract, or to use the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "custom"
              },
              {
                "type": "string",
                "const": "erc7786native"
              }
            ]
          },
          {
            "type": "string",
            "const": "superchain"
          }
        ]
      },
      "crossChainLinkAllowOverride": {
        "description": "Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to \"erc7786native\".",
        "type": "boolean"
      },
      "namespacePrefix": {
        "description": "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 and upgradeability is enabled. Default is \"myProject\".",
        "type": "string"
      },
      "access": {
        "description": "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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      },
      "restrictions": {
        "description": "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.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "boolean",
                "const": false
              },
              {
                "type": "string",
                "const": "allowlist"
              }
            ]
          },
          {
            "type": "string",
            "const": "blocklist"
          }
        ]
      },
      "freezable": {
        "description": "Whether authorized accounts can freeze and unfreeze accounts for regulatory or security purposes. This feature is experimental, not audited and is subject to change.",
        "type": "boolean"
      }
    },
    "required": [
      "name",
      "symbol"
    ]
  }
}

solidity-rwa 19 params · 2 required Make a real-world asset token that uses the ERC-20 standard. Experimental, some features are not audited and a…

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.

Input schema

Parameter	Type	Description & constraints
name*	string	The name of the contract
symbol*	string	The short symbol for the token
decimals	string	The number of decimals used to represent token amounts. Defaults to 18.
burnable	boolean	Whether token holders will be able to destroy their tokens
pausable	boolean	Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
premint	string	The number of tokens to premint for the deployer.
premintChainId	string	The chain ID of the network on which to premint tokens.
mintable	boolean	Whether privileged accounts will be able to create more supply or emit more tokens
callback	boolean	Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.
permit	boolean	Whether without paying gas, token holders will be able to allow third parties to transfer from their account.
votes	string \| string	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	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	string \| string \| string	Whether to allow authorized bridge contracts to mint and burn tokens for cross-chain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token contract, or to use the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.
crossChainLinkAllowOverride	boolean	Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to "erc7786native".
namespacePrefix	string	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 and upgradeability is enabled. Default is "myProject".
access	string \| string \| string	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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.
info	object	Metadata about the contract and author
info.securityContact	string	Email where people can contact you to report security issues. Will only be visible if contract source code is verified.
info.license	string	The license used by the contract, default is "MIT"
restrictions	boolean \| string \| string	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	Whether authorized accounts can freeze and unfreeze accounts for regulatory or security purposes. This feature is experimental, not audited and is subject to change.

Raw schema JSON

solidity-rwa — raw

{
  "name": "solidity-rwa",
  "description": "Make a real-world asset token that uses the ERC-20 standard. Experimental, some features are not audited and are subject to change.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "symbol": {
        "type": "string",
        "description": "The short symbol for the token"
      },
      "decimals": {
        "description": "The number of decimals used to represent token amounts. Defaults to 18.",
        "type": "string"
      },
      "burnable": {
        "description": "Whether token holders will be able to destroy their tokens",
        "type": "boolean"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "premint": {
        "description": "The number of tokens to premint for the deployer.",
        "type": "string"
      },
      "premintChainId": {
        "description": "The chain ID of the network on which to premint tokens.",
        "type": "string"
      },
      "mintable": {
        "description": "Whether privileged accounts will be able to create more supply or emit more tokens",
        "type": "boolean"
      },
      "callback": {
        "description": "Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.",
        "type": "boolean"
      },
      "permit": {
        "description": "Whether without paying gas, token holders will be able to allow third parties to transfer from their account.",
        "type": "boolean"
      },
      "votes": {
        "description": "Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps.",
        "anyOf": [
          {
            "type": "string",
            "const": "blocknumber"
          },
          {
            "type": "string",
            "const": "timestamp"
          }
        ]
      },
      "flashmint": {
        "description": "Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they&#39;re returned in the same transaction.",
        "type": "boolean"
      },
      "crossChainBridging": {
        "description": "Whether to allow authorized bridge contracts to mint and burn tokens for cross-chain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token contract, or to use the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "custom"
              },
              {
                "type": "string",
                "const": "erc7786native"
              }
            ]
          },
          {
            "type": "string",
            "const": "superchain"
          }
        ]
      },
      "crossChainLinkAllowOverride": {
        "description": "Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to \"erc7786native\".",
        "type": "boolean"
      },
      "namespacePrefix": {
        "description": "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 and upgradeability is enabled. Default is \"myProject\".",
        "type": "string"
      },
      "access": {
        "description": "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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      },
      "restrictions": {
        "description": "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.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "boolean",
                "const": false
              },
              {
                "type": "string",
                "const": "allowlist"
              }
            ]
          },
          {
            "type": "string",
            "const": "blocklist"
          }
        ]
      },
      "freezable": {
        "description": "Whether authorized accounts can freeze and unfreeze accounts for regulatory or security purposes. This feature is experimental, not audited and is subject to change.",
        "type": "boolean"
      }
    },
    "required": [
      "name",
      "symbol"
    ]
  }
}

solidity-account 9 params · 1 required Make an account contract that follows the ERC-4337 standard. Returns the source code of the generated contrac…

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.

Input schema

Parameter	Type	Description & constraints
name*	string	The name of the account contract
signatureValidation	boolean \| string \| string	Whether to implement the ERC-1271 standard for validating signatures. This is useful for the account to verify signatures.
ERC721Holder	boolean	Whether to implement the `onERC721Received` function to allow the account to receive ERC721 tokens.
ERC1155Holder	boolean	Whether to implement the `onERC1155Received` function to allow the account to receive ERC1155 tokens.
signer	boolean \| string \| string \| string \| string \| string \| string \| string	Defines the signature verification algorithm used by the account to verify user operations. Options: - ECDSA: Standard Ethereum signature validation using secp256k1, validates signatures against a specified owner address - EIP7702: Special ECDSA validation using account's own address as signer, enables EOAs to delegate execution rights - Multisig: ERC-7913 multisignature requiring minimum number of signatures from authorized signers - MultisigWeighted: ERC-7913 weighted multisignature where signers have different voting weights - P256: NIST P-256 curve (secp256r1) validation for integration with Passkeys and HSMs - RSA: RSA PKCS#1 v1.5 signature validation (RFC8017) for PKI systems and HSMs - WebAuthn: Web Authentication (WebAuthn) assertion validation for integration with Passkeys and HSMs on top of P256
batchedExecution	boolean	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	boolean \| string \| string	Whether to implement the ERC-7579 compatibility to enable functionality on the account with modules.
info	object	Metadata about the contract and author
info.securityContact	string	Email where people can contact you to report security issues. Will only be visible if contract source code is verified.
info.license	string	The license used by the contract, default is "MIT"
upgradeable	string \| string	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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.

Raw schema JSON

solidity-account — raw

{
  "name": "solidity-account",
  "description": "Make an account contract that follows the ERC-4337 standard.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the account contract"
      },
      "signatureValidation": {
        "description": "Whether to implement the ERC-1271 standard for validating signatures. This is useful for the account to verify signatures.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "boolean",
                "const": false
              },
              {
                "type": "string",
                "const": "ERC1271"
              }
            ]
          },
          {
            "type": "string",
            "const": "ERC7739"
          }
        ]
      },
      "ERC721Holder": {
        "description": "Whether to implement the `onERC721Received` function to allow the account to receive ERC721 tokens.",
        "type": "boolean"
      },
      "ERC1155Holder": {
        "description": "Whether to implement the `onERC1155Received` function to allow the account to receive ERC1155 tokens.",
        "type": "boolean"
      },
      "signer": {
        "description": "Defines the signature verification algorithm used by the account to verify user operations. Options:\n        - ECDSA: Standard Ethereum signature validation using secp256k1, validates signatures against a specified owner address\n        - EIP7702: Special ECDSA validation using account&#39;s own address as signer, enables EOAs to delegate execution rights\n        - Multisig: ERC-7913 multisignature requiring minimum number of signatures from authorized signers\n        - MultisigWeighted: ERC-7913 weighted multisignature where signers have different voting weights\n        - P256: NIST P-256 curve (secp256r1) validation for integration with Passkeys and HSMs\n        - RSA: RSA PKCS#1 v1.5 signature validation (RFC8017) for PKI systems and HSMs\n        - WebAuthn: Web Authentication (WebAuthn) assertion validation for integration with Passkeys and HSMs on top of P256",
        "anyOf": [
          {
            "anyOf": [
              {
                "anyOf": [
                  {
                    "anyOf": [
                      {
                        "anyOf": [
                          {
                            "anyOf": [
                              {
                                "anyOf": [
                                  {
                                    "type": "boolean",
                                    "const": false
                                  },
                                  {
                                    "type": "string",
                                    "const": "ECDSA"
                                  }
                                ]
                              },
                              {
                                "type": "string",
                                "const": "EIP7702"
                              }
                            ]
                          },
                          {
                            "type": "string",
                            "const": "Multisig"
                          }
                        ]
                      },
                      {
                        "type": "string",
                        "const": "MultisigWeighted"
                      }
                    ]
                  },
                  {
                    "type": "string",
                    "const": "P256"
                  }
                ]
              },
              {
                "type": "string",
                "const": "RSA"
              }
            ]
          },
          {
            "type": "string",
            "const": "WebAuthn"
          }
        ]
      },
      "batchedExecution": {
        "description": "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.",
        "type": "boolean"
      },
      "ERC7579Modules": {
        "description": "Whether to implement the ERC-7579 compatibility to enable functionality on the account with modules.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "boolean",
                "const": false
              },
              {
                "type": "string",
                "const": "AccountERC7579"
              }
            ]
          },
          {
            "type": "string",
            "const": "AccountERC7579Hooked"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      },
      "upgradeable": {
        "description": "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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      }
    },
    "required": [
      "name"
    ]
  }
}

solidity-governor 17 params · 3 required Make a contract to implement governance, such as for a DAO. Returns the source code of the generated contract…

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.

Input schema

Parameter	Type	Description & constraints
name*	string	The name of the contract
delay*	string	The delay since proposal is created until voting starts, default is "1 day"
period*	string	The length of period during which people can cast their vote, default is "1 week"
votes	string \| string	The type of voting to use
clockMode	string \| string	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	boolean \| string \| string	The type of timelock to use
blockTime	number	The block time of the chain in seconds, default is 12
decimals	number	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	Minimum number of votes an account must have to create a proposal, default is 0.
quorumMode	string \| string	The type of quorum mode to use
quorumPercent	number	The percent required, in cases of quorumMode equals percent
quorumAbsolute	string	The absolute quorum required, in cases of quorumMode equals absolute
storage	boolean	Enable storage of proposal details and enumerability of proposals
settings	boolean	Allow governance to update voting settings (delay, period, proposal threshold)
crossChainExecution	boolean	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 gateway and executor are chosen per proposal as arguments to the relayCrosschain function.
upgradeable	string \| string	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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.
info	object	Metadata about the contract and author
info.securityContact	string	Email where people can contact you to report security issues. Will only be visible if contract source code is verified.
info.license	string	The license used by the contract, default is "MIT"

Raw schema JSON

solidity-governor — raw

{
  "name": "solidity-governor",
  "description": "Make a contract to implement governance, such as for a DAO.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "delay": {
        "type": "string",
        "description": "The delay since proposal is created until voting starts, default is \"1 day\""
      },
      "period": {
        "type": "string",
        "description": "The length of period during which people can cast their vote, default is \"1 week\""
      },
      "votes": {
        "description": "The type of voting to use",
        "anyOf": [
          {
            "type": "string",
            "const": "erc20votes"
          },
          {
            "type": "string",
            "const": "erc721votes"
          }
        ]
      },
      "clockMode": {
        "description": "The clock mode used by the voting token. For Governor, this must be chosen to match what the ERC20 or ERC721 voting token uses.",
        "anyOf": [
          {
            "type": "string",
            "const": "blocknumber"
          },
          {
            "type": "string",
            "const": "timestamp"
          }
        ]
      },
      "timelock": {
        "description": "The type of timelock to use",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "boolean",
                "const": false
              },
              {
                "type": "string",
                "const": "openzeppelin"
              }
            ]
          },
          {
            "type": "string",
            "const": "compound"
          }
        ]
      },
      "blockTime": {
        "description": "The block time of the chain in seconds, default is 12",
        "type": "number"
      },
      "decimals": {
        "description": "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)",
        "type": "number"
      },
      "proposalThreshold": {
        "description": "Minimum number of votes an account must have to create a proposal, default is 0.",
        "type": "string"
      },
      "quorumMode": {
        "description": "The type of quorum mode to use",
        "anyOf": [
          {
            "type": "string",
            "const": "percent"
          },
          {
            "type": "string",
            "const": "absolute"
          }
        ]
      },
      "quorumPercent": {
        "description": "The percent required, in cases of quorumMode equals percent",
        "type": "number"
      },
      "quorumAbsolute": {
        "description": "The absolute quorum required, in cases of quorumMode equals absolute",
        "type": "string"
      },
      "storage": {
        "description": "Enable storage of proposal details and enumerability of proposals",
        "type": "boolean"
      },
      "settings": {
        "description": "Allow governance to update voting settings (delay, period, proposal threshold)",
        "type": "boolean"
      },
      "crossChainExecution": {
        "description": "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 gateway and executor are chosen per proposal as arguments to the relayCrosschain function.",
        "type": "boolean"
      },
      "upgradeable": {
        "description": "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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      }
    },
    "required": [
      "name",
      "delay",
      "period"
    ]
  }
}

solidity-custom 5 params · 1 required Make a custom smart contract. Returns the source code of the generated contract, formatted in a Markdown code…

Make a custom smart contract. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.

Input schema

Parameter	Type	Description & constraints
name*	string	The name of the contract
pausable	boolean	Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
access	string \| string \| string	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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.
upgradeable	string \| string	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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.
info	object	Metadata about the contract and author
info.securityContact	string	Email where people can contact you to report security issues. Will only be visible if contract source code is verified.
info.license	string	The license used by the contract, default is "MIT"

Raw schema JSON

solidity-custom — raw

{
  "name": "solidity-custom",
  "description": "Make a custom smart contract.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "access": {
        "description": "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 privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "upgradeable": {
        "description": "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 less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      }
    },
    "required": [
      "name"
    ]
  }
}

Resources 8

URI	Name	MIME type	Description
ui://openzeppelin/solidity-erc20.html	Solidity ERC20	`text/html;profile=mcp-app`	Interactive Wizard UI for solidity-erc20
ui://openzeppelin/solidity-erc721.html	Solidity ERC721	`text/html;profile=mcp-app`	Interactive Wizard UI for solidity-erc721
ui://openzeppelin/solidity-erc1155.html	Solidity ERC1155	`text/html;profile=mcp-app`	Interactive Wizard UI for solidity-erc1155
ui://openzeppelin/solidity-stablecoin.html	Solidity Stablecoin	`text/html;profile=mcp-app`	Interactive Wizard UI for solidity-stablecoin
ui://openzeppelin/solidity-rwa.html	Solidity RWA	`text/html;profile=mcp-app`	Interactive Wizard UI for solidity-rwa
ui://openzeppelin/solidity-account.html	Solidity Account	`text/html;profile=mcp-app`	Interactive Wizard UI for solidity-account
ui://openzeppelin/solidity-governor.html	Solidity Governor	`text/html;profile=mcp-app`	Interactive Wizard UI for solidity-governor
ui://openzeppelin/solidity-custom.html	Solidity Custom	`text/html;profile=mcp-app`	Interactive Wizard UI for solidity-custom

Prompts 0

No prompts advertised.

Inventory recorded Aug 6, 2026 — 5:10 AM as rev 1. Listing calls only — tools are never invoked.

Canonical contract hash

contract hash — rev 1

sha256:9c303d7088cd1e3f50ab0fcc1ab901079fdeae55449c86a4820074df5a17911c

Computed centrally from the normalized capability inventory (normalizer v1). Scanners submit raw observations; the control plane normalizes and hashes, so every scanner agrees on the same value.

Revisions 1

Rev	Observed	Hash
rev 1 baseline	Aug 6, 2026 — 5:10 AM (43 d ago)

Contract changes 0

No drift observed — every successful observation since Aug 6, 2026 has matched the baseline hash. Boring, in the best way.

Full snapshots are stored only when the canonical hash changes — unchanged observations update freshness without duplicating the contract.

Recent observations latest 30

Observed	Result	Latency
Sep 17, 2026 — 7:50 PM (24 min ago)	Reachable	109 ms
Sep 17, 2026 — 7:15 PM (59 min ago)	Reachable	182 ms
Sep 17, 2026 — 6:40 PM (2 h ago)	Reachable	101 ms
Sep 17, 2026 — 6:05 PM (2 h ago)	Reachable	134 ms
Sep 17, 2026 — 5:30 PM (3 h ago)	Reachable	208 ms
Sep 17, 2026 — 4:55 PM (3 h ago)	Reachable	130 ms
Sep 17, 2026 — 4:15 PM (4 h ago)	Reachable	137 ms
Sep 17, 2026 — 3:40 PM (5 h ago)	Reachable	126 ms
Sep 17, 2026 — 3:10 PM (5 h ago)	Reachable	142 ms
Sep 17, 2026 — 2:30 PM (6 h ago)	Reachable	112 ms
Sep 17, 2026 — 1:55 PM (6 h ago)	Reachable	102 ms
Sep 17, 2026 — 1:20 PM (7 h ago)	Reachable	106 ms
Sep 17, 2026 — 12:30 PM (8 h ago)	Reachable	96 ms
Sep 17, 2026 — 11:55 AM (8 h ago)	Reachable	87 ms
Sep 17, 2026 — 11:20 AM (9 h ago)	Reachable	75 ms
Sep 17, 2026 — 10:50 AM (9 h ago)	Reachable	98 ms
Sep 17, 2026 — 10:05 AM (10 h ago)	Reachable	80 ms
Sep 17, 2026 — 9:35 AM (11 h ago)	Reachable	80 ms
Sep 17, 2026 — 9:00 AM (11 h ago)	Reachable	92 ms
Sep 17, 2026 — 8:20 AM (12 h ago)	Reachable	181 ms
Sep 17, 2026 — 7:40 AM (13 h ago)	Reachable	83 ms
Sep 17, 2026 — 7:10 AM (13 h ago)	Reachable	116 ms
Sep 17, 2026 — 6:20 AM (14 h ago)	Reachable	62 ms
Sep 17, 2026 — 5:45 AM (14 h ago)	Reachable	62 ms
Sep 17, 2026 — 5:05 AM (15 h ago)	Reachable	103 ms
Sep 17, 2026 — 4:15 AM (16 h ago)	Reachable	241 ms
Sep 17, 2026 — 3:40 AM (17 h ago)	Reachable	81 ms
Sep 17, 2026 — 3:10 AM (17 h ago)	Reachable	97 ms
Sep 17, 2026 — 2:35 AM (18 h ago)	Reachable	64 ms
Sep 17, 2026 — 2:00 AM (18 h ago)	Reachable	118 ms

Latest check — evidence & validation Sep 17, 2026 — 7:50 PM

Reachable MCP Tools Edge Scanner ScheduledHTTP 200109 msStreamable HTTP2025-06-18

response headers (as observed)

{
  "server": "cloudflare",
  "content-type": "text/event-stream"
}

serverInfo — from initialize

{
  "name": "OpenZeppelin Solidity Contracts MCP Server",
  "version": "0.7.1",
  "title": null
}