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/EllisMorrow/CaeluneWrote 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/ellismorrow/caelune/caelune-mcp)<a href="https://agentmods.dev/mcp/ellismorrow/caelune/caelune-mcp"><img src="https://agentmods.dev/badge/mcp/ellismorrow/caelune/caelune-mcp/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/ellismorrow/caelune/caelune-mcp"><img src="https://agentmods.dev/badge/mcp/ellismorrow/caelune/caelune-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
caelune-mcp 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 10d 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
{
"caelune-mcp": {
"command": "https://github.com/EllisMorrow/Caelune/releases/download/v0.5.6/caelune-mcp-win-x64-v0.5.6.mcpb",
"args": [],
"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.
- 10d ago First seen · 7 lines scan A 7ae783432ce3
caelune-mcp is an MCP server published in the GitHub repository EllisMorrow/Caelune (45 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-30.
Other mcp servers, from other repositories
obsidian-mcp-server
Read, write, search, and surgically edit Obsidian notes, tags, and frontmatter via MCP. Runs locally from the obsidian-mcp-server npm package. Needs 10 environment variables to run.
mcp-documentation-server
Local-first document management and semantic search for AI coding agents. Runs locally from the @andrea9293/mcp-documentation-server npm package.
link
MCP server for Link local agent memory — remember, recall, search, context, and graph traversal. Runs locally from the link-mcp Python package.
fetchv2-mcp-server
A robust MCP server for fetching and extracting web content using Trafilatura. Runs locally from the fetchv2-mcp-server Python package.
evc-relay
MCP server for reading and writing Obsidian vault documents via EVC Team Relay. Runs locally from the evc-team-relay-mcp Python package. Needs 3 environment variables to run.
evc-team-relay-mcp
MCP server for reading and writing Obsidian vault documents via EVC Team Relay. Runs locally from the evc-team-relay-mcp Python package. Needs 3 environment variables to run.