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/SihyeonJeon/legend-sajuWrote 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/sihyeonjeon/legend-saju/legend-saju-legend-saju)<a href="https://agentmods.dev/mcp/sihyeonjeon/legend-saju/legend-saju-legend-saju"><img src="https://agentmods.dev/badge/mcp/sihyeonjeon/legend-saju/legend-saju-legend-saju/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/sihyeonjeon/legend-saju/legend-saju-legend-saju"><img src="https://agentmods.dev/badge/mcp/sihyeonjeon/legend-saju/legend-saju-legend-saju.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
legend-saju 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 12d 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
{
"legend-saju": {
"type": "http",
"url": "https://legend-saju-mcp-production.up.railway.app/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.
- 12d ago First seen · 6 lines scan A e9325ad2df98
legend-saju is an MCP server published in the GitHub repository SihyeonJeon/legend-saju (0 stars, last pushed 19d ago), licensed Apache-2.0. 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
true-solar-time
True solar time correction for BaZi charts: historical DST, longitude, equation of time. Runs locally from the true-solar-time-mcp npm package.
zhiji-bazi
BaZi (Chinese Four Pillars) chart calculator. Structured chart data only, no predictions. Runs locally from the zhiji-bazi npm package.
saju-mcp
MCP server wrapping the Saju API (Korean Four Pillars / Bazi) — calculate, interpret, compatibility, daily fortune in 10 languages. Runs locally from the saju-mcp npm package.
divination-chart-mcp
MCP server "divination-chart-mcp" as configured in wangsquirrel/divination-chart-mcp. Runs locally from the divination-chart-mcp Python package.
saju-mcp
Korean Four Pillars of Destiny (Saju/Bazi): calculate, interpret, compatibility & daily fortune. Runs locally from the saju-mcp npm package. Needs 1 environment variable to run.
tyme-mcp
MCP server "tyme-mcp" as configured in Zojekin/tyme-bazi-mcp. Runs locally from the tyme-mcp Python package.