io.github.Odds7/fia-signals-mcp
REMOTE · X402.FIASIGNALS.COM
Crypto market intelligence: regime detection, funding rates, liquidations, prices, signals.
Available components
Last scanned (20 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
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 Security46
- 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 8 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 563 tokens (~70/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 26% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "guarded_swap_execute_dry_run_checkout" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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 Nov 26 +41
- HTTPS: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.47 ▲ functional
- 26 Oct 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- HTTPS: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 19 Oct 26 +48
- HTTPS: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 2 Oct 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- HTTPS: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 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
- 25 Sept 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 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
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 4 Nov 2026 · Probed https://x402.fiasignals.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fiasignals.com | CN=YE2,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 52f87671ca091e8411f193982b7706d89a9 |
| SANs: *.fiasignals.com, fiasignals.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 x402.fiasignals.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fiasignals.com. | 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://x402.fiasignals.com/mcp | Verified | 200 | |
| http (plaintext) | http://x402.fiasignals.com/mcp | Served over HTTP | 200 |
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 →
contract_risk_batch_checkout ~70
Return paid x402 contract-risk batch endpoint, 0.50 USDC bundled risk-pack upsell, and ACP contract_risk checkout metadata without making a payment.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| token_addresses | string | yes | Comma-separated EVM token addresses, maximum 5. |
No output schema declared.
No examples provided.
contract_risk_preview ~52
Free live preview for Fia's paid contract_risk/token-safety checkout path.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| token_address | string | yes | EVM token contract address to screen before a swap. |
No output schema declared.
No examples provided.
guarded_swap_execute_dry_run_checkout ~99
Return the free Virtuals ACP direct-buy job-create handoff packet for guarded_swap_execute_dry_run before a Base swap. Metadata only; ACP payment/job creation is buyer-controlled.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | – |
| chain | string | – | – |
| from_token | string | – | – |
| max_slippage_bps | number | – | – |
| risk_tolerance | string | – | – |
| to_token | string | – | – |
No output schema declared.
No examples provided.
offer_angle_ping_acp_checkout ~80
Return the free Virtuals ACP direct-buy job-create handoff packet for offer_angle_ping. Metadata only; ACP payment/job creation is buyer-controlled.
| Name | Type | Req | Description |
|---|---|---|---|
| current_offer | string | – | – |
| current_price | number | – | – |
| goal | string | – | – |
| symptom | string | – | – |
| target_buyer | string | – | – |
No output schema declared.
No examples provided.
pre_trade_risk_batch_checkout ~66
Alias for token_safety_batch_checkout using the /pre-trade-risk/batch buyer-facing path. Metadata only; no payment is made.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| token_addresses | string | yes | Comma-separated EVM token addresses, maximum 5. |
No output schema declared.
No examples provided.
token_safety_batch_checkout ~67
Return paid x402 endpoint, 0.50 USDC bundled risk-pack upsell, and ACP contract_risk checkout metadata without making a payment.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| token_addresses | string | yes | Comma-separated EVM token addresses, maximum 5. |
No output schema declared.
No examples provided.
token_safety_check_acp_checkout ~72
Return the free Virtuals ACP direct-buy job-create handoff packet for token_safety_check before a token swap. Metadata only; ACP payment/job creation is buyer-controlled.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| token_address | string | yes | EVM token contract address to screen before a swap. |
No output schema declared.
No examples provided.
token_safety_free_preview ~57
Rate-limited no-spend token-safety preview plus paid /token-safety x402 upgrade metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| token_address | string | yes | EVM token contract address to screen before a swap. |
No output schema declared.
No examples provided.
How do I install the io.github.Odds7/fia-signals-mcp server?
io.github.Odds7/fia-signals-mcp is a hosted endpoint at https://x402.fiasignals.com/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 · x402.fiasignals.com
claude mcp add --transport http odds7-fia-signals-mcp 'https://x402.fiasignals.com/mcp'
What is the io.github.Odds7/fia-signals-mcp server?
io.github.Odds7/fia-signals-mcp is listed in the public MCP registry as io.github.Odds7/fia-signals-mcp. Crypto market intelligence: regime detection, funding rates, liquidations, prices, signals. This page covers its hosted endpoint (https://x402.fiasignals.com/mcp).
Is the io.github.Odds7/fia-signals-mcp server safe to use?
io.github.Odds7/fia-signals-mcp scores 59 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.Odds7/fia-signals-mcp server expose?
io.github.Odds7/fia-signals-mcp exposes 8 tools: contract_risk_preview, token_safety_free_preview, token_safety_batch_checkout, pre_trade_risk_batch_checkout, contract_risk_batch_checkout, and 3 more. Their descriptions and schemas cost roughly 563 tokens of context every time the server is loaded.
Does the io.github.Odds7/fia-signals-mcp server require authentication?
No. We connected to io.github.Odds7/fia-signals-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Odds7/fia-signals-mcp server still maintained?
io.github.Odds7/fia-signals-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.