# SealGuard (remote · guard.2cstudio.app)

Check Solana wallets and transactions for risky approvals and scam tokens; find SOL to take back.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `guard.2cstudio.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/2cstudiodev-web-sealguard/guard.md), [page](https://verifymcp.io/servers/2cstudiodev-web-sealguard/guard)

## Channel facts

- Endpoint: `https://guard.2cstudio.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 704 tokens (~176/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SealGuard MCP server?

SealGuard is a hosted endpoint at https://guard.2cstudio.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http 2cstudiodev-web-sealguard 'https://guard.2cstudio.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "2cstudiodev-web-sealguard": {
      "url": "https://guard.2cstudio.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "2cstudiodev-web-sealguard": {
      "type": "http",
      "url": "https://guard.2cstudio.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.2cstudiodev-web-sealguard]
url = "https://guard.2cstudio.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "2cstudiodev-web-sealguard": {
      "type": "remote",
      "url": "https://guard.2cstudio.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 2cstudiodev-web-sealguard --url 'https://guard.2cstudio.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  2cstudiodev-web-sealguard:
    url: "https://guard.2cstudio.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "2cstudiodev-web-sealguard": {
      "Transport": "http",
      "Url": "https://guard.2cstudio.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add 2cstudiodev-web-sealguard -t streamable-http -u 'https://guard.2cstudio.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "2cstudiodev-web-sealguard": {
      "type": "http",
      "url": "https://guard.2cstudio.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “list_empty_token_accounts” rewrote its description, which is the text the model reads
- [security] Tool “scan_wallet” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 136 → 176
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “check_transaction”
- [cosmetic] Tool “list_empty_token_accounts” changed its title: List empty token accounts and the SOL in them → List the SOL a wallet can take back

### 2026-11-12 (score 67)

First indexed and scored.

## MCP tools (4)

### `scan_wallet` (~129 tokens)

Check a Solana wallet

Checks a Solana wallet for risks and gives a 0-100 safety score: open token approvals, phishing airdrops, Token-2022 permanent delegates and transfer restrictions, stake and nonce accounts controlled by someone else, and whether the wallet account itself has been taken over. Also totals the SOL the wallet could take back: empty token accounts, pump.fun deposits, small balances it could sell, and NFTs it could burn. Read-only; returns a link where the owner can fix what was found.

Input parameters:

- `address` (string, required): The Solana wallet address (base58 public key) to check.

### `list_empty_token_accounts` (~153 tokens)

List the SOL a wallet can take back

Lists the SOL a Solana wallet could take back: empty token accounts (left behind by sold or sent tokens) with the rent in each and which ones SealGuard suggests closing (accounts for tokens the owner will likely receive again, or used in the last 30 days, are marked to keep, with the reason); pump.fun and PumpSwap deposits; small balances worth under US$1 that could be sold for SOL through Jupiter; and NFTs whose burn would return their rent. Selling and burning are never suggested by default: they're the owner's call. Read-only; returns a link where the owner can do it.

Input parameters:

- `address` (string, required): The Solana wallet address (base58 public key) to check.

### `list_token_approvals` (~85 tokens)

List open token approvals

Lists every token approval (delegate) on a Solana wallet: which address can still move which token, and how much. Also lists Token-2022 permanent delegates, which holders can't revoke. Read-only; returns a link where the owner can revoke approvals for free.

Input parameters:

- `address` (string, required): The Solana wallet address (base58 public key) to check.

### `check_transaction` (~224 tokens)

Check a Solana transaction before signing

Before a wallet signs a Solana transaction, simulates it on mainnet and says whether it would hand anything over: the wallet account itself, a token account's owner, a standing approval on its tokens, a close authority, stake or nonce authorities. Also lists the SOL and token amounts that would leave and arrive, flags durable nonces (a signed transaction that can be sent much later) and programs SealGuard doesn't know. Verdict: do_not_sign, review or no_red_flags. Read-only: nothing is signed or sent. Paid: needs a SealGuard API key (Authorization: Bearer sgk_…); new keys come with 20 free checks, then US$0.01 a check, or 1,000 a month included with the SealGuard guard. Keys at https://guard.2cstudio.app/mcp-key

Input parameters:

- `signer` (string): The wallet about to sign. Defaults to the fee payer (the first signer).
- `transaction` (string, required): The serialized transaction, base64 (base58 also accepted). Unsigned is fine.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/2cstudiodev-web-sealguard/guard#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 68
- 2026-11-15: 68
- 2026-11-14: 67
- 2026-11-13: 67
- 2026-11-12: 67

## Common questions

### What is the SealGuard MCP server?

SealGuard is an MCP server listed in the public MCP registry as io.github.2cstudiodev-web/sealguard. Check Solana wallets and transactions for risky approvals and scam tokens; find SOL to take back. This page covers its hosted endpoint (https://guard.2cstudio.app/mcp).

### Is the SealGuard MCP server safe to use?

SealGuard scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SealGuard MCP server expose?

SealGuard exposes 4 tools: scan_wallet, list_empty_token_accounts, list_token_approvals, check_transaction. Their descriptions and schemas cost roughly 591 tokens of context every time the server is loaded.

### Does the SealGuard MCP server require authentication?

No. We connected to SealGuard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SealGuard MCP server still maintained?

SealGuard is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the SealGuard MCP server?

VerifyMCP ran 12 checks on SealGuard, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SealGuard: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://guard.2cstudio.app/mcp
- Repository: https://github.com/2cstudiodev-web/sealguard
- Website: https://guard.2cstudio.app/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/2cstudiodev-web-sealguard/guard.xml
- Changelog JSON feed: https://verifymcp.io/servers/2cstudiodev-web-sealguard/guard/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/2cstudiodev-web-sealguard/guard.json
- HTML version of this page: https://verifymcp.io/servers/2cstudiodev-web-sealguard/guard
