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/igmizo/auseklisWrote 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/igmizo/auseklis/auseklis)<a href="https://agentmods.dev/mcp/igmizo/auseklis/auseklis"><img src="https://agentmods.dev/badge/mcp/igmizo/auseklis/auseklis/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/igmizo/auseklis/auseklis"><img src="https://agentmods.dev/badge/mcp/igmizo/auseklis/auseklis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
auseklis 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
{
"auseklis": {
"command": "npx",
"args": [
"-y",
"auseklis"
],
"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 c069be3753bb
auseklis is an MCP server published in the GitHub repository igmizo/auseklis (1 stars, last pushed 3mo 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
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.
uis-mcp-server
UNESCO UIS statistics (education, science, culture) with full provenance and fixed releases. Runs locally from the uis-mcp-server npm package.
astral-mcp
Precision-audited astrology MCP: natal charts, transits, synastry, moon phases. No API key. Runs locally from the astral-mcp npm package. Needs 4 environment variables to run.
getbirthchart-mcp
Official MCP server for GetBirthChart astrology calculations. Runs locally from the @getbirthchart/mcp npm package. Needs 1 environment variable to run.
chemical-safety
Chemical hazard lookup: SVHC, GHS, NIOSH, ICSC. 468K classifications. Free. Remote server at chem-mcp-server.rootsbybenda.workers.dev.
cosmetic-regulatory
Cosmetic safety: NOAEL, MoS, SCCS, 12 jurisdictions. 30K ingredients. Free. Remote server at roots-mcp-server.rootsbybenda.workers.dev.