mcpbeat Sign in

WalletHygiene MCP Server

answering

WalletHygiene is answering right now. Last checked 11 min ago.

On-chain toxicity and spam transaction detector for Web3 wallets.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
92 ms
Response time
average over 24h
authentication required
Access
sse

Nothing serious here today

Today is the operative word: we check WalletHygiene every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add wallet-hygiene --transport http https://wallet-hygiene-mcp.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "wallet-hygiene": {
      "url": "https://wallet-hygiene-mcp.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.wallet-hygiene]
url = "https://wallet-hygiene-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "wallet-hygiene": {
      "url": "https://wallet-hygiene-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "wallet-hygiene": {
      "url": "https://wallet-hygiene-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://wallet-hygiene-mcp.vercel.app/api/mcp sse needs auth 87 ms 11 min ago

Alternatives to WalletHygiene

same job, measured the same way
Ramaris App
by ramaris-app

On-chain wallet analytics and trading strategies on Base for AI assistants

local only
Arbitrum Transaction Preflight
by naur9n

Paid Arbitrum transaction simulation and risk scoring for wallets and AI agents.

25 installs/wk local only
Near Wallet Manager
by mastrophot

MCP server for NEAR wallet creation, balance checks, and transaction signing.

33 installs/wk local only
Cyberwarex Chain Data
by cyberpunk11147

EVM onchain data: wallet, token, price, gas, transactions, ENS across 5 chains.

local only
Fuse Network
by fuse

MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.

50 tools answering
MintwareDevelopers
by mintwaredevelopers

Look up on-chain Attribution reputation scores for wallets and AI agents on Base.

38 installs/wk local only
Seraph
by kondux

Crypto transaction firewall and risk tools for MCP agents.

answering
Agent Security
by mdfifty50-boop

Security scanning and threat detection for AI agents

46 installs/wk local only

WalletHygiene — questions

Answers built from our own checks of this server.

Why is there no tool list for WalletHygiene?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is WalletHygiene working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 92 ms. The bar chart above shows every period we have measured.
How do I connect WalletHygiene?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does WalletHygiene need an API key?
Yes. Every time we knock, WalletHygiene answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is WalletHygiene?
It answers our handshake in 92 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.