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/n-3-0-l-d-3-v/aether-platformWrote 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/n-3-0-l-d-3-v/aether-platform/aether)<a href="https://agentmods.dev/mcp/n-3-0-l-d-3-v/aether-platform/aether"><img src="https://agentmods.dev/badge/mcp/n-3-0-l-d-3-v/aether-platform/aether.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
aether 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 7d 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
{ "aether": { "command": "uvx", "args": [ "aether" ] } }
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.
- 7d ago First seen · 8 lines scan A aa24f6c63e3b
aether is an MCP server published in the GitHub repository n-3-0-l-d-3-v/aether-platform (0 stars, last pushed 9d ago), licensed Apache-2.0. 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
hexwitness
Durable, build-scoped reverse-engineering evidence memory and query tools for AI agents. Runs locally from the hexwitness npm package.
ghidra-mcp
MCP server "ghidra-mcp" as configured in bethington/ghidra-mcp. Runs locally from the c:/Users/benam/source/mcp/ghidra-mcp Python package. Needs 3 environment variables to run.
ghidralens
Interactive Ghidra views in your AI client: decompile, rename, and navigate a binary. Runs locally from the ghidralens npm package. Needs 2 environment variables to run.
kawaiidra
MCP server "kawaiidra" as configured in wagonbomb/kawaiidra-mcp. Runs run_server.py with python. Needs 1 environment variable to run.
rbinmcp
MCP server "rbinmcp" as configured in kirkderp/rbinmcp. Runs in Docker (ghcr.io/kirkderp/rbinmcp:1.3.0).
rea
Reverse engineer anything from your terminal or agent with one CLI and MCP server. Runs locally from the rea-agents npm package.