Finance · Local MCP server
Signalfuse
11 tools: crypto signals, sentiment, macro regime, arena, search, exec. x402 pay-per-call.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.hypeprinter007-stack/signalfuse- Version
- 1.1.4
- Status
- Active
- Category
- finance
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-26
- Updated
- 2026-08-26
- Publisher
- hypeprinter007-stack (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/hypeprinter007-stack) · how
- Repository
- github.com/hypeprinter007-stack/signalfuse-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | signalfuse-mcp | 1.1.4 | stdio |
How to connect Signalfuse
Signalfuse runs locally from a Node.js package published to the npm registry: signalfuse-mcp version 1.1.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y signalfuse-mcp@1.1.4. It reads the environment variable SIGNALFUSE_CREDIT_TOKEN (secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"signalfuse": {
"command": "npx",
"args": [
"-y",
"signalfuse-mcp@1.1.4"
],
"env": {
"SIGNALFUSE_CREDIT_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from hypeprinter007-stack (GitHub)
| Server | Runs |
|---|---|
| Anchor X402X402-paid agent tools: 18 over HTTP, 14 over stdio. USDC per call, no API key. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
More finance servers
| Server | Runs |
|---|---|
| Signal Nodus SEC FilingsAmendment-safe 10-K/10-Q section diffs, claim checks vs XBRL, 8-K events. Accuracy published. | Remote · HTTPLive check: ✗ no handshake |
| Signal8SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| SignaldaemonNarrative & signal intelligence for AI agents: crypto/AI/macro convergence & divergence. | Remote · HTTPLive check: ✓ handshake |
| SignalEDIEDI parse, validate, send, inspect, and QuickBooks tools for MCP clients. | Local · stdio |
| SignalHarness.ai330 production AI-agent services for data, validation, AI, crypto, and x402 pay-per-use. | Remote · HTTPLive check: ✓ handshake |
| signals.edge graduation radarPump.fun graduation radar for trading bots and AI agents. x402 USDC per scan, no key. | Remote · HTTPLive check: ✓ handshake |
| SignaTrustBlockchain-anchored e-signatures: send envelopes, manage templates, verify anchors on Solana. | Local · stdio |
| SignedAngel investor portfolio, startup deal pipeline, and CRM data from your Signed account. | Remote · HTTPLive check: sign-in required |