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/robinmordasiewicz/f5xc-cloudstatus-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/robinmordasiewicz/f5xc-cloudstatus-mcp/f5cloudstatus)<a href="https://agentmods.dev/mcp/robinmordasiewicz/f5xc-cloudstatus-mcp/f5cloudstatus"><img src="https://agentmods.dev/badge/mcp/robinmordasiewicz/f5xc-cloudstatus-mcp/f5cloudstatus.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
f5cloudstatus 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 7d 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
{
"f5cloudstatus": {
"command": "node",
"args": [
"dist/index.js"
],
"env": {
"API_BASE_URL": "https://www.f5cloudstatus.com/api/v2",
"API_TIMEOUT": "10000",
"API_RETRY_ATTEMPTS": "3",
"API_RETRY_DELAY": "1000",
"SCRAPER_BASE_URL": "https://www.f5cloudstatus.com",
"SCRAPER_TIMEOUT": "30000",
"SCRAPER_HEADLESS": "true",
"CACHE_TTL_STATUS": "30000",
"CACHE_TTL_COMPONENTS": "60000",
"CACHE_TTL_INCIDENTS": "120000",
"CACHE_TTL_MAINTENANCE": "300000",
"LOG_LEVEL": "info"
}
}
}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.
- 7d ago First seen · 22 lines scan A 13a5d08ab358
f5cloudstatus is an MCP server published in the GitHub repository robinmordasiewicz/f5xc-cloudstatus-mcp (1 stars, last pushed 3mo 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
f5xc-api-mcp
F5 Distributed Cloud API MCP Server - Exposes F5XC APIs to AI assistants via Model Context Protocol. Runs locally from the @robinmordasiewicz/f5xc-api-mcp npm package.
dataproc
MCP server "dataproc", hosted remotely at dataproc-$gcpregion.googleapis.com, as configured in gemini-cli-extensions/data-agent-kit-starter-pack. Needs 1 environment variable to run.
mcp-pve
Manage Proxmox VE through AI assistants. Runs locally from the @samik081/mcp-pve npm package. Needs 3 environment variables to run.
ssh-licco
SSH Model Context Protocol Server - Enable SSH functionality for AI models. Runs locally from the ssh-licco Python package. Needs 4 environment variables to run.
AWSPrice
MCP server "AWSPrice" as configured in spacehendrix/clauder. Runs locally from the awslabs.aws-pricing-mcp-server@latest Python package. Needs 3 environment variables to run.
CloudflareLogpush
MCP server "CloudflareLogpush", hosted remotely at logs.mcp.cloudflare.com, as configured in spacehendrix/clauder.