Unix Manual Server (MCP)

Created By
tizeea year ago
An MCP server that provides Unix command documentation directly within LLMs conversations.
Overview

What is Unix Manual Server (MCP)?

Unix Manual Server (MCP) is a server that provides Unix command documentation directly within conversations with LLMs, such as Claude.

How to use Unix Manual Server (MCP)?

To use the server, install it in a compatible client like Claude Desktop, and then you can request command documentation, list common commands, or check if a command exists.

Key features of Unix Manual Server (MCP)?

  • Retrieve help pages, man pages, and usage information for Unix commands.
  • Discover available commands on your system, categorized by function.
  • Verify if a specific command is available and get its version information.

Use cases of Unix Manual Server (MCP)?

  1. Getting help with specific Unix commands during development.
  2. Listing all available Unix commands for quick reference.
  3. Checking the availability of commands on a system before executing them.

FAQ from Unix Manual Server (MCP)?

  • Can I use Unix Manual Server with any LLM?

Currently, it is designed for use with Claude and other MCP-compatible clients.

  • Is there a cost to use Unix Manual Server?

No, it is free to use under the MIT license.

  • How does the server ensure security?

The server validates command names, executes commands without using a shell, and sets timeouts to prevent command injection.

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

Recommend Servers

View All
Voyei

3 hours ago
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.

13 hours ago