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/ahmedtawfeeq1/loredex-obsidianWrote 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/ahmedtawfeeq1/loredex-obsidian/loredex)<a href="https://agentmods.dev/mcp/ahmedtawfeeq1/loredex-obsidian/loredex"><img src="https://agentmods.dev/badge/mcp/ahmedtawfeeq1/loredex-obsidian/loredex/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/ahmedtawfeeq1/loredex-obsidian/loredex"><img src="https://agentmods.dev/badge/mcp/ahmedtawfeeq1/loredex-obsidian/loredex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
loredex 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.
This is a copy
100% identical to loredex — 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
{
"loredex": {
"command": "npx",
"args": [
"-y",
"loredex@latest",
"mcp"
]
}
}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 · 10 lines scan A b57feca28e45
loredex is an MCP server published in the GitHub repository ahmedtawfeeq1/loredex-obsidian (0 stars, last pushed 1mo 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 loredex, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
mcp-obsidian-via-rest
Access Obsidian vaults via Local REST API - read, search, and interact with notes. Runs locally from the @oleksandrkucherenko/mcp-obsidian npm package. Needs 4 environment variables to run.
obsidian-sync-mcp
Give AI agents access to your Obsidian vault via local files or Self-hosted LiveSync. Runs locally from the obsidian-sync-mcp npm package. Needs 11 environment variables to run.
memento-vault
MCP server "memento-vault" as configured in sandsower/memento-vault. Runs locally from the memento-vault Python package.
obsidian-mcp
Access your Obsidian vault from Claude Desktop and other AI tools — MCP server wrapping the official Obsidian CLI with tools, resources, and prompts. Runs locally from the @zethictech/obsidian-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.
evc-team-relay-mcp
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.