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/puru991/kundlit-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/puru991/kundlit-mcp/astro)<a href="https://agentmods.dev/mcp/puru991/kundlit-mcp/astro"><img src="https://agentmods.dev/badge/mcp/puru991/kundlit-mcp/astro/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/puru991/kundlit-mcp/astro"><img src="https://agentmods.dev/badge/mcp/puru991/kundlit-mcp/astro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
astro 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 9d 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
{
"astro": {
"command": "npx",
"args": [
"-y",
"@kundlit/mcp"
],
"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.
- 9d ago First seen · 10 lines scan A 82e06cfb5369
astro is an MCP server published in the GitHub repository puru991/kundlit-mcp (0 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-31.
Other mcp servers, from other repositories
mcp-starmeet
Free Vedic astrology MCP: birth-chart, panchang & nakshatra tools. Public API, no key required. Runs locally from the @edestory/mcp-starmeet npm package.
vedaksha
MCP server "vedaksha" as configured in arthiqlabs/vedaksha. Runs in Docker (ghcr.io/arthiqlabs/vedaksha-mcp:v8.0.0).
auseklis
Astrology from a real ephemeris: natal charts, transits, synastry, eclipses, returns. No API keys. Runs locally from the auseklis npm package.
nanami-products
Pre-computed astrology YAML via Swiss Ephemeris. Calculation is code, interpretation is AI. Remote server at chart.nanami-astro.com.
rishi-ai-mcp
Bring the profound wisdom of Vedic Astrology to your AI agents via the Model Context Protocol. Runs locally from the rishi-ai-mcp Python package.
ephemeris-mcp
Precision astronomical ephemeris calculations via Model Context Protocol (MCP). Provides planetary positions using Swiss Ephemeris. Runs locally from the ephemeris-mcp Python package.