crypto-mcp-server

Created By
jkosika year ago
MCP server for crypto exchange
Overview

what is crypto-mcp-server?

crypto-mcp-server is a server designed for managing and facilitating cryptocurrency exchanges, providing a robust backend for trading operations.

how to use crypto-mcp-server?

To use crypto-mcp-server, set up the server environment as per the documentation, configure your exchange parameters, and connect it to your cryptocurrency trading platform.

key features of crypto-mcp-server?

  • Supports multiple cryptocurrency exchanges
  • Real-time transaction processing
  • Secure API for trading operations

use cases of crypto-mcp-server?

  1. Managing trades across different cryptocurrency exchanges.
  2. Facilitating automated trading strategies.
  3. Providing a secure backend for cryptocurrency trading applications.

FAQ from crypto-mcp-server?

  • What exchanges does crypto-mcp-server support?

It supports a variety of popular cryptocurrency exchanges, allowing for flexible trading options.

  • Is crypto-mcp-server open source?

Yes! The project is available on GitHub for anyone to use and contribute.

  • How can I contribute to the project?

You can contribute by submitting issues, feature requests, or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jkosik
Star
0
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago