npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@robinmordasiewicz/f5xc-cloudstatus-mcp

v1.4.0

Published

MCP server for F5 Cloud Status monitoring with fully automated CI/CD

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

robinmordasiewiczrobinmordasiewicz

Keywords

mcpf5statusmonitoringcloudmodel-context-protocolstatuspageservice-statusautomated-versioningcicd

Readme

F5 Cloud Status MCP Server

MCP server for monitoring F5 Distributed Cloud service status, components, incidents, and maintenance.

Installation

{
  "mcpServers": {
    "f5xc-cloudstatus": {
      "command": "npx",
      "args": ["-y", "@robinmordasiewicz/f5xc-cloudstatus-mcp@latest"]
    }
  }
}

Config file locations:

  • Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) | %APPDATA%\Claude\claude_desktop_config.json (Windows)
  • Claude Code: claude mcp add f5xc-cloudstatus npx @robinmordasiewicz/f5xc-cloudstatus-mcp@latest
  • VS Code: code --add-mcp '{"name":"f5xc-cloudstatus","command":"npx","args":["@robinmordasiewicz/f5xc-cloudstatus-mcp@latest"]}'
  • Cursor: .cursor/mcp.json
  • Windsurf: Plugins → Search "F5 Cloud Status" → Install

Tools

| Tool | Description | |------|-------------| | f5-status-get-overall | Current overall status | | f5-status-get-components | All service components with status | | f5-status-get-component | Specific component details | | f5-status-get-incidents | Current and recent incidents | | f5-status-get-maintenance | Scheduled maintenance windows | | f5-status-search | Search components, incidents, maintenance |

Example Queries

What is the current status of F5 Cloud services?
Are there any active incidents?
Show me components that are degraded
What maintenance is scheduled?
Search for API Gateway

Performance

Browser Pooling

The MCP server uses browser instance pooling for 40-60% faster scraping performance. Browser instances are reused across operations instead of creating new ones each time.

Configuration:

  • SCRAPER_POOLING_ENABLED=true - Enable/disable pooling (default: true)
  • SCRAPER_POOLING_MIN_SIZE=1 - Minimum browsers in pool (default: 1)
  • SCRAPER_POOLING_MAX_SIZE=3 - Maximum browsers in pool (default: 3)
  • SCRAPER_POOLING_IDLE_TIMEOUT=60000 - Close idle browsers after ms (default: 60s)
  • SCRAPER_POOLING_ACQUIRE_TIMEOUT=10000 - Browser acquisition timeout (default: 10s)
  • SCRAPER_POOLING_HEALTH_CHECK_INTERVAL=30000 - Health check frequency (default: 30s)
  • SCRAPER_POOLING_ENABLE_METRICS=true - Track performance metrics (default: true)

Performance Gains:

  • Single scrape: ~50% faster (2500ms → 1200ms)
  • Parallel scrapes: ~51% faster (8300ms → 4100ms)
  • Cache hit rate: >80% after warmup

Resource Usage:

  • Each browser: ~150MB memory
  • Max pool (3 browsers): ~450MB memory
  • Idle cleanup: Automatic after 60s

Disable if needed:

SCRAPER_POOLING_ENABLED=false

Links

License

MIT