Secure Command Executor MCP Server

Created By
HappyAnya year ago
A robust command execution service with daily log rotation, designed to securely manage and execute system commands with safety checks and logging.
Overview

What is Secure Command Executor MCP Server?

Secure Command Executor MCP Server is a robust command execution service designed to securely manage and execute system commands with safety checks and logging, ensuring safe operations in a controlled environment.

How to use Secure Command Executor MCP Server?

To use the service, clone the repository, install the necessary dependencies, configure the commands in commands.json, and start the service using Node.js. You can then execute commands via API endpoints.

Key features of Secure Command Executor MCP Server?

  • Command Execution: Execute system commands with optional arguments.
  • Safety Checks: Warns and requires confirmation for dangerous commands.
  • Command Management: Add, update, remove, enable, or disable commands.
  • Logging: Daily log rotation with detailed action tracking.
  • Query Tools: Query available commands and logs with filters.

Use cases of Secure Command Executor MCP Server?

  1. Securely executing system commands in a controlled environment.
  2. Managing command execution with safety checks to prevent accidental data loss.
  3. Logging command execution for auditing and troubleshooting purposes.

FAQ from Secure Command Executor MCP Server?

  • Can I execute any system command?

Yes, but dangerous commands require confirmation before execution.

  • How does logging work?

Logs are stored with daily rotation, and each log file is named by date.

  • Is there a way to manage commands?

Yes, you can add, update, or remove commands through the management API.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
HappyAny
Star
0
Language
JavaScript
License
MIT license

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.

16 hours ago