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/SharpLu/ko-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/sharplu/ko-mcp/ko-sec-data)<a href="https://agentmods.dev/mcp/sharplu/ko-mcp/ko-sec-data"><img src="https://agentmods.dev/badge/mcp/sharplu/ko-mcp/ko-sec-data/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/sharplu/ko-mcp/ko-sec-data"><img src="https://agentmods.dev/badge/mcp/sharplu/ko-mcp/ko-sec-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ko-sec-data 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
{
"ko-sec-data": {
"url": "https://mcp.ko.io/mcp"
}
}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 · 5 lines scan A 827795ae4470
ko-sec-data is an MCP server published in the GitHub repository SharpLu/ko-mcp (0 stars, last pushed 3d 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-09-14.
Other mcp servers, from other repositories
profitelligence
MCP server "profitelligence", hosted remotely at mcp.profitelligence.com, as configured in profitelligence/profitelligence-mcp-server.
mcp-server
Financial intelligence: insider trades, SEC filings, 13F holdings, and market signals. Remote server at mcp.profitelligence.com.
xbbg-mcp
MCP server "xbbg-mcp" as configured in xbbg-org/xbbg. Launched with https://github.com/xbbg-org/xbbg/releases/download/v1.4.6/xbbg-mcp-v1.4.6.mcpb. Needs 6 environment variables to run.
us-congress-trades
US Congress stock trades and financial disclosures by member, ticker, or date, hosted MCP. Remote server at mcp.apify.com.
form4api-mcp
Real-time SEC Form 4 insider trading + Form 144 & 13F-HR data. 27 tools + 6 research prompts. Runs locally from the form4api-mcp npm package. Needs 1 environment variable to run.
agentpay
MCP server "agentpay" as configured in phuocdu/agentpay-vn. Runs agentpay.mcp_server with python. Needs 2 environment variables to run.