Shoonya MCP Server (Mock)

Created By
onlyzerosoncea year ago
Overview

what is Shoonya MCP Server?

Shoonya MCP Server is a mock Market Connectivity Protocol (MCP) server designed to simulate interactions with a Shoonya-like trading API, providing a framework for testing client applications that connect for order placement and market data.

how to use Shoonya MCP Server?

To use the Shoonya MCP Server, clone the repository, install the required dependencies, and run the Flask development server. You can then interact with the API endpoints to simulate trading operations.

key features of Shoonya MCP Server?

  • Authentication: Simulates client authentication with a /connect endpoint.
  • Order Management: Allows placing trading orders with validation and mock responses.
  • Market Data (Mock): Simulates market data subscription and retrieval through dedicated endpoints.
  • API Definition: Detailed API documentation is provided for developers.

use cases of Shoonya MCP Server?

  1. Testing client applications for trading functionalities.
  2. Simulating order placements and market data interactions without real financial transactions.
  3. Developing and debugging trading applications in a controlled environment.

FAQ from Shoonya MCP Server?

  • Is this server connected to the live Shoonya trading platform?

No, it is a mock server and does not connect to live systems.

  • Can I use this for real trading?

No, this server is intended for development and testing only, with no real financial transactions occurring.

  • What technologies are used?

The server is built using Python and Flask.

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