
WalletHygiene
Scan a Web3 wallet address for toxic contracts, spam transactions, and risky on-chain history before your agent connects users or signs flows.
Overview
WalletHygiene is an MCP server for the Ship phase that detects on-chain toxicity and spam transactions for Web3 wallets via a remote SSE endpoint.
What is this MCP server?
- Detects on-chain toxicity and spam-style transaction patterns for a given wallet address
- Remote MCP over SSE at wallet-hygiene-mcp.vercel.app—no local chain node required in the README
- Optional premium settlement via EIP-3009 TransferWithAuthorization (payment-signature header)
- Fits pre-connect checks in dApps, custody dashboards, and agent-driven wallet onboarding
- Version 1.0.0 per server manifest (WalletHygiene)
- Server version 1.0.0 in server.json
- Single documented remote SSE endpoint (wallet-hygiene-mcp.vercel.app)
- One optional secret header: payment-signature (EIP-3009)
What problem does it solve?
You cannot safely connect or display a wallet in your app when you do not know if its history is full of spam or toxic interactions.
Who is it for?
Indie Web3 builders adding wallet connect, admin treasury views, or agent tools that must screen addresses before sign-in or payouts.
Skip if: Teams that need licensed KYC/AML, offline cold-wallet key management, or deep forensic tracing without any on-chain API budget.
What do I get? / Deliverables
Your agent returns a structured hygiene assessment so you can block, warn, or quarantine risky wallets before they touch your flows.
- Agent-callable toxicity and spam-oriented wallet assessment
- Documented remote MCP registration (WalletHygiene v1.0.0)
Recommended MCP Servers
Journey fit
Wallet hygiene checks belong on the Ship shelf because they gate whether a wallet is safe to bind to a product before launch and in ongoing user flows. Security is the right subphase: the server flags toxicity and spam patterns that affect trust and abuse risk, not generic market research.
How it compares
On-chain wallet hygiene MCP—not a browser skill or a generic block explorer bookmark.
Common Questions / FAQ
Who is WalletHygiene for?
Solo and indie builders shipping Web3 apps or agent workflows who need quick toxicity and spam signal on wallet addresses before users connect.
When should I use WalletHygiene?
Use it during security review before launch or when onboarding new wallets, especially if you want automated screening inside your coding agent.
How do I add WalletHygiene to my agent?
Add the remote MCP server URL https://wallet-hygiene-mcp.vercel.app/api/mcp (SSE) in your client; set payment-signature if your plan requires EIP-3009 premium settlement.