Skills/npm/mcp-server

mcp-server@0.64.1

VERIFIED

Publisher claims: "MCP server for DWLF market analysis platform — exposes market data, indicators, signals, strategies, backtests, portfolio, trade journal, and more as AI-accessible tools" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher dwlf · publishing for 288 daysInstalls 3,333Last detonated 3d ago
$claude mcp add mcp-server -- npx -y @dwlf/mcp-server
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
DWLF_API_KEYConfiguration, not credentials: DWLF_API_URL, DWLF_TOOL_PROFILE
Where it talks to
dwlf.co.uk (its own)
What the honeypot saw
no credential files read · no network
What we could not test
what the tools do when called with real credentials

Connect it with a scoped credential, under the guard. It asks for DWLF_API_KEY and talks to dwlf.co.uk. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind.

$vet-skills run --secrets DWLF_API_KEY=dwlf.co.uk -- npx -y @dwlf/mcp-server

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-11 and scored it 95/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 26 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
6.0sprocessdependency install exit 0
26sclaimed104 tools: dwlf_get_market_data, dwlf_get_quote, dwlf_list_symbols, dwlf_get_support_resistance, dwlf_get_events, dwlf_get_price_picture, dwlf_get_cycle_setups, dwlf_get_ranges, dwlf_get_setup_transitions, dwlf_get_cycle_windows, dwlf_get_stage, dwlf_get_conditions, dwlf_get_indicators, dwlf_get_trendlines, dwlf_get_active_signals, dwlf_get_recent_signals, dwlf_get_signal_stats, dwlf_get_watchlist, dwlf_add_to_watchlist, dwlf_get_briefing_list, dwlf_add_to_briefing_list, dwlf_remove_from_briefing_list, dwlf_list_symbol_tags, dwlf_get_symbol_tags, dwlf_add_symbol_tag
26sprocessscript backend runs setup only
26sprocessno install scripts to re-run

Static findings

No findings across 8,557 lines in 72 files.

Cost to the agent

Instructions loaded
≈79 tok
1 file · 72 in bundle
Tool list per prompt
≈27,560 tok
104 tools · 265 per tool
Handshake
2785 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 552

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @dwlf/mcp-server@0.64.1 as of 3d ago. This is the package itself, not its dependencies.

mcp-server@0.64.1 safety verdict: Verified — KillerSkills