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/scalixworld/scalix-cloud-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/scalixworld/scalix-cloud-mcp/scalix)<a href="https://agentmods.dev/mcp/scalixworld/scalix-cloud-mcp/scalix"><img src="https://agentmods.dev/badge/mcp/scalixworld/scalix-cloud-mcp/scalix/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/scalixworld/scalix-cloud-mcp/scalix"><img src="https://agentmods.dev/badge/mcp/scalixworld/scalix-cloud-mcp/scalix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
scalix 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 9d 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
{
"scalix": {
"type": "http",
"url": "https://api.scalix.world/v1/mcp",
"headers": {
"Authorization": "Bearer ${SCALIX_API_KEY}"
}
}
}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.
- 9d ago First seen · 9 lines scan A 52d0ef96b187
scalix is an MCP server published in the GitHub repository scalixworld/scalix-cloud-mcp (2 stars, last pushed 8d 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
postman-mcp-server
A basic MCP server to operate on the Postman API. Runs locally from the @postman/postman-mcp-server npm package. Needs 1 environment variable to run.
mcp-server
Model Context Protocol (MCP) server for AI-assisted development of CAP applications. Runs locally from the @cap-js/mcp-server npm package.
sfcc-dev-mcp
MCP server for Salesforce B2C Commerce Cloud development assistance. Runs locally from the sfcc-dev-mcp npm package.
stitchapi-docs
StitchAPI documentation search, running locally over MCP stdio. Bundled docs, no network calls per query — the offline/air-gapped counterpart to the hosted stitchapi.dev/api/mcp server. Runs locally from the @stitchapi/docs-mcp npm package.
mcp
Apideck Unified API MCP — 330 tools across 200+ SaaS connectors (accounting, CRM, HRIS, ATS). Runs locally from the @apideck/mcp npm package. Needs 3 environment variables to run.
sendgrid-mcp
MCP server for SendGrid's v3 API: email marketing, transactional mail, templates, and analytics. Runs locally from the sendgrid-mcp npm package. Needs 2 environment variables to run.