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/dp-veritas/mcp-obsidian-toolsWrote 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/dp-veritas/mcp-obsidian-tools/mcp-obsidian-tools)<a href="https://agentmods.dev/mcp/dp-veritas/mcp-obsidian-tools/mcp-obsidian-tools"><img src="https://agentmods.dev/badge/mcp/dp-veritas/mcp-obsidian-tools/mcp-obsidian-tools/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/dp-veritas/mcp-obsidian-tools/mcp-obsidian-tools"><img src="https://agentmods.dev/badge/mcp/dp-veritas/mcp-obsidian-tools/mcp-obsidian-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-obsidian-tools 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 9 lines scan A 205fb92713de
mcp-obsidian-tools is an MCP server published in the GitHub repository dp-veritas/mcp-obsidian-tools (4 stars, last pushed 9mo ago), licensed AGPL-3.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-08-31.
Other mcp servers, from other repositories
mcp
Connect AI assistants to your Vaiz workspace: tasks, projects, boards, documents and milestones. Runs locally from the vaiz-mcp npm package. Needs 3 environment variables to run.
ticktick
MCP server "ticktick" as configured in abdulhamid-n/ticktick-mcp. Runs ${HOME}/Documents/Claude/ticktick-mcp/server.py with ${HOME}/Documents/Claude/ticktick-mcp/.venv/bin/python3. Needs 2 environment variables to run.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.
solana-mcp-vybe
MCP server "solana-mcp-vybe", hosted remotely at mcp.vybenetwork.xyz, as configured in vybenetwork/solana-mcp-vybe.
raycast
Raycast workflow automation MCP server with 9 tools. Runs locally from the raycast-mcp-server npm package.
evc-relay
MCP server for reading and writing Obsidian vault documents via EVC Team Relay. Runs locally from the evc-team-relay-mcp Python package. Needs 3 environment variables to run.