Overview
What is Kuru.io MCP Server?
Kuru.io MCP Server is a Model Context Protocol server that provides LLMs and AI assistants with access to real-time market data from the Kuru.io crypto exchange. It offers tools to fetch prices, list all trading pairs, and calculate token values.
How to use Kuru.io MCP Server?
Install dependencies with npm install, build with npm run build, then start as a stdio server using npm start or debug with npm run inspector. In Claude Desktop, add a new MCP tool pointing to node /path/to/kuru-mcp-server/dist/index.js. Use tool commands like get-price, get-all-trading-pairs, or calculate-value with the required parameters.
Key features of Kuru.io MCP Server
- Real-time market data and trending markets
- Caching mechanism with a 5‑minute TTL
get-pricetool for current trading pair pricesget-all-trading-pairstool to list all available pairscalculate-valuetool to convert token amounts between pairs
Use cases of Kuru.io MCP Server
- Ask an LLM for the current price of a specific trading pair
- Retrieve a complete list of trading pairs available on Kuru.io
- Convert an amount of one token into another (e.g., MON → USDC)
- Get trending market information directly through a conversational interface
FAQ from Kuru.io MCP Server
What data does Kuru.io MCP Server provide?
It provides real-time market data including price, volume, and liquidity for trading pairs on Kuru.io, plus trending market information.
What runtime or dependencies are required?
The server runs on Node.js and is built with TypeScript. It uses the Model Context Protocol SDK v1.8.0.
Where is the data sourced from?
Data is fetched from the Kuru.io site API. No user data is stored locally.
Are there any rate limits or caching?
The server implements a built‑in cache with a 5‑minute TTL to reduce API calls. No explicit rate limits beyond the API’s own limits are mentioned.
How is the server transported?
The server runs as a stdio‑based MCP server by default, suitable for use with LLM tools like Claude Desktop. It can also be debugged using the MCP Inspector. No authentication setup is described.