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/hivemindunit/llmintel-mcp/model-lifecyclegit clone --depth 1 https://github.com/hivemindunit/llmintel-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/hivemindunit/llmintel-mcp/model-lifecycle)<a href="https://agentmods.dev/mcp/hivemindunit/llmintel-mcp/model-lifecycle"><img src="https://agentmods.dev/badge/mcp/hivemindunit/llmintel-mcp/model-lifecycle.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
model-lifecycle 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 3d 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
{
"model-lifecycle": {
"command": "npx",
"args": [
"-y",
"@llmintel/mcp"
],
"env": {
"LLMINTEL_API_KEY": "",
"LLMINTEL_BASE_URL": ""
}
}
}What else server.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.
- 3d ago First seen · 13 lines scan A a7bd9acc6089
model-lifecycle is an MCP server published in the GitHub repository hivemindunit/llmintel-mcp (1 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
knowledge_catalog
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package. Needs 1 environment variable to run.
dataproc
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package. Needs 2 environment variables to run.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
hubmesh
Centrality-aware GraphRAG retrieval planner — drop-in layer over any vector DB. Runs locally from the hubmesh Python package.
memoo-mcp
Memoo MCP Gateway — knowledge graph RAG via Model Context Protocol. Runs locally from the memoo-mcp npm package.
generate-data-mcp
MCP server for Generate-Data.com — thin proxy to /api/v2/. Runs locally from the generate-data-mcp Python package. Needs 2 environment variables to run.