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/2233admin/obsidian-llm-wikiWrote 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/2233admin/obsidian-llm-wiki/repowise)<a href="https://agentmods.dev/mcp/2233admin/obsidian-llm-wiki/repowise"><img src="https://agentmods.dev/badge/mcp/2233admin/obsidian-llm-wiki/repowise/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/2233admin/obsidian-llm-wiki/repowise"><img src="https://agentmods.dev/badge/mcp/2233admin/obsidian-llm-wiki/repowise.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
repowise 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What else .mcp.json configures
This page is one entry in a file that holds 2. 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 · 12 lines scan A 6a4d7e986b99
repowise is an MCP server published in the GitHub repository 2233admin/obsidian-llm-wiki (36 stars, last pushed 16d ago), licensed GPL-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-30.
Other mcp servers, from other repositories
mb
MCP server for MindBase — query and write to your wiki from Claude Desktop, Cursor, Windsurf, Cline, or any MCP-compatible AI client. Runs locally from the mindbase-mcp npm package.
knowit
Shared team memory for AI coding agents — MCP server and CLI for persistent, queryable knowledge across sessions and teammates. Runs locally from the knowit npm package.
kb-graph
MCP server "kb-graph" as configured in uttambharadwaj/kb-graph. Runs locally from the kb-graph npm package.
wyrd-scribe
Creates new pages with provenance and records lineage in a ledger under .wyrd/. Runs locally from the wyrd-scribe npm package. Needs 2 environment variables to run.
wyrd
Exposes one granted folder to any AI client, read-only, behind a path-containment fence. Runs locally from the wyrd-mcp npm package. Needs 1 environment variable to run.
repo-memory
Shared, git-tracked memory for AI agents (Claude Code, Cursor, Cline) working on the same codebase. CLI + MCP server. Runs locally from the repo-memory-mcp Python package. Needs 1 environment variable to run.