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/opendata-kr/narajangteo-opening-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/opendata-kr/narajangteo-opening-mcp/narajangteo-opening)<a href="https://agentmods.dev/mcp/opendata-kr/narajangteo-opening-mcp/narajangteo-opening"><img src="https://agentmods.dev/badge/mcp/opendata-kr/narajangteo-opening-mcp/narajangteo-opening/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/opendata-kr/narajangteo-opening-mcp/narajangteo-opening"><img src="https://agentmods.dev/badge/mcp/opendata-kr/narajangteo-opening-mcp/narajangteo-opening.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
narajangteo-opening 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 11d 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.
This is a copy
88% identical to narajangteo-corpinfo — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"narajangteo-opening": {
"command": "npx",
"args": [
"-y",
"@opendata-kr/narajangteo-opening-mcp"
],
"env": {
"DATA_GO_KR_SERVICE_KEY": "",
"DATA_GO_KR_BASE_URL": "https://apis.data.go.kr/1230000/as/ScsbidInfoService"
}
}
}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.
- 11d ago First seen · 13 lines scan A 33f4babb8773
narajangteo-opening is an MCP server published in the GitHub repository opendata-kr/narajangteo-opening-mcp (0 stars, last pushed 5d 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. It is 88% identical to narajangteo-corpinfo, differing in 6 lines, and is treated as a copy.
Other mcp servers, from other repositories
narajangteo-bid-mcp
A local MCP server for South Korea's 나라장터 public procurement service, which publishes government tender notices.
narajangteo-corpinfo
A local connector for South Korea’s Narajangteo public-procurement user information service, provided through the government data.go.kr API.
narajangteo-prespec-mcp
A local MCP server for South Korea's Narajangteo pre-specification information public API. Narajangteo is the Korean government procurement system, and pre-specifications describe planned public purchases before formal bidding.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.0). Needs 6 environment variables to run.
AynOps
A Model Context Protocol server that gives AI Clients real-time cybersecurity reconnaissance capabilities — WHOIS, DNS enumeration, port scanning, SSL inspection, CVE lookup, IP reputation, ASN lookup and more. Runs locally from the AynOps Python package. Needs 2 environment variables to run.
apibase
327 tools, 92 providers. Pay per call via x402 + MPP. One MCP endpoint. Runs locally from the apibase-mcp-client npm package.