ToolTrust
A2/100
doggybee

mcp-server-ccxt

mcp1.2.1

@doggybee

High-performance CCXT MCP server for cryptocurrency exchange integration

By doggybee | 37 findings | Scanned 10/15/2026 | tooltrust-scanner/v0.3.20 | 145

Repository health

Popularity and maintenance signals alongside the security grade.

View repository
Stars

145

current snapshot

Forks

36

current snapshot

Contributors

2

public GitHub contributors

Last commit

Jun 3, 2025

GitHub repository activity

Last release

Apr 1, 2025

v1.2.1

Release version

v1.2.1

Latest GitHub release

Stars trend

Daily star additions · History data pending

—

No observed star events yet.

——

Pull request activity

Weekly PR events · History data pending

No observed PR events yet.

——
TypeScriptMITDeveloper Tools621/mo npm downloadsLast scan Oct 15, 2026
1 Low36 Info

Risk Summary

Safe With Normal Controls

Dep Visibility is the main signal, but overall risk remains within an acceptable range.

Potential impact: This finding indicates the tool should be reviewed before it is trusted.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (37)

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout

    set-proxy-config:tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×24

    No metadata.dependencies or repo_url were exposed by this MCP server, and no local project manifest could be inferred from the launch command.

    cache-statsclear-cacheset-log-levellist-exchangesget-tickerbatch-get-tickersget-orderbookget-ohlcvget-tradesget-marketsget-exchange-infoget-leverage-tiersget-funding-ratesget-market-typesaccount-balanceplace-market-orderset-leverageset-margin-modeplace-futures-market-orderget-proxy-configset-proxy-configtest-proxy-connectionclear-exchange-cacheset-market-type

    Fix: Review and remediate the identified issue.

  • InfoAS-010

    🔑Insecure Secret Handling ×11

    input parameter "secret" accepts a credential (informational; not evidence of insecure handling)

    account-balanceplace-market-orderset-leverageset-margin-modeplace-futures-market-order

    input parameter "apiKey" accepts a credential (informational; not evidence of insecure handling)

    account-balanceplace-market-orderset-leverageset-margin-modeplace-futures-market-order

    input parameter "password" accepts a credential (informational; not evidence of insecure handling)

    set-proxy-config

    Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.

  • InfoAS-002

    ⚠️Excessive Permissions

    set-proxy-config:declared capabilities: network access

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y mcp-server-ccxt"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade A](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-a.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)