WalletWhistle MCP Server

WalletWhistle is a production remote MCP server for read-only product discovery, current prices, biggest drops, item dossiers, and price-history lookups.

This page is the public documentation for the WalletWhistle connector, including setup, access notes, example prompts, privacy links, and support details.

Last updated: 4 April 2026

Description

WalletWhistle tracks products, merchants, categories, and price changes across the site, then exposes that data through a read-only remote MCP server.

The connector is designed for shopping research and price monitoring. It does not place orders, change merchant data, create user content, or perform any write actions.

At A Glance
  • Remote MCP endpoint for Claude-compatible clients.
  • All tools are read-only.
  • No WalletWhistle account, login, or API key is required.
  • Claude-compatible authless access is supported.
Features
  • Search tracked products with merchant and category context.
  • Return the biggest currently tracked price drops.
  • Fetch a single item with metadata and summary text.
  • Return tracked price history for a single item.
  • Render product cards and price-history visuals in MCP app hosts that support interactive UI.
Connection Endpoints

Anthropic-compatible remote MCP endpoint: 

https://mcp.walletwhistle.com/claude

OpenAI/ChatGPT app endpoint: 

https://mcp.walletwhistle.com/mcp

Setup

  1. Open Claude Connectors, Claude Desktop, Claude Code, or another client that supports remote MCP.
  2. If the client asks for a server URL, use https://mcp.walletwhistle.com/claude.
  3. No WalletWhistle account, login, or API key is required.
  4. Start with a prompt such as "Show me the biggest drops right now."

Authentication And Access

WalletWhistle is intended to work as an authless remote MCP server. The connector is read-only and does not require a WalletWhistle user account, password, or API key.

Anthropic's current remote MCP documentation says Claude supports both authless and OAuth-based remote servers. Because WalletWhistle does not expose private user data or any write actions, no user-scoped authorization is required for normal use.

Implementation note: the server currently also exposes OAuth and dynamic client registration endpoints for client interoperability and future compatibility, but that is an implementation detail rather than a user requirement.

Requests may be logged for diagnostics, abuse prevention, and service reliability. See the Privacy Policy for details.

Examples

Example 1: Biggest Drops

User prompt: "Show me the biggest drops right now."

The connector returns the current top price drops with titles, prices, merchant context, and direct item links. In supported MCP app hosts it can also render product cards.

Example 2: Product Search

User prompt: "Get me the biggest noise cancelling headphones drops"

The connector searches tracked items, returns product matches with merchant and category metadata, and can narrow the result set before rendering cards or links.

Example 3: Price History

User prompt: "Show me the price history for this item and plot it if possible."

The connector fetches the selected item or item ID, returns tracked historical price points, and can render a price-history graph in supported MCP app hosts.

Example 4: Merchant-Oriented Browse

User prompt: "Find recent items from Scottsdale Golf with WalletWhistle"

The connector lists or searches merchant-specific products and returns direct item pages so the user can continue browsing on the site if needed.

Privacy Policy

Privacy policy: https://walletwhistle.com/privacy

Support

Support email: [email protected]

Contact page: https://walletwhistle.com/contact

Terms of service: https://walletwhistle.com/terms

WalletWhistle website: https://walletwhistle.com/