Monitor MCP Server

Created By
unxaia year ago
Overview

what is Monitor MCP Server?

Monitor MCP Server is a system monitoring server based on the Message Control Protocol (MCP) that monitors CPU, memory, and disk usage on Mac systems.

how to use Monitor MCP Server?

To use Monitor MCP Server, you can utilize the provided tools to fetch system information such as CPU, memory, and disk usage by calling the respective functions: get_cpu_info(), get_memory_info(), and get_disk_info().

key features of Monitor MCP Server?

  • CPU usage monitoring:
    • Monitors usage per CPU core
    • Provides CPU frequency information
    • Displays the number of CPU cores
  • Memory usage monitoring:
    • Total memory
    • Available memory
    • Memory usage rate
    • Used and free memory
  • Disk usage monitoring:
    • Monitors usage per partition
    • Displays file system type
    • Shows total, used, and available space

use cases of Monitor MCP Server?

  1. Monitoring CPU performance in real-time.
  2. Analyzing memory usage trends over time.
  3. Keeping track of disk space utilization across different partitions.

FAQ from Monitor MCP Server?

  • What systems does Monitor MCP Server support?

Monitor MCP Server is designed for Mac systems.

  • Is there a graphical interface for Monitor MCP Server?

Currently, it operates through command-line tools.

  • What dependencies are required to run Monitor MCP Server?

It requires MCP protocol implementation and the psutil library for system and process monitoring.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
unxai
Star
0
Language
Python
License
-
Category
monitoring

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago