signalfuse-mcp
npm
v1.1.4
Source verified
Published by hypeprinter007-stack — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for SignalFuse — AI trading intelligence with 11 tools: real-time signals, market sentiment, macro regime, live strategy arena, web search (Brave/Tavily), sandboxed code execution (E2B). Pay-per-call via x402 micropayments.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Tool "execute_code" appears to run shell commands or evaluate code (keyword "execute code" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool execute_code
Tool "execute_code" takes a command-shaped parameter "code" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool execute_code · inputSchema.properties.code
Tool "execute_code" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool execute_code
Each tool and what it can reach — statically extracted from the published source.
execute_coderuns code / shellcheck_balanceno sensitive capabilityget_arena_leaderboardno sensitive capabilityget_arena_signalno sensitive capabilityget_pricingno sensitive capabilityget_regimeno sensitive capabilityget_sentimentno sensitive capabilityget_signalno sensitive capabilityget_signal_batchno sensitive capabilitysearch_braveno sensitive capabilitysearch_tavilyno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.1.4 latest |
A 94/100 | 3 | 1.13.0 | 2026-09-07 |
v1.1.2 |
A 93/100 | 3 | 1.13.0 | 2026-08-25 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan signalfuse-mcp --online
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.