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/houtini-ai/houtini-lmWrote 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/houtini-ai/houtini-lm/lm)<a href="https://agentmods.dev/mcp/houtini-ai/houtini-lm/lm"><img src="https://agentmods.dev/badge/mcp/houtini-ai/houtini-lm/lm/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/houtini-ai/houtini-lm/lm"><img src="https://agentmods.dev/badge/mcp/houtini-ai/houtini-lm/lm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lm 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 9d 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
{
"lm": {
"command": "npx",
"args": [
"-y",
"@houtini/lm"
],
"env": {
"HOUTINI_LM_ENDPOINT_URL": "",
"HOUTINI_LM_API_KEY": "",
"HOUTINI_LM_MODEL": "",
"HOUTINI_LM_PROVIDER": ""
}
}
}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.
- 9d ago First seen · 15 lines scan A 0c8d1ed8eae7
lm is an MCP server published in the GitHub repository houtini-ai/houtini-lm (120 stars, last pushed 6d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-07.
Other mcp servers, from other repositories
ask-llm
Unified MCP server for Gemini, Codex, Claude, Grok, Ollama, and Antigravity. Runs locally from the @ask-llm/mcp npm package. Needs 16 environment variables to run.
ask-grok
Consult Grok through xAI's metered API with exact model selection and no fallback. Runs locally from the @ask-llm/grok-mcp npm package. Needs 7 environment variables to run.
short-video-maker
Creates short videos for TikTok, Instagram Reels, and YouTube Shorts using the Model Context Protocol (MCP) and a REST API. Runs locally from the short-video-maker npm package. Needs 1 environment variable to run.
sonarqube-mcp
Model Context Protocol server for SonarQube. Runs locally from the sonarqube-mcp-server npm package.
gluestack-ui-mcp
A Model Context Protocol (MCP) server for Gluestack UI components, providing AI assistants with access to component source code, demos, and metadata. Runs locally from the gluestack-ui-mcp-server npm package.
remotion-mcp
Remotion's Model Context Protocol. Runs locally from the @remotion/mcp npm package.