mcp-registry/io.github.philpof102-svg/xsignal · v0.1.0
Also listed as glama/philpof102-svg/xsignal-mcp-server
As of 2026-10-23 07:03 UTC, the Philpof102 Svg Xsignal MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 9 minutes.
x402 pay-per-call data tools for Base agents. Flagship get_intent ABSTAINS instead of guessing.
Claude Code
claude mcp add --transport http philpof102-svg-xsignal-mcp-server https://xsignal-production.up.railway.app/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"philpof102-svg-xsignal-mcp-server": {
"type": "http",
"url": "https://xsignal-production.up.railway.app/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.philpof102-svg%2Fxsignal/fixes
{
"name": "get_intent",
"description": "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 /int",
"inputSchema": {
"type": "object",
"required": [
"addr"
],
"properties": {
"addr": {
"type": "string",
"description": "0x Base token address to read momentum for"
},
"question": {
"type": "string",
"description": "optional free-text label / social query; defaults to the token symbol"
},
"min_confidence": {
"type": "number",
"description": "0-1; abstain (no verdict, you still pay the flat fee) if mechanical confidence is below this. Default 0.6"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_preflight",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"addr"
],
"properties": {
"addr": {
"type": "string",
"description": "0x Base token address"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_screen",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"addrs"
],
"properties": {
"addrs": {
"type": "array",
"items": {
"type": "string"
},
"description": "up to 10 0x Base token addresses"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.philpof102-svg/xsignal"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.philpof102-svg/xsignal"}) over MCP.
get_intent ~269 tokensget_signal ~221 tokensget_token_brief ~186 tokensget_preflight ~179 tokensget_screen ~158 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.philpof102-svg%2Fxsignal?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.philpof102-svg%2Fxsignal?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.philpof102-svg%2Fxsignal.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.philpof102-svg%2Fxsignal.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.philpof102-svg%2Fxsignal?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d8c253662c6d1642…, first seen 2026-10-17, included at leaf 2020 of 50,659. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable finance servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 07:03 UTC, the Philpof102 Svg Xsignal MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 9 minutes.
Philpof102 Svg Xsignal MCP server advertises 6 tools, including get_intent, get_preflight, get_screen, get_signal, get_token_brief.
Point your MCP client at this streamable-http endpoint: https://xsignal-production.up.railway.app/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.