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/pwelty/mcp_triliumWrote 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/pwelty/mcp_trilium/mcp-trilium)<a href="https://agentmods.dev/mcp/pwelty/mcp_trilium/mcp-trilium"><img src="https://agentmods.dev/badge/mcp/pwelty/mcp_trilium/mcp-trilium/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/pwelty/mcp_trilium/mcp-trilium"><img src="https://agentmods.dev/badge/mcp/pwelty/mcp_trilium/mcp-trilium.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-trilium 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 11d 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
{ "mcp-trilium": { "command": "uvx", "args": [ "mcp-trilium" ] } }
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.
- 11d ago First seen · 8 lines scan A 419d2b1a1c6f
mcp-trilium is an MCP server published in the GitHub repository pwelty/mcp_trilium (7 stars, last pushed 2mo 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
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.
knowledge-inbox
MCP server "knowledge-inbox" as configured in lyc403223157-source/knowledge-inbox. Runs locally from the knowledge-inbox Python package.
calendar
MCP server "calendar", hosted remotely at localhost, as configured in philipyaz/cos.
obsidian
MCP server "obsidian" as configured in studentepercaso/obsidian-bridge. Runs ./dist/server.mjs with node.
big-brain
MCP server "big-brain" as configured in jzhao234/big-brain. Runs locally from the big-brain npm package.
mcp-mem
An MCP server implementing memory solution for data-rich applications. Runs locally from the mcp-mem Python package.