Safetrade Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Safetrade Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Docs-driven Model Context Protocol server for the SafeTrade REST API.
This MCP is intentionally not a one-tool-per-endpoint wrapper. It gives agents a small generic client that reads SafeTrade's OpenAPI docs, validates requests against those docs by default, signs private calls internally, and keeps API secrets out of prompts and command lines.
safetrade_openapiInspect the SafeTrade OpenAPI spec cached by the MCP.
Arguments:
path optional API path, such as /trade/public/tickers or /trade/account/members/memethod optional HTTP method when path is suppliedUse this first to discover paths, methods, query parameters, body schemas, and response shapes.
safetrade_requestExecute a generic SafeTrade REST request.
Arguments:
method: GET, POST, PUT, PATCH, or DELETE; default GETpath: relative SafeTrade API path starting with /query: object of query parametersbody: JSON body for non-GET requestsauth: auto, none, or required; default autovalidate: validate method/path against OpenAPI before sending; default truetimeoutMs: request timeout; default 15000, max 60000confirmDangerous: must be ALLOW_WITHDRAW for withdraw mutations when withdraws are enabled600 is required.SAFETRADE_ALLOW_WITHDRAW=trueconfirmDangerous: "ALLOW_WITHDRAW"For normal agent use, create a SafeTrade API key without withdraw permission and IP-lock it at SafeTrade.
Preferred key file:
{
"apiKey": "...",
"apiSecret": "..."
}Default path:
~/.config/opencode/keys/safetrade.jsonPermissions:
chmod 600 ~/.config/opencode/keys/safetrade.jsonEnvironment variables are also supported:
SAFETRADE_API_KEY=...
SAFETRADE_API_SECRET=...bun installbun run index.tsSelf-test:
bun run index.ts --self-testThe self-test checks:
/trade/public/tickers request returns HTTP 200If credentials are configured, MCP clients can also call private endpoints such as /trade/account/members/me through safetrade_request.
{
"mcpServers": {
"safetrade": {
"type": "stdio",
"command": "/home/cachybtw/.bun/bin/bun",
"args": [
"run",
"/home/cachybtw/.config/opencode/mcp/safetrade-mcp/index.ts"
],
"env": {
"PATH": "/home/cachybtw/.local/bin:/home/cachybtw/.bun/bin:/usr/local/bin:/usr/bin:/bin",
"SAFETRADE_KEYS_FILE": "/home/cachybtw/.config/opencode/keys/safetrade.json"
},
"enabled": true
}
}
}The signing implementation follows SafeTrade's official example client:
X-Auth-Apikey: API keyX-Auth-Nonce: millisecond timestampX-Auth-Signature: HMAC_SHA256(apiSecret, nonce + apiKey) as lowercase hexMIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.