MetaComp Skill - Carteira Web3 e Transações
metacomp-ai/metacomp-skill
Gerenciador de carteiras Web3 e transações seguras para Claude
Ver no GitHubSkill para Claude que expõe capacidades de conta e segurança Web3 da MetaComp. Permite gerenciamento de portfólio, saques, trocas de moedas, investimentos em produtos de renda fixa e análise de risco em blockchain via integração MCP.
Instalação
npx convez-ai metacomp-ai/metacomp-skill1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Visualizar saldo e portfólio multi-conta em tempo real
- Executar saques em fiat e criptomoedas com conformidade automática
- Trocar entre pares fiat-fiat, fiat-cripto e cripto-cripto
- Avaliar risco de endereços blockchain e transações com VisionX
Veredito

Solução robusta para integração de serviços Web3 e fintech ao Claude através de MCP, com roteamento inteligente por intenção e protocolos bem definidos por cenário. Exige gestão cuidadosa de chaves de API e alinhamento entre ambiente do zip e backend.
README
A tradução para o português deste README ainda está na fila.
MetaComp Agent Skill
A single MCP-powered skill that exposes MetaComp's account and Web3-security
capabilities to Claude and other MCP-compatible clients. One SKILL.md entry
point routes the request to the matching scenario — withdrawal, currency swap,
wealth (Fixed Income Products), balance / portfolio overview, or VisionX Web3
risk screening — loading the relevant files under references/ at runtime.
Download
The skill is released as one zip per backend environment, each pre-configured to talk to the matching MetaComp environment.
→ Latest release · All releases
| Zip | Backend it points to |
|---|---|
MetaComp-demo-<version>.zip | https://demo.metacomp.ai |
MetaComp-sandbox-<version>.zip | https://sandbox.metacomp.ai |
MetaComp-prod-<version>.zip | https://www.metacomp.ai (production) |
Install
- Download the zip for your target environment from the release page above.
- Unzip it — you get a single
MetaComp/folder. - Upload that folder to Claude through Customize → Skills.
- Set up the MCP connector — see Connecting the MCP server below.
What it does
| Capability | Summary |
|---|---|
| Balance / portfolio overview | Renders the multi-account portfolio overview and per-currency detail. |
| Withdrawal | Outbound fiat and crypto transfers, distinguishing first-party from third-party destinations and their differing compliance requirements. |
| Swap | Currency exchange across supported fiat–fiat, fiat–crypto, and crypto–crypto pairs, with a time-boxed quote shown before execution. |
| Wealth (FIP) | Investor pre-check, then browse and subscribe to MetaComp Fixed Income Products with an explicit agreement-acceptance step. |
| VisionX (Web3 security) | Structured risk reports for a wallet address or transaction hash — entity identification, risk-source breakdown, and exposure direction, aggregated across multiple on-chain analytics vendors. |
The skill routes by intent: describe what you want (e.g. "withdraw 500 USDC", "swap 100k USDT to SGD", "check my balance", or paste a wallet address) and the entry point dispatches to the matching scenario.
Connecting the MCP server
The skill uses the metacomp-mcp connector.
- In Claude, open Customize → Connectors → + and add a custom connector named
metacomp-mcp, using the/mcpURL for the environment your downloaded zip targets — for production that ishttps://www.metacomp.ai/mcp. - Connect and authorize with an
sk-...API key issued for that environment. - Re-send the request. A 401 after connecting means the key must be re-authorized or reissued.
The connector environment must match the zip you installed (a production zip
talks to the production backend, a uat zip to UAT, and so on).
Repository layout
.
├── MetaComp/
│ ├── SKILL.md entry point: routing + per-scenario step protocol
│ └── references/ shared/ swap/ visionx/ wealth/ withdraw/
├── build.sh per-environment URL rewrite + zip
└── .github/workflows/ bundle build workflow
SKILL.md carries YAML frontmatter (name, version, description, MCP server)
followed by the router and per-scenario step protocols. Files under
references/ are loaded by the entry point as each scenario requires.
Contributing
When editing the skill:
- Bump
version:inMetaComp/SKILL.mdfrontmatter. - Keep the router (STEP ZERO) and each scenario's sub-skill list in sync with the
files actually under
references/. - Do not loosen the Token Guard, the Wealth Evaluation Gate, or the Funds-First Gate without an explicit design discussion; they are safety rails, not stylistic choices.
- Trigger phrases (including bilingual variants) belong in the
description:field of the frontmatter, not in the step prose.