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/xalantis-hub/xalantis-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/xalantis-hub/xalantis-mcp/xalantis-mcp)<a href="https://agentmods.dev/mcp/xalantis-hub/xalantis-mcp/xalantis-mcp"><img src="https://agentmods.dev/badge/mcp/xalantis-hub/xalantis-mcp/xalantis-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/xalantis-hub/xalantis-mcp/xalantis-mcp"><img src="https://agentmods.dev/badge/mcp/xalantis-hub/xalantis-mcp/xalantis-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
xalantis-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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 13 lines scan A a2853828efe8
xalantis-mcp is an MCP server published in the GitHub repository xalantis-hub/xalantis-mcp (0 stars, last pushed 2d ago), with no licence file. 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-10-25.
Other mcp servers, from other repositories
openproject-mcp-server
MCP server for OpenProject: 89 tools for work packages, attachments, git activity, time tracking, meetings and reporting over the API v3. Runs locally from the openproject-mcp-server Python package. Needs 5 environment variables to run.
taiga-mcp-server
MCP server connecting Claude, Cursor, Windsurf, and other AI assistants to Taiga (Cloud and self-hosted) — projects, epics, user stories, tasks, issues, sprints, wiki, and more. Runs locally from the @madebyclowd/taiga-mcp-server npm package.
simple-support-system-mcp
MCP server for the Simple Support System helpdesk API: read, answer and move tickets. Runs locally from the simple-support-system-mcp npm package. Needs 3 environment variables to run.
huly-mcp
Complete MCP server for Huly project management with 209 tools across 23 categories. Supports custom task types, project-scoped status workflows, and read-side Process plugin tools. Runs locally from the @dugynoo/huly-mcp npm package. Needs 5 environment variables to run.
microsoft-planner-mcp
MCP server "microsoft-planner-mcp", hosted remotely at localhost, as configured in aixolotl/microsoft-planner-mcp.
halopsa-mcp
MCP server "halopsa-mcp" as configured in WYRE-AI/halopsa-mcp. Runs in Docker (ghcr.io/wyre-ai/halopsa-mcp:v1.8.2). Needs 7 environment variables to run.