WalletFollow

io.github.AperiAnalyticsPublished by GitHub account AperiAnalyticsv1.0.0Updated Oct 24, 2026

Read-only Hyperliquid wallet, market and portfolio research with source timestamps and coverage.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

WalletFollow is a remote, read-only MCP server for researching Hyperliquid wallets, markets and portfolios, with source timestamps and coverage notes.

What you can do
Look up Hyperliquid wallet activity and holdings for research purposes, read-only only. Review market data alongside wallet and portfolio information. Check source timestamps and coverage so results can be judged for recency and completeness. No tool list is published, so exact operations are not documented.
When to use it
Useful when you want an assistant to research Hyperliquid wallets, markets or portfolios without any ability to trade or move funds, and when knowing how fresh and how complete the data is matters.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address. OAuth authentication is required; no environment variables or headers are declared. Network access to the provider's service is needed.
Before you install
Requires OAuth sign-in to a third-party hosted service, so account identity is shared with the provider. Data is described as read-only, but the tool list is unpublished, so confirm what each tool does before relying on it. Coverage and timestamps are provider-supplied and may be incomplete or delayed.

Installation

In SourceWeft

  1. Open WalletFollow in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.AperiAnalytics%2Fwalletfollow/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "walletfollow": {
      "type": "http",
      "url": "https://mcp.walletfollow.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 15, 2026

Score

67% 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 listed15 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.