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/Zojekin/tyme-bazi-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/zojekin/tyme-bazi-mcp/tyme-mcp)<a href="https://agentmods.dev/mcp/zojekin/tyme-bazi-mcp/tyme-mcp"><img src="https://agentmods.dev/badge/mcp/zojekin/tyme-bazi-mcp/tyme-mcp/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/zojekin/tyme-bazi-mcp/tyme-mcp"><img src="https://agentmods.dev/badge/mcp/zojekin/tyme-bazi-mcp/tyme-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tyme-mcp 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.
What it actually says
{ "tyme-mcp": { "command": "uvx", "args": [ "tyme-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.
- 11d ago First seen · 8 lines scan A 88be2f858919
tyme-mcp is an MCP server published in the GitHub repository Zojekin/tyme-bazi-mcp (0 stars, last pushed 1mo 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
zhiji-bazi
BaZi (Chinese Four Pillars) chart calculator. Structured chart data only, no predictions. Runs locally from the zhiji-bazi npm package.
legend-saju
Source-traceable Saju, Zi Wei, Qimen, Daliuren, Tieban, naming, and related calculations. Remote server at legend-saju-mcp-production.up.railway.app.
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.
legend-saju
MCP server "legend-saju", hosted remotely at legend-saju-mcp-production.up.railway.app, as configured in SihyeonJeon/legend-saju.
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.
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.