xsignal
Server Details
x402 pay-per-call data tools for Base agents. Flagship get_intent ABSTAINS instead of guessing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- philpof102-svg/xsignal
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 6 of 6 tools scored.
Each tool has a clearly distinct purpose: get_intent for momentum verdict, get_preflight for safety+momentum, get_screen for batch preflight, get_signal for social signals, get_token_brief for fused brief, get_token_intel for raw market data. No overlap.
All tools follow the consistent pattern 'get_<noun>', with snake_case for compound nouns (token_brief, token_intel). No mixing of conventions.
6 tools is well-scoped for a specialized token analysis server. Each tool has a clear role, and the count is neither too sparse nor too numerous.
The tool surface covers momentum signals, safety, social signals, market data, and fused summaries. No obvious gaps; it provides a comprehensive toolkit for token analysis.
Available Tools
6 toolsget_intentInspect
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 | Required | Description | Default |
|---|---|---|---|
| addr | Yes | 0x Base token address to read momentum for | |
| question | No | optional free-text label / social query; defaults to the token symbol | |
| min_confidence | No | 0-1; abstain (no verdict, you still pay the flat fee) if mechanical confidence is below this. Default 0.6 |
get_preflightInspect
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 | Required | Description | Default |
|---|---|---|---|
| addr | Yes | 0x Base token address |
get_screenInspect
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 | Required | Description | Default |
|---|---|---|---|
| addrs | Yes | up to 10 0x Base token addresses |
get_signalInspect
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 | Required | Description | Default |
|---|---|---|---|
| limit | No | max items to return (<=25) | |
| query | No | the topic/keywords to get a signal for | |
| terms | No | optional explicit match terms | |
| source | No | xsearch | grok (live source, if a key is set) | |
| candidates | No | optional: your own posts to score instead of a live fetch |
get_token_briefInspect
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 | Required | Description | Default |
|---|---|---|---|
| addr | Yes | 0x Base token address | |
| query | No | optional topic/symbol for the social half; defaults to the token symbol |
get_token_intelInspect
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 | Required | Description | Default |
|---|---|---|---|
| addr | Yes | 0x Base token address |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!