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/ScriptXeno/ScriptXeno.github.ioInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
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/scriptxeno/scriptxeno.github.io/scriptxeno-blog)<a href="https://agentmods.dev/mcp/scriptxeno/scriptxeno.github.io/scriptxeno-blog"><img src="https://agentmods.dev/badge/mcp/scriptxeno/scriptxeno.github.io/scriptxeno-blog/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/scriptxeno/scriptxeno.github.io/scriptxeno-blog"><img src="https://agentmods.dev/badge/mcp/scriptxeno/scriptxeno.github.io/scriptxeno-blog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
scriptxeno-blog 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
{
"scriptxeno-blog": {
"command": "node",
"args": [
"G:/ScriptXeno/ScriptXeno.github.io/tools/blog-mcp/build/index.js"
]
}
}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 · 8 lines scan A dd2450decb61
scriptxeno-blog is an MCP server published in the GitHub repository ScriptXeno/ScriptXeno.github.io (5 stars, last pushed 26d 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
markdown
Markdown MCP — search, extract sections, list headings, find code blocks. Runs locally from the mcp-server-markdown npm package.
jdocmunch-mcp
Token-efficient MCP server for structured documentation retrieval via section-level indexing. Runs locally from the jdocmunch-mcp Python package.
biel-ai
Query your product docs from AI tools. Source-cited answers from your indexed documentation. Remote server at mcp.biel.ai.
helx
MCP server "helx" as configured in Asno-dev/Helx. Runs locally from the helx npm package.
docs-mcp
A local MCP service that provides searchable, verifiable documentation for open-source projects used with AI coding tools such as Claude Code or Cursor.
localdocs-mcp
MCP server "localdocs-mcp" as configured in dylan-gluck/localdocs-mcp. Runs locally from the localdocs-mcp Python package.