# WalletFollow [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://walletfollow.ai/mcp  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/walletfollow

## Description
Connect AI assistants to Hyperliquid wallet and portfolio research over Streamable HTTP at https://mcp.walletfollow.ai/mcp. The hosted connector exposes 62 read-only tools for wallet metrics, positions, retained trade history, market observations and published copy portfolios. Responses include source timestamps and coverage limits. Browser OAuth requires a verified WalletFollow account and an eligible research API key; existing plan quotas and permissions apply. This connector cannot execute trades, request wallet signatures or move funds. Public client plugin and skills: https://github.com/AperiAnalytics/walletfollow-plugin.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "walletfollow": {
    "url": "https://mcp.walletfollow.ai/mcp"
  }
}
```

## Documentation

## What WalletFollow does

The WalletFollow MCP server gives AI assistants access to read-only research about Hyperliquid wallets and portfolios. Its hosted connector covers wallet metrics, current positions, retained trade history, market observations, and published copy portfolios. This makes it suitable for agents that need to inspect trading activity or portfolio data without receiving permission to act on-chain.

The connector is listed in the Finance & Fintech category. It is intended for research and analysis workflows where an assistant can retrieve structured information and explain it to a user. Tool responses include source timestamps and coverage limits, so downstream applications can account for data freshness and the scope of available history.

## How it works

Connections use Streamable HTTP through the endpoint at `https://mcp.walletfollow.ai/mcp`. A compatible MCP client sends requests to the hosted service, which returns results from the WalletFollow research connector. The service exposes 62 read-only tools rather than local command-line operations or transaction controls.

Browser-based OAuth requires a verified WalletFollow account and an eligible research API key. Existing plan quotas and permissions continue to apply. The public client plugin and skills are available in the `AperiAnalytics/walletfollow-plugin` repository for workflows that use those published resources.

## Setup and configuration

Configure an MCP-compatible client to use the hosted Streamable HTTP endpoint. When the client uses browser OAuth, sign in with a verified WalletFollow account and provide an eligible research API key as required by the account plan. No local environment variables or local service process are specified in the provided material.

Before deploying an agent, confirm that the WalletFollow account has the permissions and quota needed for the intended research volume. The WalletFollow MCP server is hosted, so the connection target is the remote endpoint rather than a package installed on the agent host.

## Tools and capabilities

The WalletFollow MCP server provides 62 read-only tools spanning:

- Wallet metrics
- Wallet positions
- Retained trade history
- Market observations
- Published copy portfolios

These capabilities support questions such as comparing wallet activity, reviewing positions, examining retained historical trades, and consulting published portfolio data. Returned source timestamps and coverage limits provide context alongside the research results.

## Limitations and notes

The WalletFollow MCP server cannot execute trades, request wallet signatures, or move funds. It should therefore be treated as a research connector rather than a trading or custody interface. Read-only access does not grant an agent authority to approve transactions or control a wallet.

Availability and request volume depend on the account's plan quotas and permissions. Historical results are subject to the stated coverage limits, and timestamps should be checked when recency matters. OAuth access also depends on having a verified WalletFollow account and an eligible research API key.

_Full upstream README: https://allmcps.com/mcp/walletfollow/readme_