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/yotsuda/MarkdownPointerInstalling this writes the configuration, not the program: `https://github.com/yotsuda/MarkdownPointer/releases/download/v0.1.1/MarkdownPointer-0.1.1-win-x64.mcpb` 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/yotsuda/markdownpointer/markdown-pointer)<a href="https://agentmods.dev/mcp/yotsuda/markdownpointer/markdown-pointer"><img src="https://agentmods.dev/badge/mcp/yotsuda/markdownpointer/markdown-pointer/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/yotsuda/markdownpointer/markdown-pointer"><img src="https://agentmods.dev/badge/mcp/yotsuda/markdownpointer/markdown-pointer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
markdown-pointer 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.
What it actually says
{ "markdown-pointer": { "command": "https://github.com/yotsuda/MarkdownPointer/releases/download/v0.1.1/MarkdownPointer-0.1.1-win-x64.mcpb", "args": [], "env": {} } }
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 · 7 lines scan A e64deb594c49
markdown-pointer is an MCP server published in the GitHub repository yotsuda/MarkdownPointer (1 stars, last pushed 4mo 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
iwe
Markdown knowledge base as agent memory. Runs against the notes directory it is started in. Runs locally from the @iwe-org/mcp npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
tela
Self-hostable team wiki; agents read & write it via MCP; Atlas turns your repo into a cited wiki. Runs locally from the tela-mcp npm package. Needs 2 environment variables to run.
analyzer
MCP server "analyzer" as configured in Anselmoo/mcp-server-analyzer. Launched with sh -c PATH="$PWD/node_modules/.bin:$PATH" uv run mcp-server-analyzer. Needs 1 environment variable to run.
context-server
Lightweight MCP server for semantic search over organizational markdown. Runs locally from the context-server Python package.
exomem
MCP server "exomem", hosted remotely at exomem.substratesystems.io, as configured in Artexis10/exomem.