docs: Add UCAI (abi-to-mcp) to registry #3221
Open
+1
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
pip install abi-to-mcp- generate MCP servers from contract addresses or ABI filesThis 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?
Breaking Changes
None - this is a new addition to the registry.Types of changes
Checklist
Additional context
UCAI follows the Model Context Protocol specification and generates servers using the official MCP Python SDK. All generated servers include:
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
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context