io.github.manavaga/web3-signals
REMOTE · WEB3-SIGNALS-API-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED AUG 3
Crypto signal intelligence: 20 assets, 6 dimensions, regime detection, portfolio optimizer
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 →
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 10 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 910 tokens (~91/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · web3-signals-api-production.up.railway.app
claude mcp add --transport http manavaga-web3-signals https://web3-signals-api-production.up.railway.app/mcp/stream
[mcp_servers.manavaga-web3-signals] url = "https://web3-signals-api-production.up.railway.app/mcp/stream"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"manavaga-web3-signals": {
"type": "remote",
"url": "https://web3-signals-api-production.up.railway.app/mcp/stream",
"enabled": true
}
}
} openclaw mcp add manavaga-web3-signals --url https://web3-signals-api-production.up.railway.app/mcp/stream --transport streamable-http
mcp_servers:
manavaga-web3-signals:
url: "https://web3-signals-api-production.up.railway.app/mcp/stream" {
"mcpServers": {
"manavaga-web3-signals": {
"type": "http",
"url": "https://web3-signals-api-production.up.railway.app/mcp/stream"
}
}
} 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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 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
- 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +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.
- 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 58
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 3 Aug 2026 · Probed https://web3-signals-api-production.up.railway.app/mcp/stream/ · Declared URL https://web3-signals-api-production.up.railway.app/mcp/stream
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 |
DNSSEC insecure
Validation of web3-signals-api-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 |
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://web3-signals-api-production.up.railway.app/mcp/stream | Redirected | 307 | https://web3-signals-api-production.up.railway.app/mcp/stream/ |
| streamable-http · followed | https://web3-signals-api-production.up.railway.app/mcp/stream/ | Verified | 200 | |
| http (plaintext) | http://web3-signals-api-production.up.railway.app/mcp/stream | HTTPS enforced | 301 | https://web3-signals-api-production.up.railway.app/mcp/stream |
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.
compare_assets ~73
Which crypto should I buy — BTC, ETH, or SOL? Compare 2-5 cryptocurrencies ranked by signal strength. Input: comma-separated tickers (e.g. 'BTC,ETH,SOL'). Returns ranked comparison with scores, direction, and verdict. Use for portfolio allocation decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_all_signals ~85
Get buy/sell signals for all 20 major cryptocurrencies including Bitcoin, Ethereum, Solana, and more. Returns a 0-100 composite score and direction (bullish/bearish/neutral) for each asset, plus portfolio summary with market regime and risk level. Updated every 15 minutes. For full dimension breakdown and AI insights, use the paid REST API.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_analytics ~57
Who is using AgentMarketSignal? See API usage statistics including total requests, unique clients, response times, breakdowns by endpoint and client type (AI agents, browsers, scripts). Useful for understanding adoption.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_asset_performance ~53
How accurate are the signals for BTC specifically? Get per-asset accuracy metrics for any cryptocurrency. Returns 30-day rolling accuracy, total signals evaluated, and comparison to overall accuracy.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_asset_signal ~140
Is BTC bullish or bearish right now? Get a 0-100 buy/sell score for any cryptocurrency. Returns composite score, direction (bullish/bearish/neutral), signal label (STRONG BUY to STRONG SELL), and momentum. Supports: BTC, ETH, SOL, BNB, XRP, ADA, AVAX, DOT, MATIC, LINK, UNI, ATOM, LTC, FIL, NEAR, APT, ARB, OP, INJ, SUI. For the full 6-dimension breakdown with whale, technical, and derivatives analysis, use the paid REST API.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_crypto_price ~125
What is the current price of Bitcoin, Ethereum, or any major crypto? Returns the latest USD price, 24-hour price change percentage, trading volume, and market cap. Updated every 15 minutes from CoinGecko and Binance. Supports 20 assets: BTC, ETH, SOL, BNB, XRP, ADA, AVAX, DOT, MATIC, LINK, UNI, ATOM, LTC, FIL, NEAR, APT, ARB, OP, INJ, SUI. Example: get_crypto_price('BTC')
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_health ~59
Is AgentMarketSignal working? Check the real-time status of all 5 AI data pipelines (whale tracking, technical analysis, derivatives, narrative sentiment, market data) and the signal fusion engine. Returns last run times, durations, and any errors.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_market_briefing ~84
What should I buy or sell in crypto right now? Returns the top 3 buy and top 3 sell recommendations from 20 cryptocurrencies, plus market regime (trending/ranging), risk level, and momentum. Best starting point for portfolio decisions. Scores range 0-100: above 62 is a buy signal, below 38 is a sell signal.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_performance ~59
How accurate are these crypto signals? Returns 30-day rolling accuracy metrics showing how often buy/sell predictions were correct. Includes overall accuracy percentage, reputation score (0-100), and breakdowns by asset and timeframe (24h/48h).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_x402_stats ~51
How much revenue has AgentMarketSignal generated? View x402 micropayment analytics including total paid calls, revenue in USDC, payment conversion rate, and daily payment timeline.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.