Skip to content

Conversation

@nirholas
Copy link

Add UCAI (abi-to-mcp) - Smart Contract to MCP Server Generator

Motivation and Context

Added UCAI to the MCP registry. UCAI is a tool that converts Ethereum smart contract ABIs into fully functional MCP servers, enabling AI assistants like Claude to interact with any smart contract on any EVM-compatible chain.

Key features:

  • CLI & Python API: pip install abi-to-mcp - generate MCP servers from contract addresses or ABI files
  • Web Builder: mcp.ucai.tech - no-install browser-based server generation
  • Security Scanner: AI-powered contract risk analysis with 50+ security patterns
  • Contract Whisperer: Plain English explanations of smart contract functionality
  • Multi-chain Support: Ethereum, Base, Arbitrum, Polygon, Optimism, BSC, and more
  • Safety First: Write operations simulate by default, read-only mode available

This enables AI agents to query token balances, inspect NFT metadata, simulate transactions, and execute DeFi operations through natural language.

Documentation: https://docs.ucai.tech
GitHub: https://github.com/nirholas/UCAI
PyPI: https://pypi.org/project/abi-to-mcp/
Web App: https://mcp.ucai.tech

How Has This Been Tested?

  • Generated MCP servers for ERC-20 tokens (USDC, USDT)
  • Tested with Uniswap, Aave, and NFT collections (BAYC)
  • Integrated with Claude Desktop successfully
  • Utilized by numerous FinTech enterprise projects
  • 876 unit tests with 98% coverage

Breaking Changes

None - this is a new addition to the registry.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

UCAI follows the Model Context Protocol specification and generates servers using the official MCP Python SDK. All generated servers include:

  • Type-safe tool definitions mapped from Solidity types
  • Transaction simulation for write operations
  • Event queries as MCP resources
  • Proper error handling and gas estimation

Description

Publishing Your Server

Note: We are no longer accepting PRs to add servers to the README. Instead, please publish your server to the MCP Server Registry to make it discoverable to the MCP ecosystem.

To publish your server, follow the quickstart guide. You can browse published servers at https://registry.modelcontextprotocol.io/.

Server Details

  • Server:
  • Changes to:

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

<!-- Provide a brief summary of your changes -->
Add UCAI (abi-to-mcp) - Smart Contract to MCP Server Generator

## Motivation and Context

Added UCAI to the MCP registry. UCAI is a tool that converts Ethereum smart contract ABIs into fully functional MCP servers, enabling AI assistants like Claude to interact with any smart contract on any EVM-compatible chain.

Key features:
- **CLI & Python API**: `pip install abi-to-mcp` - generate MCP servers from contract addresses or ABI files
- **Web Builder**: [mcp.ucai.tech](https://mcp.ucai.tech) - no-install browser-based server generation
- **Security Scanner**: AI-powered contract risk analysis with 50+ security patterns
- **Contract Whisperer**: Plain English explanations of smart contract functionality
- **Multi-chain Support**: Ethereum, Base, Arbitrum, Polygon, Optimism, BSC, and more
- **Safety First**: Write operations simulate by default, read-only mode available

This enables AI agents to query token balances, inspect NFT metadata, simulate transactions, and execute DeFi operations through natural language.

Documentation: https://docs.ucai.tech
GitHub: https://github.com/nirholas/UCAI
PyPI: https://pypi.org/project/abi-to-mcp/
Web App: https://mcp.ucai.tech

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were tested? -->
- Generated MCP servers for ERC-20 tokens (USDC, USDT)
- Tested with Uniswap, Aave, and NFT collections (BAYC)
- Integrated with Claude Desktop successfully
- Utilized by numerous FinTech enterprise projects
- 876 unit tests with 98% coverage

## Breaking Changes
<!-- Will users need to update their code or configurations? --> None - this is a new addition to the registry.

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [ ] Documentation update

## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
- [x] I have read the [MCP Documentation](https://modelcontextprotocol.io)
- [x] My code follows the repository's style guidelines
- [x] New and existing tests pass locally
- [x] I have added appropriate error handling
- [x] I have added or updated documentation as needed

## Additional context
<!-- Add any other context, implementation notes, or design decisions -->

UCAI follows the Model Context Protocol specification and generates servers using the official MCP Python SDK. All generated servers include:
- Type-safe tool definitions mapped from Solidity types
- Transaction simulation for write operations
- Event queries as MCP resources
- Proper error handling and gas estimation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant