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/MotleyAI/slayerWrote 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/motleyai/slayer/motley-slayer)<a href="https://agentmods.dev/mcp/motleyai/slayer/motley-slayer"><img src="https://agentmods.dev/badge/mcp/motleyai/slayer/motley-slayer/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/motleyai/slayer/motley-slayer"><img src="https://agentmods.dev/badge/mcp/motleyai/slayer/motley-slayer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
motley-slayer 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
{ "motley-slayer": { "command": "uvx", "args": [ "motley-slayer" ] } }
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 · 8 lines scan A 3ec2fea5c691
motley-slayer is an MCP server published in the GitHub repository MotleyAI/slayer (314 stars, last pushed today), 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
QueryWeaver
MCP server "QueryWeaver" as configured in FalkorDB/QueryWeaver. Runs in Docker (docker.io/falkordb/queryweaver:0.0.11).
orionbelt-semantic-layer-mcp
Thin MCP server for OrionBelt Semantic Layer — delegates to REST API. Runs locally from the orionbelt-semantic-layer-mcp Python package.
semlayer
Open semantic layer format and inference engine for data warehouses. Runs locally from the semlayer Python package.
steep
MCP server "steep", hosted remotely at mcp.steep.app, as configured in SteepHq/steep-mcp.
atlas
Atlas is a YAML-defined semantic layer for analytics — authored by humans, consumed by AI agents. Runs locally from the @useatlas/mcp npm package. Needs 3 environment variables to run.
boyce
Privacy-first SQL compiler and MCP server — deterministic semantic layer for agentic database workflows. Runs locally from the boyce Python package. Needs 3 environment variables to run.