Why this verdict
plugin quantdata No issues found
- benign: 89 checks satisfied, no findings for plugin:quantdata
skill quantdata/skills/quantdata-daily-bias No issues found
- benign: 48 checks satisfied, no findings for skill:quantdata/skills/quantdata-daily-bias
skill quantdata/skills/quantdata-max-pain No issues found
- benign: 43 checks satisfied, no findings for skill:quantdata/skills/quantdata-max-pain
skill quantdata/skills/quantdata-weis-wave No issues found
- benign: 38 checks satisfied, no findings for skill:quantdata/skills/quantdata-weis-wave
Security findings 0
No security findings
No suspicious or malicious behavior was found; 1 candidate finding was refuted on review.
Open questions 1
What the analysis could not settle from the code alone.
The local MCP bridge forwards tools/list and tools/call unchanged to the remote https://api.quantdata.uk/mcp, so tool descriptions and schemas come from a mutable remote server that is not shipped here. The bridge's own code is benign, but the remote tool metadata cannot be judged from this evidence.
Tool poisoning
Refuted findings 1
Candidates the review stage examined and rejected, kept for transparency.
Tool poisoning
criticalRefutedlow confidenceThe bundled MCP bridge implements no tools and forwards tools/list and tools/call verbatim to a remote server, so tool descriptions and parameter schemas the agent reads are controlled by a mutable remote endpoint and not by the reviewed artifact.
tools/list 和 tools/call 原样转发给远程
Why it was refuted
The forwarding is the bridge's openly declared core purpose, stated in its own docstring, and not a concealed behavior. It is a plain stdio-to-HTTP relay to the vendor's own endpoint. No injected instruction or poisoned tool metadata is shown, so there is no concrete chain.
