Lattiq x402 Trading Signals

ai.lattiqPublished by lattiq.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Regime-aware ES1/NQ futures trading signals. HMM + 15 quant strategies. x402 USDC micropayments.

VerifiedStreamable HTTPWeb executableFinanceAI & ML

Overview

AI-generated overview

Remote MCP endpoint that returns regime-aware ES1/NQ futures trading signals, paid per call with USDC via the x402 payment header.

What you can do
A remote MCP server that supplies trading signals for ES1/NQ futures, described as regime-aware and built on a hidden Markov model plus 15 quantitative strategies. Tool details are not published in the manifest, so the exact tool names and parameters are unknown. Paid tool calls are settled through the x402 protocol using USDC on Base, signalled by the X-PAYMENT header.
When to use it
Consider it if you want an assistant to pull futures trading signals into an analysis or research workflow without building a signal pipeline yourself. It is a poor fit if you need documented tool schemas, free access, or signals for markets other than ES1/NQ futures.
Requirements
A remote MCP client that can reach over streamable HTTP. No account or API key is declared, but paid calls require the X-PAYMENT header carrying an x402 payment (USDC on Base), so a funded wallet capable of x402 payments is needed. Network access to the endpoint is required.
Before you install
Calls can spend real money: the X-PAYMENT header authorizes USDC payments on Base, so a funded wallet is exposed to per-call charges and the server controls when payment is required. The payment credential is a secret and should not be shared or logged. Tool schemas are not published, so verify cost and behaviour before granting broad use. Signals are financial information, not advice, and the underlying model and strategies cannot be inspected.

Installation

In SourceWeft

  1. Open Lattiq x402 Trading Signals 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/ai.lattiq%2Fx402-trading-signals/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": {
    "lattiq-x402-trading-signals": {
      "type": "http",
      "url": "https://api.lattiq.ai/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v1.0.0LatestSep 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.