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/ml8s/likiWrote 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/ml8s/liki/liki-engine-mcp)<a href="https://agentmods.dev/mcp/ml8s/liki/liki-engine-mcp"><img src="https://agentmods.dev/badge/mcp/ml8s/liki/liki-engine-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/ml8s/liki/liki-engine-mcp"><img src="https://agentmods.dev/badge/mcp/ml8s/liki/liki-engine-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
engine-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 today.
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
{
"engine-mcp": {
"type": "streamableHttp",
"url": "https://liki.hk/engine/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- today First seen · 6 lines scan A a80a9e86ae95
engine-mcp is an MCP server published in the GitHub repository ml8s/liki (85 stars, last pushed today), 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-10-17.
Other mcp servers, from other repositories
horosa
MCP server "horosa" as configured in tradecatlabs/fatecat.
paipan
MCP server "paipan" as configured in Riki-1124/bazi-ziwei-qimen-paipan-mcp. Runs jueshan_paipan_mcp.server with python.
suanming-mcp
MCP server "suanming-mcp" as configured in Enoch666/suanming-mcp. Runs locally from the suanming-mcp npm package.
asktian
Chinese metaphysics (bazi, qimen, 5-element) as decision-support tools for AI agents. Runs locally from the @asktian/mcp-server npm package. Needs 1 environment variable to run.
tower-mcp-example
MCP server "tower-mcp-example" as configured in joshrotenberg/tower-mcp. Launched with cargo run -p tower-mcp-examples --example getting_started. Needs 1 environment variable to run.
weather
MCP server "weather" as configured in joshrotenberg/tower-mcp. Launched with cargo run -p tower-mcp-examples --example weather_server. Needs 1 environment variable to run.