mcp-server@0.72.0
VERIFIEDPublisher 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.
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: BLOCK_API_URL, DWLF_API_URL, DWLF_BLOCK_BACKEND, DWLF_BLOCK_KEY, DWLF_TOOL_PROFILE- Where it talks to
- dwlf.co.uk (its own)
- What we saw when it ran
- 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.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 0.67.0
vet-skills diff mcp-server 0.67.0 0.72.0This version reaches for something 0.67.0 did not: 17 rewritten tool descriptors (dwlf_compile_custom_event, dwlf_create_custom_event, dwlf_describe_strategy_nodes, dwlf_get_conditions, …). Compared from the two recorded runs, not from source.
- Rewritten tool descriptors
- dwlf_compile_custom_event, dwlf_create_custom_event, dwlf_describe_strategy_nodes, dwlf_get_conditions, dwlf_get_custom_event_notifications, dwlf_get_cycle_setups, dwlf_get_cycle_windows, dwlf_get_divergences, dwlf_get_events, dwlf_get_indicators, dwlf_get_market_data, dwlf_get_price_picture +5
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-21 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 · 27 s · 2 scenarios · 0 deviationsStatic findings
No findings across 9,883 lines in 81 files.
Cost to the agent
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
Not checked against OSV yet; the weekly check has not reached this version.