Skip to content

Solana Wallet Tracker & Alerts

by loki.freedomlab.space · remote · no sign-in to list tools · v1.0.2 · published by space.freedomlab.loki

Solana wallet tracker & alerts: real-time activity webhooks, balances, tx history. Free.

Changes · 2

3 tools: 2 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http walletwatch https://loki.freedomlab.space/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 2Claude Code: ask
  • wallet_activityLook up a Solana mainnet wallet: current SOL balance (lamports), the 5 most recent transaction signatures with block time and success/failure, and whether an empty account is a sta…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Look up a Solana mainnet wallet: current SOL balance (lamports), the 5 most recent transaction signatures with block time and success/failure, and whether an empty account is a stake account. Use this to inspect any wallet's recent on-chain activity.
  • watch_walletStart monitoring a Solana wallet.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Start monitoring a Solana wallet. The server polls it every 15s and records each NEW transaction. If you can receive webhooks, pass webhook_url (https). If you cannot, omit it: the server creates a poll token for you — then call get_alerts with it.
Only reads 1Claude Code: allow
  • get_alertsFetch recorded alert events for a watch token (returned by watch_wallet when no webhook_url was given).Reads text others writeNo findings

    Why it is in this group

    • The name "get_alerts" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Fetch recorded alert events for a watch token (returned by watch_wallet when no webhook_url was given). Returns up to 20 most recent events. Poll this periodically.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http walletwatch https://loki.freedomlab.space/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__walletwatch__get_alerts"
    ],
    "ask": [
      "mcp__walletwatch__wallet_activity",
      "mcp__walletwatch__watch_wallet"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as walletwatch. Review it before you use it.

Capability tags behind 2 rules
  • mcp__walletwatch__watch_wallet outbound
  • mcp__walletwatch__get_alerts untrusted-input