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/psenger/obsidian-markdown-lint-mcp-serverWrote 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/psenger/obsidian-markdown-lint-mcp-server/obsidian-markdown-lint)<a href="https://agentmods.dev/mcp/psenger/obsidian-markdown-lint-mcp-server/obsidian-markdown-lint"><img src="https://agentmods.dev/badge/mcp/psenger/obsidian-markdown-lint-mcp-server/obsidian-markdown-lint/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/psenger/obsidian-markdown-lint-mcp-server/obsidian-markdown-lint"><img src="https://agentmods.dev/badge/mcp/psenger/obsidian-markdown-lint-mcp-server/obsidian-markdown-lint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
obsidian-markdown-lint 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 10d 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
{
"obsidian-markdown-lint": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"obsidian-markdown-lint-mcp"
],
"env": {}
}
}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.
- 10d ago First seen · 13 lines scan A f0456547620d
obsidian-markdown-lint is an MCP server published in the GitHub repository psenger/obsidian-markdown-lint-mcp-server (2 stars, last pushed today), 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
vellum
MCP server "vellum", hosted remotely, as configured in freema/vellum.
kiwiki
MCP server "kiwiki" as configured in natorus87/kiwiki. Runs locally from the kiwiki Python package.
iwe
Markdown knowledge base as agent memory. Runs against the notes directory it is started in. Runs locally from the @iwe-org/mcp npm package.
transcriptor-mcp
MCP server "transcriptor-mcp" as configured in samson-art/transcriptor-mcp. Runs in Docker (docker.io/artsamsonov/transcriptor-mcp:1.2.4).
oriel
MCP server "oriel" as configured in ParadoxInfinite/oriel. Runs in Docker (ghcr.io/paradoxinfinite/oriel:0.7.0).
tela
Self-hostable team wiki; agents read & write it via MCP; Atlas turns your repo into a cited wiki. Runs locally from the tela-mcp npm package. Needs 2 environment variables to run.