io.github.philpof102-svg/xsignal
REMOTE · XSIGNAL-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED SEP 22
x402 pay-per-call data tools for Base agents. Flagship get_intent ABSTAINS instead of guessing.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.philpof102-svg/xsignal MCP server?
io.github.philpof102-svg/xsignal is a hosted endpoint at https://xsignal-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · xsignal-production.up.railway.app
claude mcp add --transport http philpof102-svg-xsignal 'https://xsignal-production.up.railway.app/mcp'
{
"mcpServers": {
"philpof102-svg-xsignal": {
"url": "https://xsignal-production.up.railway.app/mcp"
}
}
} {
"servers": {
"philpof102-svg-xsignal": {
"type": "http",
"url": "https://xsignal-production.up.railway.app/mcp"
}
}
} [mcp_servers.philpof102-svg-xsignal] url = "https://xsignal-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"philpof102-svg-xsignal": {
"type": "remote",
"url": "https://xsignal-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add philpof102-svg-xsignal --url 'https://xsignal-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
philpof102-svg-xsignal:
url: "https://xsignal-production.up.railway.app/mcp" {
"McpServers": {
"philpof102-svg-xsignal": {
"Transport": "http",
"Url": "https://xsignal-production.up.railway.app/mcp"
}
}
} assistant mcp add philpof102-svg-xsignal -t streamable-http -u 'https://xsignal-production.up.railway.app/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://xsignal-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of xsignal-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://xsignal-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://xsignal-production.up.railway.app/mcp | HTTPS enforced | 301 | https://xsignal-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_intent ~264
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
| Name | Type | Req | Description |
|---|---|---|---|
| addr | string | yes | 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 |
No output schema declared.
No examples provided.
get_preflight ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| addr | string | yes | 0x Base token address |
No output schema declared.
No examples provided.
get_screen ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| addrs | array | yes | up to 10 0x Base token addresses |
No output schema declared.
No examples provided.
get_signal ~173
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
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_token_brief ~151
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
| Name | Type | Req | Description |
|---|---|---|---|
| addr | string | yes | 0x Base token address |
| query | string | – | optional topic/symbol for the social half; defaults to the token symbol |
No output schema declared.
No examples provided.
get_token_intel ~106
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…).
| Name | Type | Req | Description |
|---|---|---|---|
| addr | string | yes | 0x Base token address |
No output schema declared.
No examples provided.
What is the io.github.philpof102-svg/xsignal MCP server?
io.github.philpof102-svg/xsignal is an MCP server listed in the public MCP registry as io.github.philpof102-svg/xsignal. x402 pay-per-call data tools for Base agents. Flagship get_intent ABSTAINS instead of guessing. This page covers its hosted endpoint (https://xsignal-production.up.railway.app/mcp).
Is the io.github.philpof102-svg/xsignal MCP server safe to use?
io.github.philpof102-svg/xsignal scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.philpof102-svg/xsignal MCP server expose?
io.github.philpof102-svg/xsignal exposes 6 tools: get_intent, get_token_brief, get_signal, get_token_intel, get_preflight, get_screen. Their descriptions and schemas cost roughly 970 tokens of context every time the server is loaded.
Does the io.github.philpof102-svg/xsignal MCP server require authentication?
No. We connected to io.github.philpof102-svg/xsignal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.philpof102-svg/xsignal MCP server still maintained?
io.github.philpof102-svg/xsignal is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.