Wallet Doctor

io.github.zikrizPublished by GitHub account zikrizv0.2.3Updated Oct 24, 2026

Solana wallet forensics SDK, x402 pay-per-call, AI agents.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

A Solana wallet forensics SDK exposed as an MCP server, with x402 pay-per-call access for AI agents.

What you can do
Provides Solana wallet forensics capabilities to an assistant, per the registry description, which frames it as an SDK for investigating wallet activity on Solana. Access is described as x402 pay-per-call, meaning individual calls are billed through the x402 payment scheme. No tool list, instructions or README were supplied, so the exact operations available cannot be confirmed from this entry.
When to use it
Consider it when an assistant needs Solana wallet forensics data and you are prepared to pay per call through x402. Because no tool list or documentation is provided, verify its actual capabilities before relying on it.
Requirements
Runs either as a remote streamable HTTP endpoint or as a local process from the PyPI package wallet-doctor over stdio. No authentication, environment variables or headers are declared. x402 pay-per-call implies a payment-capable client or wallet setup.
Before you install
Calls are described as pay-per-call via x402, so usage can spend money; set limits before connecting. No authentication is declared, so check what wallet or payment credentials the client must supply. The server is third-party and undocumented here, so review its behavior before sending sensitive data.

Installation

In SourceWeft

  1. Open Wallet Doctor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.zikriz%2Fwallet-doctor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "wallet-doctor": {
      "type": "http",
      "url": "https://defi-webhook.m-zikriz.workers.dev/api/agent"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.2.3LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.