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/paulhkang94/markviewWrote 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/paulhkang94/markview/markview)<a href="https://agentmods.dev/mcp/paulhkang94/markview/markview"><img src="https://agentmods.dev/badge/mcp/paulhkang94/markview/markview/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/paulhkang94/markview/markview"><img src="https://agentmods.dev/badge/mcp/paulhkang94/markview/markview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
markview 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
{
"markview": {
"command": "npx",
"args": [
"-y",
"mcp-server-markview"
],
"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 · 10 lines scan A 3125a37b2e95
markview is an MCP server published in the GitHub repository paulhkang94/markview (38 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. 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
assemblyai-docs
MCP server "assemblyai-docs", hosted remotely at mcp.assemblyai.com, as configured in AssemblyAI/blurt.
seekstone
Filesystem-direct Obsidian MCP server — search and edit your vault with low context-tax. Runs locally from the seekstone npm package. Needs 1 environment variable to run.
easy-notion
Markdown-first Notion MCP server. 6-7x fewer response tokens vs official Notion MCP. 43 tools. Runs locally from the easy-notion-mcp npm package. Needs 2 environment variables to run.
carbone-mcp
Generate PDF/DOCX/XLSX/PPTX from templates+JSON. Convert Office/HTML/MD to PDF. Universal templating. Runs locally from the carbone-mcp npm package. Needs 2 environment variables to run.
spoken
Podcast transcripts as clean Markdown with real speaker names — via the Spoken API. Runs locally from the spoken-mcp npm package. Needs 1 environment variable to run.
jdocmunch-mcp
Token-efficient MCP server for structured documentation retrieval via section-level indexing. Runs locally from the jdocmunch-mcp Python package.