Aegis Protocol vs Contracts Wizard
A side-by-side look at the Aegis Protocol and Contracts Wizard MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Aegis Protocol for finance & fintech work as a local process; choose Contracts Wizard for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Aegis Protocol when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
Choose Contracts Wizard when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
solidity-erc20, solidity-erc721, solidity-erc1155.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 40/100 · Fair | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 295 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 33 |
| Full listing | View Aegis Protocol | View Contracts Wizard |
Tools & capabilities
Aegis Protocol tools
No tool names declared yet. Check the project README from the listing page.
Contracts Wizard tools 33
solidity-erc20Make 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.solidity-erc721Make 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.solidity-erc1155Make 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.solidity-stablecoinMake a stablecoin token that uses the ERC-20 standard. This contract type does not support upgradeability. 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.solidity-rwaMake a real-world asset token that uses the ERC-20 standard. This contract type does not support upgradeability. 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.solidity-accountMake 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.solidity-governorMake 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.solidity-customMake a custom smart contract. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.cairo-erc20Make 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.cairo-erc721Make 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.cairo-erc1155Make 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.cairo-erc6909Make a minimal multi-token per the ERC-6909 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.- +21 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Aegis Protocol
{
"mcpServers": {
"aegis-protocol": {
"command": "uvx",
"args": [
"crewai"
]
}
}
}
Contracts Wizard
{
"mcpServers": {
"openzeppelin-contracts-wizard": {
"command": "npx",
"args": [
"-y",
"@openzeppelin/contracts-mcp"
]
}
}
}
Frequently asked questions
Aegis Protocol is categorized under Finance & Fintech and uses a local stdio subprocess. Contracts Wizard belongs to Finance & Fintech and uses a local stdio subprocess. Pick Aegis Protocol for finance & fintech work and Contracts Wizard for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Aegis Protocol has no declared pricing — check the project's own site. Contracts Wizard is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aegis-protocol and openzeppelin-contracts-wizard as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aegis Protocol has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 4 GitHub stars. Contracts Wizard has 68/100 (Great) with 1 views, 0 installs and 295 GitHub stars.