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/LivelyKernel/lively4-coreWrote 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/livelykernel/lively4-core/lively4)<a href="https://agentmods.dev/mcp/livelykernel/lively4-core/lively4"><img src="https://agentmods.dev/badge/mcp/livelykernel/lively4-core/lively4/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/livelykernel/lively4-core/lively4"><img src="https://agentmods.dev/badge/mcp/livelykernel/lively4-core/lively4.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lively4 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 28d 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
{
"lively4": {
"url": "http://localhost:9005/_mcp/message"
}
}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.
- 28d ago First seen · 5 lines scan A aa91ff697547
lively4 is an MCP server published in the GitHub repository LivelyKernel/lively4-core (91 stars, last pushed 18d 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-30.
Other mcp servers, from other repositories
go-language-server
MCP server "go-language-server" as configured in coder/coder. Launched with go run github.com/isaacphi/mcp-language-server@latest -workspace ./ -lsp go -- r.
typescript-language-server
MCP server "typescript-language-server" as configured in coder/coder. Launched with go run github.com/isaacphi/mcp-language-server@latest -workspace ./site/ -lsp pn.
coder
Manage Coder workspaces, templates, and cloud development environments. Remote server at {coder_hostname}.
storybook
MCP server "storybook", hosted remotely at localhost, as configured in coder/coder.
envkit
MCP server "envkit" as configured in Env-Kit/envkit-releases. Launched with https://github.com/Env-Kit/envkit-releases/releases/download/v0.33.0-beta.44/env.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.