mcpField
P
pump.fun launch feed + trend radar

pump.fun launch feed + trend radar

Remote
x402-mcp.huntercarver24.workers.devFinance0Updated 1d ago

About pump.fun launch feed + trend radar

Signal Desk is a pay-per-call MCP service for agents that need live pump.fun launch and trend data, alongside page rendering, file hosting, and callbacks. Calls are paid in USDC on Base through x402, with payment settled only after successful work.

Key features

  1. 01Fetch recent pump.fun token launches
  2. 02Match launches with trend topics
  3. 03Aggregate Google Trends and Polymarket topics
  4. 04Render public pages as Markdown, PNG, or PDF
  5. 05Host files and schedule callbacks

Use cases

  1. 01Monitor new token launches against current topics
  2. 02Compare trends across Google Trends and Polymarket
  3. 03Render a public page for agent analysis
  4. 04Share a temporary file link or schedule a URL callback

MCP support

The service exposes five tools through MCP endpoints, including a feeds-only endpoint for launch and trend data. MCP clients need x402 support to pay automatically; other clients can view the tools and payment-required responses.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://x402-mcp.huntercarver24.workers.dev/feeds/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Signal Desk

monitor

Pay-per-call tools for AI agents, paid in USDC on Base through x402. No account and no API key: the first call answers 402 Payment Required with the price, the agent's wallet signs a transfer for exactly that amount, and the second call gets the result plus a receipt. Settlement happens only after the work succeeded, so a call the service refuses is never charged.

toolHTTP routepricewhat the agent gets
render_pagePOST /render$0.01a public page opened in a real headless Chrome, returned as clean Markdown, a PNG screenshot or a PDF
host_filePOST /files$0.01up to 10 MB stored at a public link for 1 to 168 hours, free to download
schedule_callbackPOST /later$0.005a URL called 60 seconds to 7 days from now (GET, or POST with a JSON body), plus a free status page
recent_launchesPOST /launches$0.005every pump.fun token created in the last N minutes, with its creator, the creator's 7-day launch count, and the live Google Trends or Polymarket topic its name matches
trending_topicsPOST /trends$0.01what is trending now across Google Trends (US) and Polymarket, merged by topic, strongest first, with score, velocity, a type label and the headlines behind it
endpointURL
HTTP routeshttps://x402-paywall.huntercarver24.workers.dev
MCP, all five toolshttps://x402-mcp.huntercarver24.workers.dev/mcp (registry: io.github.huntercarver24/signal-desk)
MCP, the two feeds onlyhttps://x402-mcp.huntercarver24.workers.dev/feeds/mcp (registry: io.github.huntercarver24/pumpfun-trends)

Every route's fields, limits and an example are in its 402 answer and in GET / on the HTTP host. Every refusal (bad input, private address, executable upload) carries the same usage object, free.

Try it before paying. /radar shows the launch feed and trend radar 30 minutes late, free (JSON). For free calls to the live routes, open an issue and ask for a voucher. Send it as an X-Voucher header on any HTTP route, or as a header on the MCP connection: the call's price comes off the voucher instead of a wallet, and a failed call is refunded.

Use it

Use a throwaway wallet holding a few cents of USDC on Base, never a main wallet.

Any HTTP client
import { x402Client } from "@x402/core/client";
import { toClientEvmSigner } from "@x402/evm";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { wrapFetchWithPayment } from "@x402/fetch";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
registerExactEvmScheme(client, {
  signer: toClientEvmSigner(privateKeyToAccount(process.env.X402_PRIVATE_KEY)),
});
const payingFetch = wrapFetchWithPayment(fetch, client);

const res = await payingFetch("https://x402-paywall.huntercarver24.workers.dev/render", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({ url: "https://example.com", format: "markdown" }),
});
console.log(res.status, await res.text());

npm install @x402/core @x402/evm @x402/fetch viem, Node 20 or later, saved as an .mjs file.

Claude Code
claude plugin marketplace add huntercarver24/signal-desk
claude plugin install x402-pay@signal-desk
export X402_PRIVATE_KEY=0x...

The x402-pay skill teaches Claude the five routes and pays them with scripts/pay.mjs. Claude says the price before the first paid call, and each payment runs as a command you approve.

MCP clients that pay x402

An MCP client needs x402 support to pay; any other client still lists the tools and sees each price in a payment-required result. With @x402/mcp:

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
import { x402Client } from "@x402/core/client";
import { toClientEvmSigner } from "@x402/evm";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { wrapMCPClientWithPayment } from "@x402/mcp";
import { privateKeyToAccount } from "viem/accounts";

const mcp = new Client({ name: "my-agent", version: "1.0.0" });
await mcp.connect(
  new StreamableHTTPClientTransport(new URL("https://x402-mcp.huntercarver24.workers.dev/feeds/mcp"))
);
const payment = new x402Client();
registerExactEvmScheme(payment, {
  signer: toClientEvmSigner(privateKeyToAccount(process.env.X402_PRIVATE_KEY)),
});
const paying = wrapMCPClientWithPayment(mcp, payment);

const result = await paying.callTool("trending_topics", { hours: 6, limit: 10 });
console.log(result.content[0].text);

npm install @modelcontextprotocol/sdk @x402/core @x402/evm @x402/mcp viem.

OpenCode
mkdir -p .opencode/plugins && curl -fsSL https://raw.githubusercontent.com/huntercarver24/signal-desk/main/opencode/x402-tools.ts -o .opencode/plugins/x402-tools.ts

Then add the dependencies listed in opencode/package.json to .opencode/package.json; OpenCode installs them at startup. The agent gets the five tools.

ElizaOS

eliza/ is an ElizaOS 1.7 plugin for the two feeds. It adds two paid actions, SIGNAL_DESK_TRENDS and SIGNAL_DESK_LAUNCHES, and a free provider, SIGNAL_DESK_RADAR, with the 30-minute-late preview. It pays with SIGNAL_DESK_VOUCHER or with SIGNAL_DESK_PRIVATE_KEY (USDC on Base). SIGNAL_DESK_MAX_USD_PER_CALL caps the price, default $0.01, and is checked before anything is signed. Build and install steps are in eliza/README.md.

House rules

  • A refused call costs nothing. Neither does a feed that has fallen behind its source: it answers 503 with retry-after instead of charging for stale data.
  • The launch feed and the trend radar are data only. Nothing in them rates, recommends or trades a token. Sports topics and markets are filtered out, by keywords in the title and headlines and by a model check on each topic before it is shown. The free preview also hides vulgar coin names; the paid data is as launched.
  • No caller has an account, so nothing is stored about you beyond the payment on chain. Hosted files expire at the time you choose.

Status

monitor/check.mjs probes every surface a paying agent touches, for free, every 15 minutes: the paywall's health and configuration, a live 402 with its terms, the trend sources' freshness, the launch feed's lag, and both MCP endpoints. The badge above is its latest result.

The launch feed was down from October 29 to November 1, 2026, when its only data provider cut the project off. It now reads Solana through Shyft's free tier, with public endpoints as fallbacks. If it falls behind again, launch calls refuse for free and this monitor fails.

License

MIT. The services themselves are run by Hunter Carver; this repository holds the clients, the uptime check and these docs.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.