crypto_wallet_intel
Multi-chain on-chain analytics for crypto trading agents, on-chain analysts, AML/compliance teams and DeFi BD. Covers Ethereum, Base, Polygon, BSC, Arbitrum, Optimism — EVM-compatible addresses only. 5 modes: • wallet_profile — full wallet summary: type (EOA/contract/CEX/protocol), inferred perso...
This record as markdown: /tools/io-github-getgapup-gapup-mcp/crypto-wallet-intel.md
What crypto_wallet_intel does on Gapup Mcp
AI agents call crypto_wallet_intel to retrieve information from Gapup Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | Yes | Analysis mode. wallet_profile=full wallet summary + persona + sanctions flag. token_flows=ERC-20 inflows/outflows per token priced in USD. pnl_estimate=FIFO rea |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
chain | string | — | Chain to analyze. Default "ethereum". Use "all" to scan all 6 chains (slower, ~30s). |
address | string | Yes | EVM-compatible wallet address (0x... 40 hex chars). Works on all supported chains. |
period_days | number | — | Lookback window in days for token_flows, pnl_estimate, counterparties, defi_positions. Default 30. |
min_value_usd | number | — | Minimum USD value filter for token_flows and counterparties. Default $100. |
Parameters from the server's own tool schema.
Why crypto_wallet_intel is rated Low
This tool retrieves and analyzes on-chain blockchain data across multiple chains — wallet profiles, token flows, and P&L estimates. It performs no writes, executions, or financial transactions.
From the tool's definition on-chain analytics...wallet_profile — full wallet summary...token_flows — ERC-20 inflows/outflows...pnl_estimate — FIFO realized + unrealized P&L...OFAC sanctions flag
Attacks that exploit this kind of access
The rule that runs crypto_wallet_intel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto_wallet_intel, this is the rule to start with:
crypto_wallet_intel is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every crypto_wallet_intel call is checked against it from then on.
Questions about crypto_wallet_intel
Multi-chain on-chain analytics for crypto trading agents, on-chain analysts, AML/compliance teams and DeFi BD. Covers Ethereum, Base, Polygon, BSC, Arbitrum, Optimism — EVM-compatible addresses only. 5 modes: • wallet_profile — full wallet summary: type (EOA/contract/CEX/protocol), inferred persona (whale/MEV-bot/DeFi-user/hodler…), age, tx count, native balance, ERC-20 count, NFT collections, OFAC sanctions flag • token_flows — ERC-20 inflows/outflows per token on the selected period, priced in USD via CoinGecko • pnl_estimate — FIFO realized + unrealized P&L on the period with confidence rating (high/medium/low) • counterparties — top 20 counterparties ranked by USD volume with CEX/DEX/protocol labels • defi_positions — active DeFi positions detected via Etherscan interaction history (Aave/Compound/Uniswap/Curve/Lido/Balancer/SushiSwap) Signal detection (P0/P1/P2): P0 if OFAC SDN match OR direct Tornado Cash / sanctioned-protocol interaction P1 if >$1M volume on wallet <30 days old OR MEV-bot pattern OR >80% volume on single counterparty P2 informational (CEX wallet, new wallet, no anomaly) Sources: Etherscan family (keyless free-tier, optional API key per chain), DefiLlama (keyless), public EVM RPC (keyless), CoinGecko free tier (keyless). Cache TTL: 5 min (wallet activity evolves fast). Budget: 8s per source. Env vars (all optional, raise Etherscan rate-limit from 1 req/5s to 5 req/s): ETHERSCAN_API_KEY · BASESCAN_API_KEY · POLYGONSCAN_API_KEY BSCSCAN_API_KEY · ARBISCAN_API_KEY · OPTIMISM_API_KEY. It is categorised as a Read tool in the Gapup Mcp MCP Server, which means it retrieves data without modifying state.
crypto_wallet_intel accepts 6 parameters: mode, async, chain, address, period_days, min_value_usd. Required: mode, address. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for crypto_wallet_intel: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Gapup Mcp. Nothing to install.
crypto_wallet_intel is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the crypto_wallet_intel rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for crypto_wallet_intel. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
crypto_wallet_intel is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue