MCP Server

Created By
Hades-gsla year ago
MCP Server is a tool for injecting faults and performing stress tests on Kubernetes pods and hosts using Chaos Mesh.
Overview

what is MCP Server?

MCP Server is a tool designed for injecting faults and performing stress tests on Kubernetes pods and hosts using Chaos Mesh. It helps developers ensure the resilience and reliability of their applications by simulating various failure scenarios.

how to use MCP Server?

To use MCP Server, clone the repository, set up a virtual environment, install dependencies, and run the server. You can specify the transport method for communication.

key features of MCP Server?

  • Pod Fault Injection: Simulate pod failures, pod kills, and container kills.
  • Pod Stress Testing: Simulate CPU and memory stress tests on pods.
  • Host Stress Testing: Simulate CPU and memory stress tests on hosts.
  • Host Disk Faults: Simulate disk fill, read payload, and write payload faults on hosts.
  • Network Faults: Simulate network partition and bandwidth limitations.
  • Log Retrieval: Retrieve logs for specific services and containers.
  • Load Test Monitoring: Parse and retrieve aggregated load test results.

use cases of MCP Server?

  1. Testing the resilience of microservices in a Kubernetes environment.
  2. Simulating real-world failure scenarios to improve application reliability.
  3. Monitoring and analyzing the impact of stress tests on system performance.

FAQ from MCP Server?

  • Can MCP Server be used with any Kubernetes cluster?

Yes! MCP Server is designed to work with any Kubernetes cluster that has Chaos Mesh installed.

  • Is there any cost associated with using MCP Server?

No! MCP Server is open-source and free to use.

  • What are the prerequisites for using MCP Server?

You need to have uv installed and Chaos Mesh set up in your Kubernetes cluster.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Hades-gsl
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago