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/loganlinn/trsInstalling this writes the configuration, not the program: `mise` has to be on your PATH already, or the server will not start.
Wrote 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/loganlinn/trs/mise)<a href="https://agentmods.dev/mcp/loganlinn/trs/mise"><img src="https://agentmods.dev/badge/mcp/loganlinn/trs/mise/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/loganlinn/trs/mise"><img src="https://agentmods.dev/badge/mcp/loganlinn/trs/mise.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mise 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 1mo 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
{
"mise": {
"type": "stdio",
"command": "mise",
"args": [
"mcp"
],
"env": {
"MISE_EXPERIMENTAL": "1"
}
}
}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.
- 1mo ago First seen · 12 lines scan A 3de4b4134b2d
mise is an MCP server published in the GitHub repository loganlinn/trs (1 stars, last pushed 4mo 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
uk-tenders
MCP server "uk-tenders", hosted remotely at tenders.run.cns.me, as configured in tractorjuice/arckit-codex.
agentbus
A CAN bus-inspired agent communication layer built on Bun. Runs locally from the agentbus npm package.
chist
MCP server "chist" as configured in hiropon164/chist-server. Runs locally from the chist Python package.
codegraph-memory-mcp-lite
MCP server "codegraph-memory-mcp-lite" as configured in StaryMoon/codegraph-memory-mcp-lite. Runs locally from the codegraph-memory-mcp-lite Python package.
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package.
telegram-mcp
MCP server for Telegram - lets AI agents communicate with users via Telegram. Runs locally from the telegram-mcp Python package.