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/seongwon030/velog_mcpWrote 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/seongwon030/velog_mcp/velog)<a href="https://agentmods.dev/mcp/seongwon030/velog_mcp/velog"><img src="https://agentmods.dev/badge/mcp/seongwon030/velog_mcp/velog/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/seongwon030/velog_mcp/velog"><img src="https://agentmods.dev/badge/mcp/seongwon030/velog_mcp/velog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
velog 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
{
"velog": {
"command": "npx",
"args": [
"-y",
"velog-mcp-claude"
],
"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 bc96b545160c
velog is an MCP server published in the GitHub repository seongwon030/velog_mcp (6 stars, last pushed 12d 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
velog
A local MCP server for Velog, a Korean blogging platform, that lets coding agents read, search, and view statistics, and can create drafts or private posts by default. It runs from an npm package and needs five environment settings.
velog
An MCP server for Velog, a Korean developer blogging platform, with support for reading and writing blog content and creating diagrams or sequences. Public publishing is optional and requires configuration and access credentials.
charlotte
Renders web pages into structured, agent-readable representations using headless Chromium. Runs locally from the @ticktockbent/charlotte npm package.
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
filesystem-mcp
Secure filesystem MCP server for reading, writing, searching, diffing, and patching files. Runs locally from the @j0hanz/filesystem-mcp npm package. Needs 1 environment variable to run.
advisory
MCP server "advisory" as configured in microsoft/github-advisory-mcp. Runs ${workspaceFolder}/dist/index.js with node. Needs 2 environment variables to run.