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/MarcusJellinghaus/mcp-tools-pyInstalling this writes the configuration, not the program: `cmd` 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/marcusjellinghaus/mcp-tools-py/obsidian-wiki)<a href="https://agentmods.dev/mcp/marcusjellinghaus/mcp-tools-py/obsidian-wiki"><img src="https://agentmods.dev/badge/mcp/marcusjellinghaus/mcp-tools-py/obsidian-wiki/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/marcusjellinghaus/mcp-tools-py/obsidian-wiki"><img src="https://agentmods.dev/badge/mcp/marcusjellinghaus/mcp-tools-py/obsidian-wiki.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
obsidian-wiki 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.
This is a copy
100% identical to obsidian-wiki — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"obsidian-wiki": {
"type": "stdio",
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"obsidian-mcp",
"${USERPROFILE}\\Documents\\GitHub\\obsidian-dev-wiki"
],
"env": {},
"alwaysLoad": true
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. 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.
- 1mo ago First seen · 15 lines scan A f9ca560a88ca
obsidian-wiki is an MCP server published in the GitHub repository MarcusJellinghaus/mcp-tools-py (20 stars, last pushed 3d 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. It is 100% identical to obsidian-wiki, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
cite-caddy
Remote MCP server for full read/write access to a Zotero library. Remote server at citecaddy.herbertkokholm.dk.
onenote-mcp
MCP server "onenote-mcp" as configured in sandraschi/onenote-mcp. Runs locally from the onenote-mcp Python package.
excel-mcp-server
MCP server for creating, reading and editing Excel workbooks without Microsoft Excel. Runs locally from the excel-mcp-server Python package.
d365fo-client
Microsoft Dynamics 365 Finance & Operations client and MCP server. Runs locally from the d365fo-client Python package. Needs 4 environment variables to run.
okf-mcp
Validate, search, graph, and safely author local Open Knowledge Format bundles. Runs locally from the @mfdaves/okf-mcp 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.