Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.hypeprinter007-stack/signalfuse

NPM · SIGNALFUSE-MCP · SCANNED SEP 20

11 tools: crypto signals, sentiment, macro regime, arena, search, exec. x402 pay-per-call.

Available components

0 this week 92 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to hypeprinter007-stack/signalfuse-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 24 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 739 tokens (~67/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 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; "execute_code" 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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.hypeprinter007-stack/signalfuse MCP server?

io.github.hypeprinter007-stack/signalfuse runs locally as an npm package, launched with npx -y signalfuse-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · signalfuse-mcp

# add to Claude Code
claude mcp add hypeprinter007-stack-signalfuse -- npx -y signalfuse-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "hypeprinter007-stack-signalfuse": {
      "command": "npx",
      "args": [
        "-y",
        "signalfuse-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hypeprinter007-stack-signalfuse": {
      "command": "npx",
      "args": [
        "-y",
        "signalfuse-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add hypeprinter007-stack-signalfuse -- npx -y signalfuse-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hypeprinter007-stack-signalfuse": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "signalfuse-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hypeprinter007-stack-signalfuse --command npx --arg -y --arg signalfuse-mcp
# ~/.hermes/config.yaml
mcp_servers:
  hypeprinter007-stack-signalfuse:
    command: "npx"
    args: ["-y", "signalfuse-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hypeprinter007-stack-signalfuse": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "signalfuse-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add hypeprinter007-stack-signalfuse -t stdio -c npx -a -y signalfuse-mcp
// mcp.json
{
  "mcpServers": {
    "hypeprinter007-stack-signalfuse": {
      "command": "npx",
      "args": [
        "-y",
        "signalfuse-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −2
    • Stability: pass → 0.83 functional
    • Package version: 1.1.2 → 1.1.4 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 0
    • Package version: 1.1.2 → 1.1.4 functional
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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 20 Sept 2026 · Analysed npm/signalfuse-mcp@1.1.4

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo hypeprinter007-stack/signalfuse-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/hypeprinter007-stack/signalfuse-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 2607690106
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:6ff327bf3722c6c70d7d7dc05a272a446e4625b94f6045fd7e913a77939a493fc9294d0104bb0542d12478fd103b327fa0d6c4c875327151126a87311

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~739 tokens

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 →

Tool Tokens
check_balance ~41

Check remaining credits for a prepaid credit token. Returns wallet, credits_remaining, and pack info.

NameTypeReqDescription
credit_tokenstringyesCredit token to check balance for

No output schema declared.

No examples provided.

execute_code ~93

Execute code in a sandboxed E2B environment. Supports Python (default) and JavaScript. Max 60s timeout. Paid endpoint.

NameTypeReqDescription
codestringyesCode to execute
credit_tokenstringCredit token for authentication (optional if using x402)
languagestringProgramming language (python or javascript)
timeoutnumberExecution timeout in seconds (max 60)

No output schema declared.

No examples provided.

get_arena_leaderboard ~45

Get the Strategy Arena leaderboard. Returns an array of strategies with wins, losses, total_pnl_bp, win_rate, and total_income_usd. Free endpoint.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_arena_signal ~112

Get a signal from a specific Strategy Arena strategy for a given asset. Returns direction, score, and confidence. Paid endpoint.

NameTypeReqDescription
credit_tokenstringOptional credit token for bulk-prepaid access
strategy_idstringyesStrategy identifier. One of: rsi_7_extremes, ema_5_breakout, bb_squeeze, rsi_reversion_swing, vwap_reversion
symbolstringyesAsset ticker, e.g. BTC, ETH, SOL

No output schema declared.

No examples provided.

get_pricing ~22

Get pricing info for all SignalFuse API endpoints. Free endpoint.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_regime ~48

Get current macro risk regime — risk_on, risk_off, or neutral. Useful for position sizing and directional bias.

NameTypeReqDescription
credit_tokenstringOptional credit token for bulk-prepaid access

No output schema declared.

No examples provided.

get_sentiment ~44

Get raw social sentiment breakdown for a crypto asset.

NameTypeReqDescription
credit_tokenstringOptional credit token for bulk-prepaid access
symbolstringyesAsset ticker

No output schema declared.

No examples provided.

get_signal ~100

Get composite trading signal for a crypto asset. Returns sentiment, macro regime (risk_on/risk_off), funding rate bias, OI delta, signal strength (0-100), confidence, and direction (long/short/neutral). Powered by SignalFuse.

NameTypeReqDescription
credit_tokenstringOptional credit token for bulk-prepaid access
symbolstringyesAsset ticker, e.g. BTC, ETH, SOL, DOGE, PEPE

No output schema declared.

No examples provided.

get_signal_batch ~71

Get fused signals for multiple assets at once. Pass comma-separated symbols or omit for all supported assets.

NameTypeReqDescription
credit_tokenstringOptional credit token for bulk-prepaid access
symbolsstringComma-separated tickers, e.g. BTC,ETH,SOL. Omit for all.

No output schema declared.

No examples provided.

search_brave ~73

Search the web using Brave Search via SignalFuse gateway. Paid endpoint (x402). Returns Brave search results.

NameTypeReqDescription
countnumberNumber of results to return (default 10)
credit_tokenstringOptional credit token for bulk-prepaid access
querystringyesSearch query string

No output schema declared.

No examples provided.

search_tavily ~90

Search the web using Tavily via SignalFuse gateway. Paid endpoint (x402). Returns Tavily search results.

NameTypeReqDescription
credit_tokenstringOptional credit token for bulk-prepaid access
max_resultsnumberMaximum number of results to return
querystringyesSearch query string
search_depthstringSearch depth: "basic" or "advanced"

No output schema declared.

No examples provided.

Common questions

What is the io.github.hypeprinter007-stack/signalfuse MCP server?

io.github.hypeprinter007-stack/signalfuse is an MCP server listed in the public MCP registry as io.github.hypeprinter007-stack/signalfuse. 11 tools: crypto signals, sentiment, macro regime, arena, search, exec. x402 pay-per-call. This page covers its npm package (signalfuse-mcp).

Is the io.github.hypeprinter007-stack/signalfuse MCP server safe to use?

io.github.hypeprinter007-stack/signalfuse scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.hypeprinter007-stack/signalfuse MCP server expose?

io.github.hypeprinter007-stack/signalfuse exposes 11 tools: get_signal, get_regime, get_sentiment, get_signal_batch, get_arena_leaderboard, and 6 more. Their descriptions and schemas cost roughly 739 tokens of context every time the server is loaded.

Is the io.github.hypeprinter007-stack/signalfuse MCP server still maintained?

io.github.hypeprinter007-stack/signalfuse is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.hypeprinter007-stack/signalfuse MCP server under?

io.github.hypeprinter007-stack/signalfuse declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.