여러 EVM 체인에서 스왑, 브릿지, 지정가 주문 및 시장 조사를 포함한 DeFi 작업을 AI agent가 실행할 수 있도록 지원합니다.
다른 이름 Apegurus/web3agent
- 스타
- 1
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.6.2
- 마지막 커밋
- 2026년 9월 25일
- 라이선스
- MIT
web3agent MCP란?
web3agent은(는) MCP server입니다. 여러 EVM 체인에서 스왑, 브릿지, 지정가 주문 및 시장 조사를 포함한 DeFi 작업을 AI agent가 실행할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
web3agent MCP server 정보
web3agent는 AI agent를 통해 스왑, 브릿지, 지정가 주문과 같은 DeFi 작업을 실행할 수 있게 해줍니다. 이 MCP server는 지갑 관리, 시장 조사 및 여러 EVM 체인과의 상호작용을 위한 190개 이상의 도구를 제공합니다. 복잡한 프로토콜 통합을 다시 구축할 필요 없이 블록체인 실행 기능을 통합하려는 AI agent 빌더, DeFi 팀 및 개발자를 위해 설계되었습니다.
이 server는 stdio 연결을 통해 로컬에서 작동하며 Claude Code, Cursor, Windsurf, OpenCode, Codex와 같은 호스트와 호환됩니다. 셀프 커스토디 방식이므로 키는 사용자의 환경에 그대로 유지됩니다. 보안을 보장하기 위해 모든 쓰기 작업은 기본적으로 확인 대기열을 거치며, 트랜잭션이 실행되기 전에 사용자의 명시적인 승인이 필요합니다.
사용자는 Base에서 ERC-20 잔액을 확인하는 것부터 Orbs를 통한 트리거 주문 설정, 또는 LI.FI를 사용하여 20개 이상의 체인 간 자산을 브릿징하는 것까지 다양한 작업을 수행할 수 있습니다. 시스템이 복잡한 라우팅과 트랜잭션 준비를 처리하므로, agent는 유동성 허브, CCXT를 통한 거래소, CoinGecko 또는 DefiLlama와 같은 다양한 시장 데이터 제공업체와 상호작용할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
web3agent MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 web3agent MCP 설치
$ claude mcp add --env 'COINGECKO_API_KEY=<YOUR_COINGECKO_API_KEY>' --env 'ETHERSCAN_API_KEY=<YOUR_ETHERSCAN_API_KEY>' --env 'OWS_PASSPHRASE=<YOUR_OWS_PASSPHRASE>' --env 'ZEROX_API_KEY=<YOUR_ZEROX_API_KEY>' web3agent -- npx -y web3agentCursor에 web3agent MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"web3agent": {
"command": "npx",
"args": [
"-y",
"web3agent"
],
"env": {
"COINGECKO_API_KEY": "<YOUR_COINGECKO_API_KEY>",
"ETHERSCAN_API_KEY": "<YOUR_ETHERSCAN_API_KEY>",
"OWS_PASSPHRASE": "<YOUR_OWS_PASSPHRASE>",
"ZEROX_API_KEY": "<YOUR_ZEROX_API_KEY>"
}
}
}
}VS Code에 web3agent MCP 설치
.vscode/mcp.json
{
"servers": {
"web3agent": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"web3agent"
],
"env": {
"COINGECKO_API_KEY": "<YOUR_COINGECKO_API_KEY>",
"ETHERSCAN_API_KEY": "<YOUR_ETHERSCAN_API_KEY>",
"OWS_PASSPHRASE": "<YOUR_OWS_PASSPHRASE>",
"ZEROX_API_KEY": "<YOUR_ZEROX_API_KEY>"
}
}
}
}VS Code CLI에 web3agent MCP 설치
$ code --add-mcp '{"name":"web3agent","type":"stdio","command":"npx","args":["-y","web3agent"],"env":{"COINGECKO_API_KEY":"<YOUR_COINGECKO_API_KEY>","ETHERSCAN_API_KEY":"<YOUR_ETHERSCAN_API_KEY>","OWS_PASSPHRASE":"<YOUR_OWS_PASSPHRASE>","ZEROX_API_KEY":"<YOUR_ZEROX_API_KEY>"}}'Claude Desktop에 web3agent MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"web3agent": {
"command": "npx",
"args": [
"-y",
"web3agent"
],
"env": {
"COINGECKO_API_KEY": "<YOUR_COINGECKO_API_KEY>",
"ETHERSCAN_API_KEY": "<YOUR_ETHERSCAN_API_KEY>",
"OWS_PASSPHRASE": "<YOUR_OWS_PASSPHRASE>",
"ZEROX_API_KEY": "<YOUR_ZEROX_API_KEY>"
}
}
}
}Codex에 web3agent MCP 설치
$ codex mcp add web3agent --env 'COINGECKO_API_KEY=<YOUR_COINGECKO_API_KEY>' --env 'ETHERSCAN_API_KEY=<YOUR_ETHERSCAN_API_KEY>' --env 'OWS_PASSPHRASE=<YOUR_OWS_PASSPHRASE>' --env 'ZEROX_API_KEY=<YOUR_ZEROX_API_KEY>' -- npx -y web3agentCodex config.toml에 web3agent MCP 설치
~/.codex/config.toml
[mcp_servers.web3agent] command = "npx" args = ["-y", "web3agent"] [mcp_servers.web3agent.env] COINGECKO_API_KEY = "<YOUR_COINGECKO_API_KEY>" ETHERSCAN_API_KEY = "<YOUR_ETHERSCAN_API_KEY>" OWS_PASSPHRASE = "<YOUR_OWS_PASSPHRASE>" ZEROX_API_KEY = "<YOUR_ZEROX_API_KEY>"
Gemini CLI에 web3agent MCP 설치
$ gemini mcp add -s user -e 'COINGECKO_API_KEY=<YOUR_COINGECKO_API_KEY>' -e 'ETHERSCAN_API_KEY=<YOUR_ETHERSCAN_API_KEY>' -e 'OWS_PASSPHRASE=<YOUR_OWS_PASSPHRASE>' -e 'ZEROX_API_KEY=<YOUR_ZEROX_API_KEY>' web3agent npx -- -y web3agentGemini settings.json에 web3agent MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"web3agent": {
"command": "npx",
"args": [
"-y",
"web3agent"
],
"env": {
"COINGECKO_API_KEY": "<YOUR_COINGECKO_API_KEY>",
"ETHERSCAN_API_KEY": "<YOUR_ETHERSCAN_API_KEY>",
"OWS_PASSPHRASE": "<YOUR_OWS_PASSPHRASE>",
"ZEROX_API_KEY": "<YOUR_ZEROX_API_KEY>"
}
}
}
}구성
COINGECKO_API_KEY비밀Optional CoinGecko API key for higher-rate market data.
ETHERSCAN_API_KEY비밀Optional Etherscan API key for Etherscan-backed explorer tools.
OWS_PASSPHRASE비밀Optional Open Wallet Standard vault passphrase for persisted local wallets.
ZEROX_API_KEY비밀Optional 0x API key for 0x swap plugin support.
CCXT_CONFIG_PATHOptional local path to a CCXT account config JSON file.
CHAIN_IDDefault EVM chain ID. Defaults to Base mainnet (8453).
CONFIRM_WRITESRequire explicit confirmation before write operations execute. Defaults to true.
WEB3AGENT_EXAMPLE_ACCOUNT
| 이름 | 설명 | 유형 |
|---|---|---|
| COINGECKO_API_KEY | Optional CoinGecko API key for higher-rate market data. | 비밀 |
| ETHERSCAN_API_KEY | Optional Etherscan API key for Etherscan-backed explorer tools. | 비밀 |
| OWS_PASSPHRASE | Optional Open Wallet Standard vault passphrase for persisted local wallets. | 비밀 |
| ZEROX_API_KEY | Optional 0x API key for 0x swap plugin support. | 비밀 |
| CCXT_CONFIG_PATH | Optional local path to a CCXT account config JSON file. | |
| CHAIN_ID | Default EVM chain ID. Defaults to Base mainnet (8453). | |
| CONFIRM_WRITES | Require explicit confirmation before write operations execute. Defaults to true. | |
| WEB3AGENT_EXAMPLE_ACCOUNT | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능apegurus/web3agent is public and reachablegithub.com/apegurus/web3agent ↗통과
- 패키지가 이 저장소를 소스로 명시web3agent names apegurus/web3agent as sourcenpmjs.com/package/web3agent ↗통과
- 빌드 출처(Sigstore 증명)No build attestation published for this release검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-09-25github.com/apegurus/web3agent ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from web3agent통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음310 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기See it in production: The Arena — 11 AI agents trade real capital through Web3Agent.
web3agent
MCP package:
web3agent| npm: https://www.npmjs.com/package/web3agent | GitHub: https://github.com/Apegurus/web3agent | Contact: hello@apeguru.dev
Links: Website · GitHub · npm · Smithery · The Arena · X / @Web3AgentFi
Give your AI agent EVM execution and DeFi tooling: swaps, bridges, limit and trigger orders, exchange trading, market data, research, wallet management. 190+ MCP tools. One install.
Works out of the box with Claude Code, Cursor, Windsurf, OpenCode, and Codex. Self-custodial. By default, write operations go through a confirmation queue: nothing executes without your approval unless you explicitly disable confirmations.
EVM execution is a solved problem. Stop rebuilding it. Plug in and ship.
What you can do
Once installed, your AI agent can execute real DeFi operations in plain language:
- "Swap 0.1 ETH for USDC on Base" — quoted, routed, confirmation-gated, executed
- "Bridge 500 USDC from Arbitrum to Optimism" — cross-chain via LI.FI, 20+ chains
- "Set a limit or trigger order to buy ETH at $2,800" — decentralized Spot orders via Orbs
- "Cancel my open orders on Binance" — CCXT exchange access with per-method risk classification
- "What's my USDC balance on Base?" — read-only EVM and ERC-20 balance checks
- "Show me yield opportunities above 5% APY" — research tools, protocol analysis, due diligence
Common flows avoid ABI handling and transaction building. Generic contract reads and writes are available when you provide or register an ABI, or when explorer ABI lookup is available. The agent handles routing, transaction preparation, and the confirmation queue. You approve, it executes.
Quickstart for agent power users
npx web3agent init
This detects Claude Code, Cursor, Windsurf, OpenCode, or Codex and configures the MCP server automatically. Restart your host, then ask:
What Web3 tools do you have available, and what chain are you configured for?
For any other MCP-capable host, configure a stdio server that runs:
npx web3agent
The generic MCP config shape is:
{
"web3agent": {
"type": "stdio",
"command": "npx",
"args": ["web3agent"]
}
}
Writes are confirmation-gated by default, and wallet secrets are not exposed through MCP unless explicitly enabled.
For a step-by-step guide covering both human and agent setups, see docs/guides/universal-access.md.
Smithery local bundle
Smithery URL publishing requires a hosted Streamable HTTP MCP endpoint. Web3Agent is distributed as a local stdio/npm server, so Smithery distribution uses an MCPB bundle instead:
pnpm run mcpb:check
smithery mcp publish dist/web3agent.mcpb -n Apegurus/web3agent
The generated MCPB is a thin local bundle that launches the published npm package with npm exec --package web3agent@0.6.2.
Why Web3Agent
- One-line install.
npx web3agent initauto-configures Claude Code, Cursor, Windsurf, OpenCode, or Codex. No manual config edits for supported hosts. - Self-custodial. Keys stay in your environment, wallet secrets are kept out of agent-visible MCP flows by default, and every write goes through the confirmation queue unless you intentionally disable it.
- Battle-tested infrastructure. Built on GOAT SDK, LI.FI, Orbs, Blockscout, Etherscan, DexScreener, and other production Web3 rails.
- Live in production. Powers Orbzy and The Arena, where AI agents trade real capital through Web3Agent.
- One MCP surface. Swaps, bridges, orders, market data, research, token resolution, wallet lifecycle, and agent-payment protocols are available through one server.
Who it is for
- AI agent builders who need Web3 execution without rebuilding protocol integrations
- DeFi teams adding MCP support to internal tools, research agents, or trading agents
- Developers prototyping wallet-aware agents, swaps, bridges, and market workflows
- MCP host users who want read-only chain data plus explicit-confirmation write flows
Copy-paste prompts
Use these after installation to get to value quickly:
List the supported chains and tell me which Web3 tools are safest to try first.
Resolve USDC, WETH, and DEGEN on Base. Show token addresses and decimals.
Quote swapping 0.01 ETH to USDC on Base, but do not execute anything.
Show yield opportunities above 5% APY and explain the main protocol risks.
Explain this wallet's recent activity on Base: 0x0000000000000000000000000000000000000000
Supported hosts
| Host | Config location |
|---|---|
| Claude Code | ~/.claude/mcp.json |
| Cursor | .cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| OpenCode | .opencode/config.json |
| Codex | .codex/config.toml |
| OpenClaw | agent-mediated self-install via canonical guide |
Supported chains
Basic EVM operations use viem's chain registry and can target any viem-supported EVM chain when RPC access is available.
Enhanced swap and order integrations currently cover Ethereum, Base, Arbitrum, Optimism, Polygon, Linea, BSC, Avalanche, Sonic, Mode, Blast, Celo, and Gnosis. Token resolution, explorer, LI.FI, and market/research tools have provider-specific coverage; LI.FI bridge quotes and execution support 20+ chains through LI.FI's own chain list.
Default: Base (8453). Override with the CHAIN_ID env var or pass chainId per call.
What's included
| Capability | Provider | Notes |
|---|---|---|
| On-chain state | Native EVM tools | Balances, contract reads/writes, gas, ENS, multicall (27 tools) |
| Swaps | GOAT / Uniswap / Balancer | Same-chain, ERC-20/721 |
| Aggregated swaps | Orbs Liquidity Hub | Optimal pricing via solver network |
| Cross-chain bridges | LI.FI | 20+ chains |
| Lending | GOAT SDK / protocol integrations | Aave, Morpho, and major money-market surfaces where supported |
| Advanced orders | Orbs | Spot market, limit, TWAP, stop-loss, take-profit, delayed orders |
| Exchange trading | CCXT | Public/private access across 100+ exchanges (6 tools) |
| Block explorer | Blockscout + Etherscan | Address info, tx history, NFTs, contract ABIs, network stats (35 tools) |
| Market data | DefiLlama / CoinGecko / Binance | TVL, prices, DEX volume, stablecoin stats, sentiment (20 tools) |
| Research | DefiLlama / on-chain | Contract security, yield analysis, whale tracking, governance (13 tools) |
| Token resolution | Built-in registry + DexScreener | Symbol-to-address, long-tail assets |
| Wallet management | web3agent + Open Wallet Standard | CLI/MCP lifecycle, encrypted OWS vault when configured, legacy fallback |
| Confirmation queue | Built-in | Write operations require explicit approval by default |
| Agent protocols | aGDP / ACP / ERC-8183 / x402 / ERC-8004 | Agent marketplace, cooperation, payments |
| Price data | CoinGecko | Requires COINGECKO_API_KEY |
| 0x swaps | 0x | Requires ZEROX_API_KEY |
Starter templates
npx web3agent create
Scaffolds a ready-to-run project from one of three bundled templates:
- Vercel AI SDK — chat agent with tool calling
- Mastra — agent framework with web3agent tools
- MCP-host — lightweight MCP client
Each starter uses the same web3agent lifecycle surfaces as MCP and CLI.
Examples
Root examples are included in the npm package:
# Safe import-only previews
node examples/swap.mjs
node examples/bridge.mjs
# Read-only live quote examples
node examples/swap.mjs --quote
node examples/bridge.mjs --quote
# Prepared external-wallet flows
WEB3AGENT_EXAMPLE_ACCOUNT=0x... node examples/swap.mjs --prepare
WEB3AGENT_EXAMPLE_ACCOUNT=0x... node examples/bridge.mjs --prepare
The examples default to small USDC-denominated flows and only prepare wallet actions when you pass --prepare.
Quickstart examples
Agent that prepares a swap on Base
import { prepareOperation, resolveCanonicalTokenSync } from "web3agent";
const chainId = 8453;
const usdc = resolveCanonicalTokenSync({ chainId, symbol: "USDC" });
const weth = resolveCanonicalTokenSync({ chainId, symbol: "WETH" });
if (!usdc || !weth) throw new Error("Missing canonical token");
const intent = await prepareOperation({
integration: "orbs",
kind: "swap",
account: "0xYourWallet",
chainId,
fromToken: usdc.address,
toToken: weth.address,
fromAmount: "10000000",
slippagePct: 0.5,
});
console.log(intent.nextActions);
Agent that prepares a bridge from Ethereum to Arbitrum
import { prepareOperation, resolveCanonicalTokenSync } from "web3agent";
const fromChainId = 1;
const toChainId = 42161;
const from = resolveCanonicalTokenSync({ chainId: fromChainId, symbol: "USDC" });
const to = resolveCanonicalTokenSync({ chainId: toChainId, symbol: "USDC" });
if (!from || !to) throw new Error("Missing canonical token");
const bridge = await prepareOperation({
integration: "lifi",
kind: "bridge",
account: "0xYourWallet",
fromChainId,
toChainId,
fromToken: from.address,
toToken: to.address,
fromAmount: "1000000",
});
console.log(bridge.nextActions);
Agent that monitors a wallet
import { getAddressInfo, getTransactionHistory, listSupportedChains } from "web3agent";
const address = "0x0000000000000000000000000000000000000000";
const chainId = 8453;
const [chains, info, history] = await Promise.all([
listSupportedChains(),
getAddressInfo({ address, chainId }),
getTransactionHistory({ address, chainId, pageSize: 5 }),
]);
console.log({
supportedChains: chains.chains.length,
wallet: info,
recentTransactions: history.transactions,
});
For crypto teams
Use web3agent when you want AI agents to discover or interact with your protocol without every team rebuilding wallet, chain, token, quote, explorer, and confirmation plumbing.
Integration surfaces:
- MCP tools for Claude Code, Cursor, Windsurf, OpenCode, Codex, and other MCP hosts
- Programmatic SDK from
web3agentfor app-owned agents and browser-wallet flows - Prepared operations for protocols that need users or apps to sign externally
- Confirmation-gated writes so execution never bypasses an explicit approval path by default
Good first integration targets:
- token, market, and position reads
- quote and simulation tools
- prepared wallet actions for browser/app signing
- protocol-specific research or risk tools
For protocol support or integration questions, open an issue at https://github.com/Apegurus/web3agent/issues or contact hello@apeguru.dev.
Usage
# Initialize for your host (run once)
npx web3agent init
# Start the MCP server
npx web3agent
# CLI fallback (for non-MCP hosts or scripting)
npx web3agent tools list --json
npx web3agent tools call resolve_token --input '{"symbol":"USDC","chainId":8453}' --json
npx web3agent doctor --json
# Local-only wallet secret flows (requires OWS_PASSPHRASE >= 12 chars and an interactive TTY)
OWS_PASSPHRASE='...' npx web3agent wallet generate
OWS_PASSPHRASE='...' npx web3agent wallet generate --mnemonic
OWS_PASSPHRASE='...' npx web3agent wallet activate --from-file ./secret.txt --type private-key
# Options
npx web3agent --help
npx web3agent --version
Wallet secret MCP tools are disabled by default so private keys and mnemonics do not enter an AI agent's inference context. Use the local web3agent wallet ... commands above for safe generation/import. If you explicitly accept the risk of agent-visible secrets, set WEB3AGENT_ALLOW_AGENT_VISIBLE_SECRETS=1 to re-enable the legacy MCP behavior.
wallet_deactivate only deactivates the current runtime session and returns to read-only ephemeral mode. Use confirmation-gated wallet_delete when you intentionally want to permanently remove persisted wallet material.
Wallet security defaults
By default, web3agent keeps wallet secrets out of MCP tool responses and agent-visible inputs. The local web3agent wallet ... commands are the recommended way to generate or import private keys and mnemonics because they require an interactive TTY and refuse JSON secret output. Set WEB3AGENT_ALLOW_AGENT_VISIBLE_SECRETS=1 only if you explicitly accept that private keys or mnemonics can be sent through the MCP host and visible to the agent/inference provider.
For persisted server-side wallets, setting OWS_PASSPHRASE is not mandatory, but strongly recommended. When it is set on macOS/Linux and OWS is available, web3agent uses the Open Wallet Standard encrypted vault instead of the legacy filesystem-protected wallet store. The OWS spec minimum is 12 characters; web3agent warns on weak runtime passphrases and local wallet generation/import rejects shorter values. Use a 16+ character mixed passphrase in production. Configure it in the process that runs web3agent, whether that is npx web3agent as an MCP server or an app/service using createRuntime({ env: { OWS_PASSPHRASE: "..." } }).
If OWS_PASSPHRASE is missing, empty, OWS is unavailable, the platform is Windows, or OWS_FORCE_LEGACY=1 is set, web3agent falls back to legacy wallet storage protected by file permissions only. Migrating a legacy wallet.json leaves a plaintext wallet.json.migrated rollback backup; delete it after verifying OWS access. For multi-agent services, run separate wallet-using runtimes in separate processes until per-runtime wallet isolation is supported.
Programmatic usage
Root API
Use the package root for stable, typed EVM capabilities from another app or agent layer.
import {
getChain,
listChainTokens,
resolveCanonicalTokenSync,
resolveToken,
} from "web3agent";
const chain = getChain(8453);
const usdc = resolveCanonicalTokenSync({ symbol: "USDC", chainId: 8453 });
const tokens = listChainTokens({ chainId: 8453 });
const discovered = await resolveToken({ symbol: "DEGEN", chainId: 8453 });
console.log(
chain?.name,
usdc?.address,
discovered.address,
tokens.tokens.length,
);
Use resolveCanonicalToken() for well-known registry tokens and native-token aliases. Use resolveToken() when you also want DexScreener discovery fallback for long-tail assets.
Browser wallet flows
Use the root API when your app owns the signer (e.g. a browser wallet via wagmi or AppKit).
import {
prepareOperation,
resumeOperation,
simulateTransaction,
} from "web3agent";
prepareOperation(...)returns the next wallet actions plusresumeState- Your app executes those actions with the browser wallet
resumeOperation(...)continues until the operation completes
Transaction actions are only considered complete once you return a confirmed result:
{ type: "transaction", txHash: "0x...", status: "confirmed" }
resumeOperation() independently verifies the receipt before advancing.
Architecture notes: docs/architecture/browser-wallet-operations.md
Runtime API
Use web3agent/runtime when you need tool discovery, generic invocation, or upstream passthrough tools.
import { createRuntime } from "web3agent/runtime";
const runtime = await createRuntime();
try {
console.log(runtime.getHealth());
console.log(
runtime
.listTools()
.slice(0, 5)
.map((tool) => tool.name),
);
const result = await runtime.invokeTool("list_supported_chains");
console.log(result.structuredContent);
} finally {
await runtime.shutdown();
}
Environment variables
See WEB3_CONTEXT.md for the full environment variable reference.
For authenticated exchange access via CCXT tools, set CCXT_CONFIG_PATH to a JSON file containing named accounts and exchange credentials.
Known limitations
- Blockscout explorer tools work on 8 chains only (Ethereum, Polygon, Arbitrum, Optimism, Base, Gnosis, Scroll, zkSync Era)
- Yield tooling is read-only research; protocol-specific execution beyond first-class tools uses ABI-backed EVM calls
- 0x and CoinGecko plugins require their respective API keys
- MCP hosts cannot open a browser wallet prompt directly — MCP can prepare, simulate, and submit signed payloads, but signing requires your app to handle the wallet interaction
Requirements
- Node.js 22+
- pnpm (for development)
License
MIT
web3agent MCP 질문
web3agent MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'COINGECKO_API_KEY=<YOUR_COINGECKO_API_KEY>' --env 'ETHERSCAN_API_KEY=<YOUR_ETHERSCAN_API_KEY>' --env 'OWS_PASSPHRASE=<YOUR_OWS_PASSPHRASE>' --env 'ZEROX_API_KEY=<YOUR_ZEROX_API_KEY>' web3agent -- npx -y web3agent를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
web3agent MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
AI agent와 함께 사용해도 안전한가요?
네, 셀프 커스토디 방식이며 쓰기 작업은 기본적으로 승인 절차를 거칩니다. 즉, 명시적으로 비활성화하지 않는 한 사용자의 승인 없이 아무것도 실행되지 않습니다.
어떤 AI agent 또는 호스트를 지원하나요?
Claude Code, Cursor, Windsurf, OpenCode, Codex에서 즉시 사용할 수 있습니다.
agent가 어떤 종류의 DeFi 작업을 수행할 수 있나요?
스왑, 브릿지, 지정가 및 트리거 주문, 거래소 트레이딩, 시장 데이터 조사를 수행할 수 있습니다.
agent를 위해 어떻게 설치하나요?
npx web3agent init 명령어를 사용하여 지원되는 호스트를 자동으로 설정할 수 있습니다.