Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.redoxnet/lsopenapi

NUGET · REDOXNET.MCP.LSOPENAPI · SCANNED SEP 21

LS Securities OpenAPI MCP server: Korean + overseas stocks, charts, screeners, portfolio, accounts.

Available components

nuget · RedoxNet.Mcp.LsOpenApi 81
0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 115 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 23877 tokens (~477/item across 50 items; 50 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 50 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 51 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.redoxnet/lsopenapi MCP server?

io.github.redoxnet/lsopenapi runs locally as a NuGet package, launched with dnx RedoxNet.Mcp.LsOpenApi@1.6.0 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

nuget · RedoxNet.Mcp.LsOpenApi

# add to Claude Code
claude mcp add redoxnet-lsopenapi -- dnx RedoxNet.Mcp.LsOpenApi@1.6.0 --yes
// .cursor/mcp.json
{
  "mcpServers": {
    "redoxnet-lsopenapi": {
      "command": "dnx",
      "args": [
        "RedoxNet.Mcp.LsOpenApi@1.6.0",
        "--yes"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "redoxnet-lsopenapi": {
      "command": "dnx",
      "args": [
        "RedoxNet.Mcp.LsOpenApi@1.6.0",
        "--yes"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add redoxnet-lsopenapi -- dnx RedoxNet.Mcp.LsOpenApi@1.6.0 --yes
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "redoxnet-lsopenapi": {
      "type": "local",
      "command": [
        "dnx",
        "RedoxNet.Mcp.LsOpenApi@1.6.0",
        "--yes"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  redoxnet-lsopenapi:
    command: "dnx"
    args: ["RedoxNet.Mcp.LsOpenApi@1.6.0", "--yes"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "redoxnet-lsopenapi": {
      "Transport": "stdio",
      "Command": "dnx",
      "Arguments": [
        "RedoxNet.Mcp.LsOpenApi@1.6.0",
        "--yes"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "redoxnet-lsopenapi": {
      "command": "dnx",
      "args": [
        "RedoxNet.Mcp.LsOpenApi@1.6.0",
        "--yes"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed nuget/RedoxNet.Mcp.LsOpenApi@1.6.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem nuget
Reason Signature present, unreadable

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 50 exposed · ~21,382 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ls_watched_themes ~243

Manages the local watched-themes list (LS t1531 theme codes); no LS credentials needed to save. `action`: "list" (watched themes, enriched with t1531 avgdiff as change_pct when credentials exist), "add" (requires `theme_code` — a 4-char tmcode, e.g. '0064' 2차전지; optional `theme_name`, `note`), "remove" (drops `theme_code`). USE WHEN the user wants to track / 관심 테마 추가 an LS theme; theme codes are not stock short codes (use ls_watchlist for stocks). v0.10 BREAKING: replaces ls_watched_themes_add / _remove / _list.

NameTypeReqDescription
actionstringyesOperation to perform: 'list', 'add', or 'remove'.
notestring–add: optional user note for this theme.
theme_codestring–add / remove: LS theme code (tmcode, 4-char), e.g. '0064'.
theme_namestring–add: optional human-readable theme name (defaults to theme_code).

No output schema declared.

No examples provided.

ls_watchlist ~516

Manages the local saved watchlist — stock items and their groups. Does not require LS credentials to save. Pick the operation with `action`: - action="list" — lists watchlist data. Default returns grouped items, each enriched with current price / change_pct (batch t8407 when LS credentials are available; partial quote failures allowed). `scope="groups"` instead returns group metadata only ({name, description, sort_order, item_count}). Optional `group_name` filters items. - action="add" — adds `shcode` to a watchlist group (`group_name`, defaults 'default'). Optional `note`. The item is saved even when LS credentials are unavailable. - action="remove" — removes `shcode` from `group_name` (defaults 'default'). - action="group_upsert" — creates a group, updates its description, or renames one. `name` is the target group name; with `rename_from` set it renames that group to `name`, otherwise it inserts (or upserts the description). Optional `description`. - action="group_delete" — deletes the group `name` and cascades its saved items. USE WHEN: the user wants to remember / track / 관심종목 추가 a stock, see their watchlist, or manage watchlist groups. AVOID for general market questions unrelated to saved watchlists. v0.10 BREAKING: replaces ls_watchlist_add / ls_watchlist_remove / ls_watchlist_list / ls_watchlist_group_create / ls_watchlist_group_delete.

NameTypeReqDescription
actionstringyesOperation to perform: 'list', 'add', 'remove', 'group_upsert', or 'group_delete'.
descriptionstring–group_upsert: optional group description.
group_namestring–add / remove: watchlist group name (defaults to 'default'). list: optional group filter (scope='items' only).
namestring–group_upsert / group_delete: the target group name.
notestring–add: optional user note for this watchlist item.
rename_fromstring–group_upsert: optional existing group name to rename to `name`.
scopestring–list: 'items' (default — grouped items + quote enrichment) or 'groups' (group metadata only).
shcodestring–add / remove: 6-character Korean short code (e.g. '005930' or '0117V0').

No output schema declared.

No examples provided.

Common questions

What is the io.github.redoxnet/lsopenapi MCP server?

io.github.redoxnet/lsopenapi is an MCP server listed in the public MCP registry as io.github.redoxnet/lsopenapi. LS Securities OpenAPI MCP server: Korean + overseas stocks, charts, screeners, portfolio, accounts. This page covers its NuGet package (RedoxNet.Mcp.LsOpenApi).

Is the io.github.redoxnet/lsopenapi MCP server safe to use?

io.github.redoxnet/lsopenapi scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.redoxnet/lsopenapi MCP server expose?

io.github.redoxnet/lsopenapi exposes 50 tools: ls_get_market_warnings, ls_account, ls_get_investor_flow, ls_add_indicator, ls_get_etf_holdings, and 45 more. Their descriptions and schemas cost roughly 21,382 tokens of context every time the server is loaded.

Is the io.github.redoxnet/lsopenapi MCP server still maintained?

io.github.redoxnet/lsopenapi is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.redoxnet/lsopenapi MCP server under?

io.github.redoxnet/lsopenapi declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.