nobitex

This MCP server provides access to Nobitex market data via the MCP (Model Context Protocol). It exposes two tools: getMarketStats, which retrieves statistics for a specific cryptocurrency market pair (for example, BTC/IRR or USD/BTC), and getGlobalStats, which returns global statistics for the cryptocurrency market. You can connect to this MCP server using your MCP client or the evals workflow described in the repository, and issue requests to fetch real-time market data from Nobitex. The server is intended to be run locally and accessed through MCP tooling that understands the MCP tools namespace and method names.

To use the evals environment described in the README, you can preload environment variables (for example, OPENAI_API_KEY) and run the evaluation script with npx mcp-eval to exercise the available tools. Typical usage pattern involves targeting the tools/market.tools.ts module (or equivalent) to invoke getMarketStats and getGlobalStats and process the responses in your client.

Prerequisites:

• Node.js and npm installed on your system
• Access to the repository containing this Nobitex MCP server

Installation steps:

1. Install dependencies

npm install

2. Start the MCP server

npm run start

3. Verify the server is running (optional)

• Check the console for a startup message indicating the server is listening for MCP requests.
• Or attempt a test request using your MCP client.

Tips and common considerations:

• The server is accessed via the MCP tooling; ensure your MCP client is configured to connect to the server and use the available tools getMarketStats and getGlobalStats.
• When integrating with Claude Desktop, use the provided configuration snippet to point the client to the local repository path where this server runs.
• If you need to pass environment variables to the evals workflow, prepend them to the command, for example: OPENAI_API_KEY=your-key npx mcp-eval evals.ts tools/market.tools.ts
• If you encounter connectivity issues, confirm that the server process started successfully and is listening on the expected port/domain, and that any firewall rules allow local MCP communication.