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.
npx agentmods add mcp/yotsuda/markdownpointer/markdown-pointergit clone --depth 1 https://github.com/yotsuda/MarkdownPointerGrade 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 yesterday.
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.
- yesterday First seen · 7 lines scan A e64deb594c49
markdown-pointer is an MCP server published in the GitHub repository yotsuda/MarkdownPointer (1 stars, last pushed 2mo 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.
apify
Apify MCP Server. Runs locally from the @apify/actors-mcp-server npm package. Needs 2 environment variables to run.
better-code-review-graph
Knowledge graph for token-efficient code reviews -- semantic search and call-graph resolution across your codebase. Runs locally from the better-code-review-graph Python package. Needs 4 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.
vera-ue
MCP server "vera-ue" as configured in ezesubu/VERA. Launched with C:/Users/ezesu/AppData/Local/Programs/Python/Python314/python.exe -m vera.tools.. Needs 1 environment variable to run.
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.