mcpField
E
emblemai-crypto-wallet

emblemai-crypto-wallet

github.com/sickn33Other48.7k78 installsUpdated today
Repository

About emblemai-crypto-wallet

emblemai-crypto-wallet is a skill for agents handling explicitly authorized crypto wallet operations. It covers balance and portfolio checks, token research, swaps, and transfers across several chains, with a focus on verifying transaction details before approval.

Key features

  1. 01Check wallet balances across chains
  2. 02Retrieve portfolio and token details
  3. 03Swap tokens and make transfers
  4. 04Support NFT and cross-chain operations
  5. 05Review and confirm exact transaction parameters

Use cases

  1. 01Review wallet balances and portfolio holdings
  2. 02Research tokens and verify asset identity
  3. 03Swap or transfer tokens with explicit authorization

MCP support

This is an agent skill, not an MCP server; the input does not describe an MCP integration.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill emblemai-crypto-wallet

After installing, type/emblemai-crypto-walletin Claude Code to confirm it loaded.

Details

From the project README

EmblemAI Crypto Wallet

Use the provider only for explicitly authorized wallet operations. The chain/endpoint list is historical reference, not a live capability or custody guarantee; verify current official provider documentation and account permissions before use.

When to Use

  • User wants to check crypto wallet balances
  • User wants to swap or trade tokens
  • User wants portfolio analysis or token research
  • User wants to interact with DeFi protocols
  • User needs cross-chain wallet operations

Setup

This AAS entry is an integration index; the full external references/scripts are not bundled. If installation is requested, review an immutable source/version and its dependency/signing behavior before activating it:

npx skills add EmblemCompany/Agent-skills --skill emblem-ai-agent-wallet

Or install the npm package directly:

npm install @emblemvault/agentwallet

Supported Chains

ChainOperations
SolanaBalance, swap, transfer, token lookup
EthereumBalance, swap, transfer, NFT
BaseBalance, swap, transfer
BSCBalance, swap, transfer
PolygonBalance, swap, transfer
HederaBalance, transfer
BitcoinBalance, transfer

API Integration

Base URL: https://api.agenthustle.ai

Authentication requires an API key passed as x-api-key header.

Core Endpoints
  • GET /balance/{chain}/{address} — Check wallet balance
  • POST /swap — Execute token swap
  • GET /portfolio/{address} — Portfolio overview
  • GET /token/{chain}/{contract} — Token information
  • POST /transfer — Send tokens

Key Behaviors

  1. Exact transaction authorization — before signing/submitting, show chain/network, verified token/asset address, source wallet, recipient, amount, fees, slippage, minimum received, approvals/allowance, spender, expiry and actual simulation result; obtain confirmation for that exact transaction. A quote/portfolio request does not authorize a swap or transfer
  2. Check balances first before attempting swaps or transfers
  3. Verify asset identity independently using authoritative chain/explorer/project sources; a third-party rugcheck score is advisory and cannot prove legitimacy
  4. Report gas estimates when available
  5. Protect credentials and verify custody — never send private keys or seed phrases through chat, logs or unapproved APIs. Provider claims about server-side vault signing need verification; do not guarantee custody architecture from this index

Links

Limitations

  • If signing, broadcasting or confirmation times out, preserve the transaction/idempotency reference and reconcile actual chain state before retrying; do not risk a duplicate transfer. Finality, failed execution, quote expiry and rejected simulation must be reported distinctly.
  • A balance/quote is read-only advice, not transaction authorization; approvals and unlimited allowances are separate risky actions. No wallet, account, provider call or transaction was executed during content review.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported