# io.github.philpof102-svg/xsignal (remote · xsignal-production.up.railway.app)

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

- Trust score: 55/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `xsignal-production.up.railway.app`: 55/100 (this document), [markdown](https://verifymcp.io/servers/philpof102-svg-xsignal/xsignal-production.md), [page](https://verifymcp.io/servers/philpof102-svg-xsignal/xsignal-production)
- npm · `@rakshasar/xsignal`: 34/100, [markdown](https://verifymcp.io/servers/philpof102-svg-xsignal/rakshasar-xsignal.md), [page](https://verifymcp.io/servers/philpof102-svg-xsignal/rakshasar-xsignal)

## Channel facts

- Endpoint: `https://xsignal-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 35/100
  - AI-judged instruction clarity (poor).
  - Context-footprint check failed: tool/resource definitions use about 970 tokens (~161/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http philpof102-svg-xsignal https://xsignal-production.up.railway.app/mcp
```

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "philpof102-svg-xsignal": {
      "type": "remote",
      "url": "https://xsignal-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add philpof102-svg-xsignal --url https://xsignal-production.up.railway.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  philpof102-svg-xsignal:
    url: "https://xsignal-production.up.railway.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "philpof102-svg-xsignal": {
      "type": "http",
      "url": "https://xsignal-production.up.railway.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 53, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 52, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 50, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 49)

First indexed and scored.

## MCP tools (6)

### `get_intent` (~264 tokens)

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

Input parameters:

- `addr` (string, required): 0x Base token address to read momentum for
- `min_confidence` (number): 0-1; abstain (no verdict, you still pay the flat fee) if mechanical confidence is below this. Default 0.6
- `question` (string): optional free-text label / social query; defaults to the token symbol

### `get_token_brief` (~151 tokens)

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

Input parameters:

- `addr` (string, required): 0x Base token address
- `query` (string): optional topic/symbol for the social half; defaults to the token symbol

### `get_signal` (~173 tokens)

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

Input parameters:

- `candidates` (array): optional: your own posts to score instead of a live fetch
- `limit` (integer): max items to return (<=25)
- `query` (string): the topic/keywords to get a signal for
- `source` (string): xsearch | grok (live source, if a key is set)
- `terms` (array): optional explicit match terms

### `get_token_intel` (~106 tokens)

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…).

Input parameters:

- `addr` (string, required): 0x Base token address

### `get_preflight` (~151 tokens)

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.

Input parameters:

- `addr` (string, required): 0x Base token address

### `get_screen` (~125 tokens)

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.

Input parameters:

- `addrs` (array, required): up to 10 0x Base token addresses

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/philpof102-svg-xsignal/xsignal-production#diagnostics

## Score history

- 2026-08-04: 55
- 2026-08-03: 55
- 2026-08-02: 54
- 2026-08-01: 54
- 2026-07-31: 53
- 2026-07-30: 52
- 2026-07-29: 51
- 2026-07-28: 51
- 2026-07-27: 50
- 2026-07-26: 49

## Links

- Remote endpoint: https://xsignal-production.up.railway.app/mcp
- Repository: https://github.com/philpof102-svg/xsignal
- Changelog RSS feed: https://verifymcp.io/servers/philpof102-svg-xsignal/xsignal-production/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/philpof102-svg-xsignal/xsignal-production/changelog.json
- HTML version of this page: https://verifymcp.io/servers/philpof102-svg-xsignal/xsignal-production