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/ebeirne/lians2/liansgit clone --depth 1 https://github.com/ebeirne/Lians2Wrote 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/ebeirne/lians2/lians)<a href="https://agentmods.dev/mcp/ebeirne/lians2/lians"><img src="https://agentmods.dev/badge/mcp/ebeirne/lians2/lians.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
lians 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 5d 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.
This is a copy
86% identical to lians — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"lians": {
"command": "uvx",
"args": [
"lians-sdk",
"lians-sdk[mcp]",
"lians-mcp"
],
"env": {
"LIANS_URL": "",
"LIANS_API_KEY": "",
"LIANS_AGENT_ID": "mcp-agent"
}
}
}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.
- 5d ago First seen · 15 lines scan A 024902cdf075
lians is an MCP server published in the GitHub repository ebeirne/Lians2 (0 stars, last pushed 1mo 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. It is 86% identical to lians, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
saihm-mcp-server-pro
Enterprise-ready portable memory for AI agents: encrypted, shareable, provably erased. Join SAIHM. Runs locally from the @saihm/mcp-server-pro npm package. Needs 4 environment variables to run.
inite-brain-service
Open-source bitemporal memory layer for LLM agents — knowledge graph with conflict resolution. Remote server at brain.inite.ai.
loreweave
Durable agent memory over a markdown vault: bitemporal facts, timelines, hybrid graph search. Runs locally from the loreweave npm package.
gctrl
Governed graph-native agent memory: knowledge extraction, fusion, hybrid RAG, scoped access tokens. Runs locally from the gctrl-mcp npm package. Needs 3 environment variables to run.
procheiron
Review gate for shared agent memory: an unreviewed or hand-edited memory never reaches your agents. MCP-native, zero dependencies. Runs locally from the procheiron Python package. Needs 1 environment variable to run.
eu-audit-mcp
Tamper-evident audit trail MCP server for EU AI Act and GDPR compliance. Runs locally from the eu-audit-mcp Python package. Needs 1 environment variable to run.