Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/PLUG-OpenAPI/nhplug-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/plug-openapi/nhplug-mcp/mcp-server)<a href="https://agentmods.dev/mcp/plug-openapi/nhplug-mcp/mcp-server"><img src="https://agentmods.dev/badge/mcp/plug-openapi/nhplug-mcp/mcp-server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/plug-openapi/nhplug-mcp/mcp-server"><img src="https://agentmods.dev/badge/mcp/plug-openapi/nhplug-mcp/mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "mcp-server": { "command": "npx", "args": [ "-y", "@nhplug/mcp-server" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A 161c4c44f533
mcp-server is an MCP server published in the GitHub repository PLUG-OpenAPI/nhplug-mcp (13 stars, last pushed 20d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp
Background checks for Korean stocks - 10 years of DART filings for all KRX companies, in English. Remote server at mcp.koreastockcheck.com.
trading212
MCP server "trading212" as configured in guilyx/t212-mcp. Runs locally from the t212-mcp npm package. Needs 3 environment variables to run.
financialdatasets
MCP server "financialdatasets", hosted remotely at mcp.financialdatasets.ai, as configured in lowtidebuild/public-equity-research.
market-intelligence-mcp
Recession probability, capital rotation scoring, and economic data API. Runs locally from the @bullrundata/market-intelligence npm package. Needs 1 environment variable to run.
krx-cli
CLI & MCP server for KRX (Korea Exchange) Open API — query Korean stock market data (KOSPI, KOSDAQ, ETF, bonds, derivatives) from terminal or AI agents. Runs locally from the krx-cli npm package.
questrade-mcp-server
MCP server for Questrade API integration. Runs locally from the questrade-mcp-server npm package.