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/palisadescan/palisadeWrote 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/palisadescan/palisade/palisade-mcp)<a href="https://agentmods.dev/mcp/palisadescan/palisade/palisade-mcp"><img src="https://agentmods.dev/badge/mcp/palisadescan/palisade/palisade-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/palisadescan/palisade/palisade-mcp"><img src="https://agentmods.dev/badge/mcp/palisadescan/palisade/palisade-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
palisade-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
{ "palisade-mcp": { "command": "uvx", "args": [ "palisade-mcp" ] } }
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 · 8 lines scan A 8849ffdcdeb3
palisade-mcp is an MCP server published in the GitHub repository palisadescan/palisade (1 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
loot-agent-mcp
MCP server "loot-agent-mcp" as configured in D-Kek/loot-agent-mcp. Runs locally from the loot-agent-mcp npm package. Needs 4 environment variables to run.
hyde-mcp
Discover and trade tokenize-anything coins on hyde.trade (Robinhood Chain). Non-custodial. Runs locally from the hyde-mcp npm package. Needs 1 environment variable to run.
nodeflare-mcp
Blockchain JSON-RPC on 23 EVM chains for AI agents - free tier, API key, or x402 pay-per-call. Runs locally from the nodeflare-mcp npm package. Needs 2 environment variables to run.
nodeflare
MCP server for NodeFlare RPC — blockchain data on 23 EVM chains for AI agents. Free public tier, API key, or pay-per-call with x402 (USDC on Base/Polygon/Arbitrum). Runs locally from the nodeflare-mcp npm package.
rugcheck-ai
Solana token safety for AI agents — rug-pull, honeypot & Token-2022 trap detection before you buy. Remote server at web-production-58d585.up.railway.app.
robinx-mcp
Robinhood Chain (4663) caller accuracy + token intel, graded vs real price since genesis. x402-paid. Runs locally from the robinx-mcp npm package. Needs 1 environment variable to run.