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.
npx agentmods add mcp/sjk4425/ncloud-mcp-server/ncloudgit clone --depth 1 https://github.com/sjk4425/ncloud-mcp-serverWrote 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/sjk4425/ncloud-mcp-server/ncloud)<a href="https://agentmods.dev/mcp/sjk4425/ncloud-mcp-server/ncloud"><img src="https://agentmods.dev/badge/mcp/sjk4425/ncloud-mcp-server/ncloud.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ncloud 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 4d 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
{
"ncloud": {
"command": "npx",
"args": [
"-y",
"ncloud-mcp-server"
],
"env": {
"NCLOUD_ACCESS_KEY": "",
"NCLOUD_SECRET_KEY": "",
"NCLOUD_REGION": "",
"NCLOUD_TOOL_GROUPS": "",
"NCLOUD_RESPONSE_PRUNE": "",
"NCLOUD_TIMEOUT_MS": "",
"NCLOUD_LANG": "",
"NCLOUD_RESPONSE_MAXBYTES": ""
}
}
}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.
- 4d ago First seen · 19 lines scan A 1c56741471fe
ncloud is an MCP server published in the GitHub repository sjk4425/ncloud-mcp-server (2 stars, last pushed 8d 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
railway
MCP server "railway", hosted remotely at mcp.railway.com, as configured in railwayapp/railway-skills.
dokploy-mcp
Dokploy MCP server for Codex, Cursor, and Claude with compact stdio and hosted HTTP modes. Runs locally from the @vibetools/dokploy-mcp npm package. Needs 3 environment variables to run.
vmware
MCP server "vmware" as configured in Hokonoken/mcp-vmware. Launched with ssh jumphost VMware/mcp-vmware/run.sh.
blc-ssh-mcp
MCP server giving AI assistants SSH access to run commands, transfer files, and manage server fleets. Runs locally from the blc-ssh-mcp Python package.
infra-lens-mcp
MCP server that connects to Linux servers over SSH, collects live metrics, builds statistical baselines, detects anomalies with z-score analysis, and explains infrastructure health in plain English. Runs locally from the infra-lens-mcp npm package.
openstack-mcp
MCP server "openstack-mcp" as configured in abhishekambad-leapswitch/openstack-mcp. Runs locally from the openstack-mcp Python package.