MCP servers › io.github.gdietsch › trading-signals-mcp
MCP server · registry snapshot 2026-11-14 · last tested 2026-11-14
trading-signals-mcp MCP server
Registry name io.github.gdietsch/trading-signals-mcp
by gdietsch · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗
Trading tools for agents: AI trade brief, pre-trade check, event gate, insider buys. Remote or x402 — the publisher's description
Summary
io.github.gdietsch/trading-signals-mcp is a remote and local MCP server listed in the official MCP registry at version 0.1.15, under the namespace of the GitHub account gdietsch. Its linked repository, github.com/gdietsch/trading-signals-mcp, belongs to the same GitHub account. On 2026-11-14 ProtocolProbe connected to it in read-only mode and read its inventory: 21 tools, 0 resources and 0 prompts.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- not met: No known critical or high advisory in the package or its dependencies
- #1,537 of 20,610 packages by monthly downloads
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote and local package
- Transport
- standard input/output, streamable HTTP
- Your own values
- for the package, a secret: X402_PRIVATE_KEY
- Sign-in
- none needed to open a session
- Package
- npm · listed version current
- License
- MIT
- Dependencies
- 2 packages with a critical or high advisory (0 critical, 2 high)
- Repository
- public
- Tools
- 21
- Last tested
- 2026-11-14
Tool list size
10,025 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (21 tools). Counted with Anthropic's token counter on 2026-11-14, from the tool list we read on 2026-11-14. Median across 28,560 counted servers: 2,657 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-14 (signals.incomefather.com), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (0.1.15).
Worth knowing before you connect it
- 2 packages with a critical or high advisory (0 critical, 2 high) in its dependencies (as resolved on 2026-11-14).
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-14
- Mode
- read-only (no tool calls)
- Latest version
- 0.1.15, published 2026-11-14 (registry, as of the 2026-11-14 snapshot)
- First listed version
- 2026-11-10 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 7 versions listed, 2026-11-10 to 2026-11-14; 7 in the 90 days before the 2026-11-14 snapshot.(versions still listed in the registry only)
Most recent 7 versions
0.1.15· 2026-11-140.1.12· 2026-11-110.1.6· 2026-11-110.1.5· 2026-11-110.1.4· 2026-11-100.1.3· 2026-11-100.1.2· 2026-11-10
- Registry data
- snapshot 2026-11-14
- Package and repository
- checked 2026-11-14
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.1.12 (published 2026-11-11) → 0.1.15 (published 2026-11-14), between the registry lists of 2026-11-13 and 2026-11-14.
The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.
Source: the official MCP Registry list on 2026-11-13 and on 2026-11-14; release notes from the GitHub Releases API, checked 2026-11-14.
What it is
What does this server offer?
Observed inventoryNone of its 21 tools are described as changing anything. For 21 the reading was uncertain, so no mark is shown.
- ai_trade_brief
“AI-written summary of the toolkit's own market data for ES/NQ/CL/GC/ZN (event-risk calendar check, session context, Treasury yields, CFTC positioning, SEC insider activity, and the macro event study …”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
3 inputs, 1 required
symbolstringrequired“Futures root: ES (E-mini S&P 500), NQ (E-mini Nasdaq-100), CL (WTI crude), GC (gold), ZN (10-year T-note)”windowinteger“Look-ahead window in minutes (1-240, default 30)”pricenumber“Optional current futures price so typical move sizes can be shown as price levels”
- pre_trade_checkon 7 other servers
“One GO / CAUTION / NO_GO event-risk status with plain reasons for a futures contract: event-risk calendar check + session context (US macro calendar, Treasury yields, CFTC positioning, holidays) + SE…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
4 inputs, 1 required
symbolstringrequired“Futures root: ES (E-mini S&P 500), NQ (E-mini Nasdaq-100), CL (WTI crude), GC (gold), ZN (10-year T-note)”windowinteger“Look-ahead window in minutes (1-240, default 30)”tickerstring“Optional US equity ticker (e.g.”tokenstring“Optional Base ERC-20 token address: adds an A-F token safety verdict”
- token_pre_trade
“One GO / CAUTION / STOP status for a token: the Solana or Base token safety verdict, an OFAC sanctions screen of the token's mint/freeze authority or owner and of an optional counterparty wallet, and…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
5 inputs, 1 required
tokenstringrequired“Solana mint (base58) or Base ERC-20 address (0x…), e.g.”chainstring“Token chain (default: detected from the address)”walletstring“Optional counterparty or paying wallet (Base 0x… or Solana base58)”walletChainstring“Wallet chain (default: detected)”amountnumber“USDC the wallet wants to pay (default 1; needs wallet)”
- cot_screener
“Weekly CFTC Commitments of Traders screener across 45 futures markets (equity indexes, VIX, Treasuries, SOFR, crude, natgas, gold, silver, copper, grains, livestock, softs, FX, BTC, ETH): large-specu…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
4 inputs
extremeboolean“true = only markets flagged crowded_long or crowded_short”assetClassstring“Comma list: equity_index, volatility, rates, energy, metals, grains, livestock, softs, fx, crypto”symbolsstring“Comma list, e.g.”thresholdinteger“Percentile that counts as crowded (default 90)”
- treasury_desk
“US rates snapshot: Treasury par yield curve 1m-30y with 2s10s, 3m10y, 2s5s and 5s30s spreads and 1-day/1-week/1-month changes in bp; upcoming Treasury auctions with ET close time and minutes-to (reop…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
3 inputs
daysinteger“Upcoming-auction lookahead in days (default 14)”resultsinteger“Number of recent auction results (default 6)”billsboolean“true = bills instead of notes, bonds, TIPS and FRNs”
- event_gate
“safeToTrade verdict plus the next high-impact US release (BLS CPI/NFP/PPI, FOMC, Treasury auctions) within a minutes window.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input
windowinteger“Look-ahead window in minutes (1-240, default 30)”
- event_studyon 1 other server
“How ES/NQ/RTY/ZN moved +5/+15/+30/+60 min after each of the last N CPI, NFP (jobs), FOMC, PPI, retail sales, GDP or PCE releases (% and approx.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
4 inputs, 1 required
eventstringrequired“Release type: CPI, NFP (jobs report), FOMC (rate decision), PPI, RETAIL (retail sales), GDP, PCE”symbolstring“Futures root or ETF (default ES)”lookbackinteger“Number of past releases (1-24, default 12)”pricenumber“Optional current price so typical move sizes can be shown as price levels”
- session_briefon 4 other servers
“Session brief for ES/NQ/CL/GC/ZN: upcoming US high-impact releases with ET times and minutes-to, latest/prior BLS values, Treasury 2y/10y/2s10s with daily change, CFTC COT net positioning with 3y per…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
2 inputs, 1 required
symbolstringrequired“Futures root: ES (E-mini S&P 500), NQ (E-mini Nasdaq-100), CL (WTI crude), GC (gold), ZN (10-year T-note)”windowinteger“Look-ahead window in minutes (1-240, default 30)”
- token_verdicton 29 other servers
“Call before an agent buys, swaps into, lists or accepts a Base ERC-20.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
addressstringrequired“Base ERC-20 token contract address”
- solana_token_verdicton 3 other servers
“Call before an agent buys or accepts a Solana SPL or Token-2022 mint (memecoins, pump.fun launches, airdrops).”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
mintstringrequired“Solana token mint address (base58), e.g.”
- whale_flow
“Call before chasing or fading a Base or Solana token move, to see if big wallets are buying or dumping.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
4 inputs, 1 required
tokenstringrequired“Token address: Base ERC-20 0x… or Solana mint (base58)”chainstring“Chain (default: detected from the token format)”hoursinteger“Look-back window in hours (default 24)”minUsdnumber“Minimum trade size in USD (default: auto from liquidity and volume)”
- wallet_pay_readiness
“Before an agent pays: can this Base or Solana wallet pay a given USDC amount?”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
3 inputs, 1 required
addressstringrequired“Wallet address: Base 0x… or Solana base58”chainstring“Chain (default: detected from the address format)”amountnumber“USDC amount to pay (default 1)”
Show 9 more tools
- sanctions_screenon 26 other servers
“Screen a crypto address (any chain: EVM/Base/Ethereum, Bitcoin, Tron, Solana and more, via OFAC's listed digital currency addresses) and/or a person or entity name (fuzzy, scored 0-100) against the o…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
3 inputs
addressstring“Crypto address on any chain, e.g.”namestring“Person or entity name to screen (fuzzy match)”minScoreinteger“Minimum name match score 70-100 (default 85)”
- insider_buyson 2 other servers
“SEC Form 4 open-market insider purchases (code P) for one ticker: insider, role, shares, price, value, dates, per-insider totals and a cluster flag.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
2 inputs, 1 required
tickerstringrequired“US equity ticker, e.g.”daysinteger“Lookback in days (1-90, default 30)”
- insider_clusterson 2 other servers
“Listed tickers where several distinct insiders made open-market purchases (Form 4 code P) in the last N days, with buyers, roles, totals and VWAP.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
2 inputs
daysinteger“Lookback by filing date (1-14, default 7)”minBuyersinteger“Minimum distinct insider buyers (2-10, default 3)”
- sec_13f_holdingson 2 other servers
“Latest SEC Form 13F-HR holdings for one fund manager, by CIK or name (e.g.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
3 inputs
cikinteger“SEC CIK of the manager, e.g.”namestring“Manager name if you don't know the CIK, e.g.”topinteger“Number of top positions (default 25)”
- sec_13f_holders
“Which notable fund managers (Berkshire Hathaway, Pershing Square, Bridgewater, Baupost, Duquesne, Appaloosa, Soros, Tiger Global, Coatue, ARK and ~17 more) hold a stock in their latest SEC 13F-HR: sh…”
Publisher declares: read-only yes · destructive no · idempotent no · open-world yes
1 input, 1 required
tickerstringrequired“US stock ticker, e.g.”
- vwap_bands
“VWAP with standard-deviation bands from your OHLCV bars (session-anchored or full), z-score and band position.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
5 inputs, 1 required
barsarrayrequired“OHLCV bars, oldest first: {t (ISO-8601 or epoch s/ms), o, h, l, c, v} or [t,o,h,l,c,v].”anchorstring“session (reset each tz date, default) or all”bandsarray“Band multipliers, default [1, 2]”tzstring“IANA timezone for sessions (default America/New_York)”includeSeriesboolean“Return the last 500 VWAP points”
- opening_range
“Opening range (first N minutes) high/low/size for the latest session in your bars, breakout state, first breakout and 1x/2x extension targets.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
5 inputs, 1 required
barsarrayrequired“OHLCV bars, oldest first: {t (ISO-8601 or epoch s/ms), o, h, l, c, v} or [t,o,h,l,c,v].”minutesinteger“Opening range minutes (default 15)”sessionStartstring“HH:MM in tz (default 09:30)”sessionEndstring“HH:MM in tz (default 16:00)”tzstring“IANA timezone for sessions (default America/New_York)”
- atr_stop
“Wilder ATR, an ATR-multiple price level, and position size from account risk %.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
8 inputs, 1 required
barsarrayrequired“OHLCV bars, oldest first: {t (ISO-8601 or epoch s/ms), o, h, l, c, v} or [t,o,h,l,c,v].”periodinteger“ATR period (default 14)”multipliernumber“Price-level distance = ATR × multiplier (default 2)”sidestringentrynumber“Entry price (default last close)”accountSizenumber“Account equity”riskPctnumber“% of account risked (default 1)”pointValuenumber“$ per point per contract (ES = 50)”
- backtest_opening_range_breakout
“Opening-range-breakout backtest on your intraday bars: trades, win rate, avg R, total R, profit factor, max drawdown, exits, long/short split and recent trades.”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
9 inputs, 1 required
barsarrayrequired“OHLCV bars, oldest first: {t (ISO-8601 or epoch s/ms), o, h, l, c, v} or [t,o,h,l,c,v].”minutesinteger“Opening range minutes (default 15)”rrnumber“Target in R multiples (default 2)”stopstringdirectionstringcostPerTradenumber“Cost in points per trade”sessionStartstringsessionEndstringtzstring“IANA timezone for sessions (default America/New_York)”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-14.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 93% of 73
- Tools with a description
- 100% of 21
- Typical description length
- 378 characters
The tool set
Counted from the listing
- Tools
- 21
- Size of the list
- about 6,603 tokens for an agent to load (characters ÷ 4)
- Naming
- 21 of 21 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 21 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the npm package x402-trading-signals-mcp
This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"trading-signals-mcp": {
"command": "npx",
"args": [
"-y",
"x402-trading-signals-mcp@0.1.15"
],
"env": {
"X402_PRIVATE_KEY": "<X402_PRIVATE_KEY>"
}
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"trading-signals-mcp": {
"command": "npx",
"args": [
"-y",
"x402-trading-signals-mcp@0.1.15"
],
"env": {
"X402_PRIVATE_KEY": "<X402_PRIVATE_KEY>"
}
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"trading-signals-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"x402-trading-signals-mcp@0.1.15"
],
"env": {
"X402_PRIVATE_KEY": "${input:x402-private-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "x402-private-key",
"description": "X402_PRIVATE_KEY",
"password": true
}
]
}Claude Code
claude mcp add --env "X402_PRIVATE_KEY=<X402_PRIVATE_KEY>" --transport stdio trading-signals-mcp -- npx -y x402-trading-signals-mcp@0.1.15
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"trading-signals-mcp": {
"command": "npx",
"args": [
"-y",
"x402-trading-signals-mcp@0.1.15"
],
"env": {
"X402_PRIVATE_KEY": "<X402_PRIVATE_KEY>"
},
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"trading-signals-mcp": {
"command": "npx",
"args": [
"-y",
"x402-trading-signals-mcp@0.1.15"
],
"env": {
"X402_PRIVATE_KEY": "<X402_PRIVATE_KEY>"
}
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.trading-signals-mcp] command = "npx" args = ["-y", "x402-trading-signals-mcp@0.1.15"] [mcp_servers.trading-signals-mcp.env] "X402_PRIVATE_KEY" = "<X402_PRIVATE_KEY>"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"trading-signals-mcp": {
"command": "npx",
"args": [
"-y",
"x402-trading-signals-mcp@0.1.15"
],
"env": {
"X402_PRIVATE_KEY": "<X402_PRIVATE_KEY>"
}
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -e "X402_PRIVATE_KEY=<X402_PRIVATE_KEY>" -- npx -y x402-trading-signals-mcp@0.1.15
- Replace <X402_PRIVATE_KEY> with your own values; the entry marks X402_PRIVATE_KEY as secret, so keep the file out of version control.
- Optional settings the entry also lists (left out above): MAX_USD_PER_CALL, TRADING_SIGNALS_BASE_URL.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-14 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://signals.incomefather.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"trading-signals-mcp": {
"url": "https://signals.incomefather.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"trading-signals-mcp": {
"type": "http",
"url": "https://signals.incomefather.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"trading-signals-mcp","type":"http","url":"https://signals.incomefather.com/mcp"}'Claude Code
claude mcp add --transport http trading-signals-mcp https://signals.incomefather.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"trading-signals-mcp": {
"type": "streamableHttp",
"url": "https://signals.incomefather.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"trading-signals-mcp": {
"httpUrl": "https://signals.incomefather.com/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.trading-signals-mcp] url = "https://signals.incomefather.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"trading-signals-mcp": {
"url": "https://signals.incomefather.com/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://signals.incomefather.com/mcp --transport http
- Optional settings the entry also lists (left out above): Authorization.
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.1.15
- Latest stable
- 0.1.15
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-14. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-14 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-Utm0Z33c85JGLlNIz…
- Signature
- signed
- License
- MIT
Source: the package registry · 2026-11-14.
Usage
- Downloads
- 2,220 in the last month
Source: api.npmjs.org · 2026-11-14.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Install-time script (npm). No install-time script in the published package.json (version 0.1.15). Source: registry.npmjs.org/x402-trading-signals-mcp/0.1.15 · read 2026-11-14.
- Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: registry.npmjs.org/x402-trading-signals-mcp/0.1.15 · read 2026-11-14.
- Node.js version (npm). Needs Node 18 or later (engines.node
>=18.17). Source: registry.npmjs.org/x402-trading-signals-mcp/0.1.15 · read 2026-11-14. - MCP SDK in the package files. Lists
@modelcontextprotocol/sdkas a dependency (package.json). Source: registry.npmjs.org/x402-trading-signals-mcp/-/x402-trading-signals-mcp-0.1.15.tgz · read 2026-11-14. - Build workflow. No build provenance published for this version. Source: registry.npmjs.org/x402-trading-signals-mcp/0.1.15 · read 2026-11-14.
Registry entry
- Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-14.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-14. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-14. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-14. Source: read 2026-11-14.
- Cline marketplace. Not in the Cline marketplace on 2026-11-14. Source: read 2026-11-14.
Own host
- security.txt. No security.txt at https://signals.incomefather.com/.well-known/ (HTTP 404, 2026-11-14). Source: signals.incomefather.com/.well-known/security.txt · read 2026-11-14.
- A2A agent card. No A2A agent card at https://signals.incomefather.com/.well-known/ (HTTP 404, 2026-11-14). Source: signals.incomefather.com/.well-known/agent-card.json · read 2026-11-14.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint signals.incomefather.com/mcp | Session opened | matches | our test · 2026-11-14 |
| A secret is declared as required | Opened a session without any credential | differs | our test · 2026-11-14 |
| Version 0.1.15 on npm | Exists and can be installed | matches | npm · 2026-11-14 |
| Repository github.com/gdietsch/trading-signals-mcp | Opens publicly | matches | api.github.com · 2026-11-14 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.gdietsch
- GitHub owner
- a personal account (gdietsch)
- Build record
- signed
- Repository
- github.com/gdietsch/trading-signals-mcp
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-14; security policy read from GitHub · 2026-11-12.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Tool list changes
Our reads compared · no tool calledHosted endpoint signals.incomefather.com/mcp
1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-11-12 to 2026-11-14; versions 0.1.12 to 0.1.15).
Last change seen between our reads on 2026-11-12 (version 0.1.12) and 2026-11-14 (version 0.1.15).
Added (1):
whale_flowChanged (2):
solana_token_verdict: descriptiontoken_verdict: descriptionCompared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-14 is not known yet. No tool was called. How it is compared
Choosing
Record checks
Public records · not a safety rating6 of 9 record checks met
- #1,537 of 20,610 packages by monthly downloads
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- Not metNo known critical or high advisory in the package or its dependencies2 packages in its dependencies with a critical or high advisory (npm audit counts packages, not advisories).What changes this check: npm's documentation describes listing a project's dependency advisories with npm audit and applying compatible dependency updates. npm: npm audit
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-14 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.gdietsch/trading-signals-mcp
Answered from the data aboveWho publishes io.github.gdietsch/trading-signals-mcp?
The registry ties the namespace io.github.gdietsch to the GitHub account gdietsch; only its owner can publish under it. Its linked repository, github.com/gdietsch/trading-signals-mcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.gdietsch/trading-signals-mcp safe to install?
We do not rate servers as safe or unsafe. 6 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has packages with advisories (2 high; npm audit). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does io.github.gdietsch/trading-signals-mcp need an API key or sign-in?
It opened a session without any credential on 2026-11-14. The registry entry declares a required secret.
Has io.github.gdietsch/trading-signals-mcp been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.
Does io.github.gdietsch/trading-signals-mcp publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
Yes. The registry lists 0.1.15, the latest stable release on npm.
Where is the source code of io.github.gdietsch/trading-signals-mcp?
In github.com/gdietsch/trading-signals-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (no operator permission)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-11-14, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,127 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 21 tools, 0 resources, 0 prompts.
- 4,640 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.gdietsch/trading-signals-mcp: MCP server record.” Data checked 2026-11-14. https://protocolprobe.com/mcp/servers/io.github.gdietsch/trading-signals-mcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.gdietsch/trading-signals-mcp)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology