Xsignal MCP Server

by philpof102-svg Your server? Claim it

answering

Xsignal is answering right now. Last checked 16 min ago. 35 installs a week from npm. It exposes 6 tools. Last commit 18 Aug 2026.

x402 pay-per-call data tools for Base agents. Flagship get_intent ABSTAINS instead of guessing.

Installs per day peak 10 · avg 4 · +179% w/w

a month agotoday

Uptime history 48 days of history · worst day 71%

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

289 ms

Response time

average over 24h

Installs / week

npm and PyPI

Nothing serious here today

Today is the operative word: we check Xsignal every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 16 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add xsignal --transport http https://xsignal-production.up.railway.app/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "xsignal": {
      "url": "https://xsignal-production.up.railway.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.xsignal]
url = "https://xsignal-production.up.railway.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "xsignal": {
      "url": "https://xsignal-production.up.railway.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "xsignal": {
      "url": "https://xsignal-production.up.railway.app/mcp"
    }
  }
}

This one needs environment variables set before it will start: XSIGNAL_WALLET (Your 0x Base address for 3 free calls per wallet; beyond that the tools return an x402 pay pointer.). The author declared them in the registry entry; get the values from the project itself.

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

token

get_token_brief

A fused MEAL: one call combines Base token market intel + real-time social signal into a single "what is happening with $TOKEN right now" brief - market flags + top CITED social posts + a plain-language, non-advisory summary. Saves an agent the fetch-and-fuse work. x402-paid at GET/POST /brief ($0.05; 3 free per wallet via ?wallet=0x…). Example: GET /brief?addr=0x4ed4…&q=degen

get_token_intel

Base token MARKET data (liquidity, 24h volume, price + change, pool age, buy/sell flow, mechanical flags) from public DEX pools. Market data, NOT a trust/safety rating. Best used as an input to get_token_brief. x402-paid at GET/POST /token ($0.01; 3 free per wallet via ?wallet=0x…).

intent

get_intent

FLAGSHIP. An outcome-priced momentum verdict that ABSTAINS below your confidence bar - the only x402 signal that refuses to answer (honestly) when it is not sure. Post {addr, min_confidence 0-1} then pay $0.01, and get a mechanical momentum verdict "gaining" or "fading" IF the signal agreement clears your bar, else a calibrated "abstain". Paid answers carry a keyless tamper-evidence receipt. confidence is a transparent heuristic, NOT a prediction; not financial advice. x402-paid at GET/POST /intent (3 free calls per wallet via ?wallet=0x…). Example: GET /intent?addr=0x4ed4E862860beD51a9570b96d89aF5E1B0Efefed&min_confidence=0.7

preflight

get_preflight

The Base PREFLIGHT: one call fuses MainStreet on-chain SAFETY (SAFE/WATCH/AVOID + rug flags) with xsignal MOMENTUM (the abstaining read) into a single recommendation (GO / CAUTION / AVOID / AVOID_ENTRY / NEUTRAL / UNVERIFIED) answering "is this token safe to touch AND moving?". Safety GATES momentum - never green-lights a token that can rug. x402-paid at GET/POST /preflight ($0.05; 3 free per wallet via ?wallet=0x…). Input: addr (0x Base token). Not financial advice.

screen

get_screen

BATCH watchlist screen: run the preflight (safety ⊕ momentum) over up to 10 Base tokens in one call → which are GO (safe + moving), plus a per-token verdict + a summary count. For an agent screening a watchlist. x402-paid at GET/POST /screen ($0.10; 3 free per wallet via ?wallet=0x…). Input: addrs (array or comma-separated 0x addresses). Not financial advice.

signal

get_signal

Real-time X/social signal for a topic: scored (virality + freshness) and CITED (source urls), deduped and ranked. Input: query (topic) OR candidates[] (bring your own posts to score). x402-paid at GET/POST /signal ($0.01; 3 free per wallet via ?wallet=0x…). Example: GET /signal?q=base+memecoin

Endpoints

URL	Transport	State	Latency	Checked
https://xsignal-production.up.railway.app/mcp	streamable-http	answering	264 ms	16 min ago

Alternatives to Xsignal

same job, measured the same way

Agent Data API

by ptrgit1

19 pay-per-call data tools for AI agents: crypto/DeFi, web, PDF, FX, weather, DNS. x402 on Base.

326 installs/wk local only

Agent Web Reader

by charliemorrison

Pay-per-call data tools for AI agents: crypto signal, web reader, SEO audit. x402 USDC on Base.

3 tools answering

X402 API

by fernsugi

DeFi data API for AI agents — pay-per-call via x402/USDC on Base

41 installs/wk local only

Polyform

by polyform

Pay-per-call data APIs for AI agents. USDC on Base via x402. 33 tools, no signup.

67 tools answering

x402-vend — WebIntel

by omarnassar1127

Pay-per-call web & EU business intelligence for AI agents (x402 USDC on Base). 11 tools.

11 tools answering

Oromi Agent Services

by oromi-uk

25 pay-per-call UK data & verification tools for AI agents. x402 USDC on Base; free quote mode.

39 installs/wk local only

Blixtworks

by blixtworks-www

63 pay-per-call tools for agents: vision, text, data, web, blockchain. USDC on Base via x402.

85 installs/wk 68 tools answering

Instagram data for agents

by fetcher-instagram

16 Instagram endpoints. Pay per call in USDC via x402.

18 tools answering

Xsignal — questions

Answers built from our own checks of this server.

What can Xsignal do?

It exposes 6 tools, read directly from the server on our last check. Among them: get_intent, get_preflight, get_screen, get_signal, get_token_brief, get_token_intel. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Xsignal working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 289 ms. The bar chart above shows every period we have measured.

How do I connect Xsignal?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Xsignal need an API key?

No. Xsignal completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Xsignal?

It answers our handshake in 289 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Xsignal?

The npm package @rakshasar/xsignal was installed 35 times in the last week. Week over week that is +179%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Xsignal open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.