Universal Contract AI Interface (UCAI)
ABI-to-MCP generator: turns any smart contract ABI into an MCP server agents can call.
- Sato Score86
- ChainsMultichain
Universal Contract AI Interface (UCAI) is an open-source developer tool, with last code activity on 2026-09-15 (Active). Sato Score 86/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-14. How the score works →
See how to install Universal Contract AI Interface (UCAI) →Last commit Sep 15, 2026 · ★ 37
Listed from github.com/nirholas/UCAI on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21. Evidence →
Next step
Watch Universal Contract AI Interface (UCAI)
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on nirholas/ucai before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
UCAI is an open-source generator that converts a smart contract's ABI into an MCP server, covering DeFi protocols, ERC-20 tokens, NFTs, and arbitrary contracts. Instead of hand-writing MCP tools per contract, an agent builder points UCAI at an ABI and gets contract read/write tools an agent can call. Useful for quickly exposing bespoke or long-tail contracts to an agent stack; generated write tools still need the same key-handling care as any transaction path.
Sato Score
86/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 18/20
- Interface verifiability
- 8/10
- Docs & demo
- 10/10
- Listing transparency & provenance
- 12/15
- Independent verification
- 3/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v0.1.0 · as of 2026-09-29- Does it take your key?
- Reads a key
- Does your key leave?
- Not yet run
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from github.com/nirholas/UCAI on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | docs.ucai.tech | as of 2026-10-14 |
| Verification status | Unverified — not independently reviewed | self-reported | github.com/nirholas/UCAI | as of 2026-10-14 |
| Recent activity | last commit 2026-09-15 | observed | github.com/nirholas/UCAI | 2026-10-14 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | github.com/nirholas/UCAI | 2026-07-21 |
| Website answers | answered (HTTP 200) | observed | github.com/nirholas/UCAI | 2026-10-14 |
| Daily check record | 90 of 90 daily checks since 2026-07-16 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-13 |
| Takes your key | reads private-key material | traced | satohub.ai | 2026-09-29 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-09-29 |
| Creator profile | https://github.com/nirholasconfidence 0.85 | self-reported | github.com/nirholas/UCAI | as of 2026-07-14 |
| Works with | Claudeconfidence 0.60 | self-reported | github.com/nirholas/UCAI | as of 2026-07-14 |
| Docs | https://docs.ucai.techconfidence 0.85 | self-reported | github.com/nirholas/UCAI | as of 2026-07-14 |
| Demo | https://mcp.ucai.techconfidence 0.85 | self-reported | github.com/nirholas/UCAI | as of 2026-07-14 |
| Demo available | yesconfidence 0.85 | self-reported | github.com/nirholas/UCAI | as of 2026-07-14 |
| Sato Score | 86/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-14 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — reproduced in a container Jul 21, 2026
Runtime: Python 3.10+
pip install abi-to-mcp abi-to-mcp generate <source> [options] — e.g. abi-to-mcp generate 0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D -o ~/uniswap-server; generated server needs cd ~/uniswap-server && pip install -r requirements.txt
You supply: RPC_URL (required, Web3 RPC endpoint for the generated server), PRIVATE_KEY (required only for write/transaction tools — risk: controls funds), ETHERSCAN_API_KEY (optional, for fetching ABIs)
MCP invocation: python server.py (stdio) — runs the generated server, not UCAI itself
Read from the project’s own docs as of 2026-07-21. What a deploy spec is →
Observed record — 90 daily checks since 2026-07-17
- Succeeded
- 90
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-14, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Multichain
- Agent types
- Developer Tool, MCP Server
- Open source
- Yes
- Works with
- Claude
- Last checked
- 2026-10-14
Marketplace Signals
- ▸ Demo available
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Universal Contract AI Interface (UCAI) fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets
Listing History
Recorded changes to Universal Contract AI Interface (UCAI)'s listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Jul 21, 2026Verified: deploy spec
- Jul 20, 2026Sato Score tier: Medium → HighScore 65 → 73.
- Jul 17, 2026Sato Hub began tracking this listing
- Jul 14, 2026Enriched: supported integrations
- Jul 14, 2026Auto-enriched: creator profile url, docs url, has demo, demo url
- Jul 14, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Universal Contract AI Interface (UCAI)
- Is Universal Contract AI Interface (UCAI) open source?
- Yes. Universal Contract AI Interface (UCAI) is open source under the Proprietary (README states 'All rights reserved') license; the repository is https://github.com/nirholas/UCAI. Checked as of 2026-10-14.
- Which chains does Universal Contract AI Interface (UCAI) support?
- Universal Contract AI Interface (UCAI) lists support for Multichain as of 2026-10-14.
- Is Universal Contract AI Interface (UCAI) still maintained?
- The most recent code activity Sato Hub observed was on 2026-09-15 (last commit 2026-09-15), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Universal Contract AI Interface (UCAI)?
- Python 3.10+. Install: pip install abi-to-mcp. Entry: abi-to-mcp generate <source> [options] — e.g. abi-to-mcp generate 0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D -o ~/uniswap-server; generated server needs cd ~/uniswap-server && pip install -r requirements.txt. Sato Hub reproduced this install in a container on 2026-07-21.
- Is Universal Contract AI Interface (UCAI) verified on Sato Hub?
- Sato Hub holds one earned check for Universal Contract AI Interface (UCAI): Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 86 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Universal Contract AI Interface (UCAI) — Sato Hub." Sato Hub, updated 2026-10-14, accessed 2026-10-15. https://satohub.ai/resources/ucaiData last refreshed 2026-10-14; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.