mcpbeat

Xsignal MCP Server

io.github.philpof102-svg/xsignal
answering

Xsignal is answering right now. Last checked 9 min ago. 21 installs a week from npm. It exposes 6 tools. Last commit 5 Jul 2026.

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

Installs per day peak 29 · avg 6 · -16% w/w
a month agotoday
Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
279 ms
Response time
average over 24h
21
Installs / week
npm and PyPI

Connect this server

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

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"
    }
  }
}

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

URLTransportStateLatencyChecked
https://xsignal-production.up.railway.app/mcp streamable-http answering 297 ms 9 min ago

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 279 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 279 ms on average, which is faster than 49% 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 21 times in the last week. Week over week that is -16%. 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.