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/IcaroBichir/lorcana-mcpWrote 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/icarobichir/lorcana-mcp/lorcana)<a href="https://agentmods.dev/mcp/icarobichir/lorcana-mcp/lorcana"><img src="https://agentmods.dev/badge/mcp/icarobichir/lorcana-mcp/lorcana/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/icarobichir/lorcana-mcp/lorcana"><img src="https://agentmods.dev/badge/mcp/icarobichir/lorcana-mcp/lorcana.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lorcana 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 2mo 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
{
"lorcana": {
"command": "uvx",
"args": [
"lorcana-mcp"
],
"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.
- 2mo ago First seen · 9 lines scan A ffe7f64bbf8d
lorcana is an MCP server published in the GitHub repository IcaroBichir/lorcana-mcp (9 stars, last pushed 15d 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
lorcana-mcp
MCP server for searching, exploring, and aggregating Disney Lorcana TCG cards — card search, deck validation, deck stats, and Dreamborn/Pixelborn deck import/export. Runs locally from the lorcana-cards-mcp Python package.
hotelbooking-ai
RollingGo Hotel Booking MCP Server (Global/AI Edition). Runs locally from the hotelbooking-ai npm package. Needs 1 environment variable to run.
Rollinggo-Hotel
MCP server "Rollinggo-Hotel", hosted remotely at mcp.rollinggo.ai, as configured in RollingGo-AI/RollingGo-Hotel-MCP-Global.
ask-llm
Unified MCP server for Gemini, Codex, Claude, Grok, Ollama, and Antigravity. Runs locally from the @ask-llm/mcp npm package. Needs 16 environment variables to run.
ask-claude
Bridge Codex and other MCP clients with Anthropic Claude Code CLI for read-only second opinions. Runs locally from the @ask-llm/claude-mcp npm package. Needs 4 environment variables to run.
ask-codex
Bridge Claude with OpenAI Codex CLI for AI-to-AI collaboration, code review, and second opinions. Runs locally from the @ask-llm/codex-mcp npm package. Needs 2 environment variables to run.