SealGuard

모든 Solana 지갑에서 위험한 승인과 사기 토큰을 확인하고, 빈 계정에 잠겨 있는 SOL을 찾습니다. 읽기 전용입니다.

호스팅형 MCP 서버

npx add-mcp 'https://guard.2cstudio.app/mcp'

Claude Code, Codex, Cursor 등에 설치됩니다

문서

Check Solana wallets from your AI app

SealGuard's MCP server lets Claude, Cursor, VS Code and other AI apps run the same wallet check as this site. Ask "is this wallet safe?", "which approvals are still open?" or "how much SOL can I get back from empty accounts?" and get an answer from the chain.

Server URL: https://guard.2cstudio.app/mcp

The wallet checks are free, with no sign-in and no API key. Checking a transaction before it's signed (check_transaction) is paid: see below. It's all read-only: it never asks for a seed phrase and can't send a transaction. When something needs fixing, the answer includes a link to SealGuard, where the wallet's owner connects their wallet and approves each fix.

Add it to your AI app

Claude (claude.ai and the desktop app): Settings → Connectors → Add custom connector, then paste the server URL.

Claude Code:

claude mcp add --transport http sealguard https://guard.2cstudio.app/mcp

Cursor (~/.cursor/mcp.json):

{ "mcpServers": { "sealguard": { "url": "https://guard.2cstudio.app/mcp" } } }

VS Code (.vscode/mcp.json):

{ "servers": { "sealguard": { "type": "http", "url": "https://guard.2cstudio.app/mcp" } } }

Any other client that supports remote MCP servers over Streamable HTTP works the same way.

Tools

  • scan_wallet: a 0–100 safety score and everything found: open token approvals, phishing airdrops, Token-2022 permanent delegates and transfer restrictions, stake and nonce accounts someone else controls, and whether the wallet account itself has been taken over. Also totals the SOL in empty token accounts.
  • list_empty_token_accounts: each empty token account, the SOL rent in it, and which ones SealGuard suggests closing. Accounts for tokens you'll likely receive again, or used in the last 30 days, are marked to keep, with the reason.
  • list_token_approvals: every address that can still move tokens out of the wallet, and how much, plus permanent delegates that holders can't revoke.
  • check_transaction (paid): before a wallet signs a transaction, SealGuard simulates it and says whether it would hand anything over. See below.

Checking a transaction before it's signed

For agents and apps that sign Solana transactions. Pass the serialized transaction (base64; unsigned is fine) and, if it isn't the fee payer, the wallet about to sign. SealGuard simulates it on mainnet and compares that wallet's accounts before and after. It reports:

  • the wallet account handed to another program, a token account given a new owner, a standing approval left on tokens, a new close authority, and stake or nonce authorities moved to someone else;
  • the SOL and token amounts that would leave and arrive, and a warning when things leave and nothing comes back;
  • a durable nonce, which keeps a signed transaction valid long after it was signed, and programs SealGuard doesn't know.

The answer starts with a verdict: do_not_sign, review or no_red_flags. It can't judge prices, or whether a payment is one you meant to make, and the chain can change between the check and the signature.

Price: a wallet's first key comes with 20 free checks. After that, US$0.01 a check, bought 500 at a time for US$5 in USDC, SOL or SKR. Wallets with the SealGuard guard get 1,000 checks a month included. A check is taken only when SealGuard returns an answer. Get a key at guard.2cstudio.app/mcp-key: connect the wallet that will own it, sign in and buy checks there.

Send the key as a header. Claude Code:

claude mcp add --transport http sealguard https://guard.2cstudio.app/mcp --header "Authorization: Bearer sgk_…"

Cursor (~/.cursor/mcp.json):

{ "mcpServers": { "sealguard": { "url": "https://guard.2cstudio.app/mcp", "headers": { "Authorization": "Bearer sgk_…" } } } }

VS Code (.vscode/mcp.json):

{ "servers": { "sealguard": { "type": "http", "url": "https://guard.2cstudio.app/mcp", "headers": { "Authorization": "Bearer sgk_…" } } } }

Agents calling the server directly send the same header (or x-api-key: sgk_…) with each request. SealGuard doesn't keep the transactions it checks; it counts checks per key.

Things to ask

  • "Is wallet <address> safe? Explain anything risky in plain words."
  • "How much SOL can I get back from empty token accounts in <address>?"
  • "Does <address> have any token approvals I should revoke?"
  • "Before signing, check this transaction with SealGuard: <base64>"

Limits and privacy

Each free check reads the wallet from the Solana network, so there are limits: 30 checks an hour from one connection, and a daily total across everyone. Paid transaction checks are limited per key to a few dozen a minute. SealGuard keeps a record of each check, including the address (see the privacy notice). It also keeps a count of calls per connection, under a one-way hash, for up to two days, for the limit. Results are general information, not financial or security advice: see the terms.

Fixing what it finds

Revoking approvals and burning phishing tokens are free. Closing empty token accounts costs 5% of the SOL returned, paid in the same transaction, and nothing for wallets with the guard. For the step-by-step guides, see closing empty token accounts and revoking token approvals.

An MCP server for your own API?

SealGuard is made by 2C Studio. We build MCP servers like this one for other teams: on your existing API, on your own domain, listed in the official MCP Registry and the main directories. See 2cstudio.app/services for prices and a quote.