Kuru.io MCP Server

Created By
georgyturevicha year ago
Overview

what is Kuru.io MCP Server?

Kuru.io MCP Server is a Model Context Protocol (MCP) server designed to access Kuru.io crypto exchange data, making it available for LLMs and AI assistants.

how to use Kuru.io MCP Server?

To use the Kuru.io MCP Server, install the dependencies, build the project, and start the server. You can interact with it using various MCP tools for fetching market data.

key features of Kuru.io MCP Server?

  • Access to real-time market data and trending markets.
  • Tools for getting current prices, calculating token values, and listing trading pairs.
  • Built-in caching mechanism to minimize API calls.

use cases of Kuru.io MCP Server?

  1. Fetching real-time prices for cryptocurrency trading pairs.
  2. Analyzing market trends and data for investment decisions.
  3. Integrating with AI assistants for automated trading queries.

FAQ from Kuru.io MCP Server?

  • What programming language is Kuru.io MCP Server built with?

It is built with TypeScript and Node.js.

  • How can I get the current price of a trading pair?

Use the get-price tool with the trading pair symbol.

  • Is there a caching mechanism in place?

Yes, it has a built-in caching mechanism with a 5-minute TTL to reduce API calls.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
georgyturevich
Star
0
Language
TypeScript
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)

5 hours ago
Alloy

2 days ago