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/pawcoding/astro-loader-pocketbaseWrote 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/pawcoding/astro-loader-pocketbase/astro-docs)<a href="https://agentmods.dev/mcp/pawcoding/astro-loader-pocketbase/astro-docs"><img src="https://agentmods.dev/badge/mcp/pawcoding/astro-loader-pocketbase/astro-docs/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/pawcoding/astro-loader-pocketbase/astro-docs"><img src="https://agentmods.dev/badge/mcp/pawcoding/astro-loader-pocketbase/astro-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
astro-docs 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
{
"astro-docs": {
"url": "https://mcp.docs.astro.build/mcp",
"type": "http"
}
}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 · 6 lines scan A 8699efe7ec2c
astro-docs is an MCP server published in the GitHub repository pawcoding/astro-loader-pocketbase (63 stars, last pushed 2d 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-09-20.
Other mcp servers, from other repositories
mcp
Framework-aware Starwind UI v3 tools for Astro and React setup, components, docs, and migration. Runs locally from the @starwind-ui/mcp npm package.
open-ephemeris
Sub-arcsecond astrology on NASA JPL DE440: natal, transits, Human Design, Vedic, BaZi. Remote server at mcp.openephemeris.com.
one
MCP server "one" as configured in one-ie/one. Launched with sh -c set -a; [ -f site/.dev.vars ] && . ./site/.dev.vars; [ -f .env.local ] && .
astro-mcp
MCP server to support Astro project development. Runs locally from the astro-mcp npm package.
astro
MCP server "astro", hosted remotely at localhost, as configured in morinokami/astro-mcp.
pocketbase-mcp
Complete Model Context Protocol (MCP) server for PocketBase — collections, records, auth, files, logs, settings, backups, crons and more. Runs locally from the pocketbase-mcp-bridge npm package. Needs 3 environment variables to run.