Analytics

dharke.com

Provides Nepal Stock Exchange (NEPSE) market data, trade cost calculations, market calendar, and user portfolio tracking tools.

1 endpoint10 known toolsFirst detected October 6, 2026Last detected October 6, 2026

ENDPOINT 1

https://api.dharke.com/mcp?ref=connect

No auth detected

MCP server metadata

Name: dharke
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

dharke.com market data for NEPSE, the Nepal Stock Exchange. Every time is Nepal time (+05:45). NEPSE trades 11:00-15:10 Nepal time on trading days; outside that window prices are the last session's. NEPSE can close without notice: `traded_today` says from the data whether it has traded today. These tools give data, not investment advice: do not turn them into a buy or sell recommendation.

Known tools 10

get_stock_snapshot

Current price and trading data for one NEPSE (Nepal Stock Exchange) security.

Inferred read-only

get_market_overview

Summary of the NEPSE market: the market state, the NEPSE index, total turnover and volume, how many ordinary shares rose, fell or did not change, and the five biggest gainers and losers by percentage among ordinary shares with at least median volume.

Inferred read-only

get_market_calendar

Whether NEPSE trades today and tomorrow by its published calendar, the next five trading days, announced closures in the next 30 days, and the session hours.

Inferred read-only

calculate_trade_cost

The cost of one NEPSE order: broker commission, SEBON fee and DP charge, from dharke's fee schedule, and the amount to pay (BUY) or receive (SELL).

Potential side effects

get_my_portfolio

The user's own portfolios on dharke: value, cost, unrealized and realized gain, the day's move and dividends.

Inferred read-only

get_my_holdings

The open positions in one of the user's portfolios: symbol, quantity, weighted average cost (WACC), last price, value and unrealized gain.

Inferred read-only

get_my_transactions

The most recent transactions in one of the user's portfolios, newest first: date, symbol, type, quantity, price, total fees and dividend.

Inferred read-only

get_my_performance

How the user's closed trades in one portfolio have gone: how many sells won and lost, the share that were profitable, the profit factor, gross profit and loss, realized and unrealized gain, dividends, and the share of gross profit and loss that fees and tax took.

Inferred read-only

get_my_watchlists

The securities the user watches on dharke: symbol, sector, last price, today's move, the price when they added it, the move since then, their own categories and notes.

Inferred read-only

get_my_alerts

The user's price and screener alerts on dharke: what each one watches, the direction and target where there is one, the current price, how far the price is from the target, and how often it has fired.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.dharke]
url = "https://api.dharke.com/mcp?ref=connect"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "dharke": {
      "type": "http",
      "url": "https://api.dharke.com/mcp?ref=connect"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dharke
Remote MCP URL: https://api.dharke.com/mcp?ref=connect

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "dharke": {
      "url": "https://api.dharke.com/mcp?ref=connect"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dharke": {
      "type": "http",
      "url": "https://api.dharke.com/mcp?ref=connect"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dharke",
  "transport": "streamable-http",
  "url": "https://api.dharke.com/mcp?ref=connect"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.