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/studentepercaso/obsidian-bridgeWrote 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/studentepercaso/obsidian-bridge/obsidian)<a href="https://agentmods.dev/mcp/studentepercaso/obsidian-bridge/obsidian"><img src="https://agentmods.dev/badge/mcp/studentepercaso/obsidian-bridge/obsidian.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
obsidian 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 5d 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": {
"command": "node",
"args": [
"./dist/server.mjs",
"--mode=read"
],
"cwd": ".",
"env_vars": [
"OBSIDIAN_CLI_PATH",
"OBSIDIAN_BRIDGE_SETTINGS_PATH",
"OBSIDIAN_BRIDGE_ALLOWED_FOLDERS",
"OBSIDIAN_BRIDGE_DENIED_FOLDERS",
"OBSIDIAN_BRIDGE_TIMEOUT_MS",
"OBSIDIAN_BRIDGE_MAX_OUTPUT_BYTES",
"OBSIDIAN_BRIDGE_DATA_DIR"
],
"startup_timeout_sec": 20,
"tool_timeout_sec": 30,
"required": false,
"default_tools_approval_mode": "auto"
}
}What else .mcp.json configures
This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 5d ago First seen · 23 lines scan A fdc2f5e90210
obsidian is an MCP server published in the GitHub repository studentepercaso/obsidian-bridge (0 stars, last pushed 5d 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
knowledge-inbox
MCP server "knowledge-inbox" as configured in lyc403223157-source/knowledge-inbox. Runs locally from the knowledge-inbox Python package.
chamber
Cited Q&A over your own notes, plus drift detection when a cited source changes. Local-first CLI. Runs locally from the @bu7umaid/chamber npm package. Needs 2 environment variables to run.
enzyme
MCP server "enzyme" as configured in byenzyme/enzyme. Launched with https://github.com/byenzyme/enzyme/releases/download/v0.9.2/enzyme-mcp-0.9.2-mac. Needs 1 environment variable to run.
omd
One More Dimension — lightweight LLM agent framework with tool-calling, streaming, skills, and file tools. Runs locally from the omd Python package.
big-brain
MCP server "big-brain" as configured in jzhao234/big-brain. Runs locally from the big-brain npm package.
cairn
MCP server exposing Cairn's local-first file-organization tools to Claude Code, Codex, Cursor, and any MCP client. Runs locally from the cairn-mcp-server Python package. Needs 1 environment variable to run.