One host for all your MCP servers — shared instances, lazy start, one dashboard, a fraction of the RAM.
mcpd is a daemon/supervisor for MCP servers, not a primary tool provider. The 5 example tools (echo, add, read_file, sequentialthinking, whoami) are minimal demonstrations. Naming is adequate (verb-based: echo, add, read_file). Descriptions exist but are terse (10-194 chars). Schemas are present and properly typed for most tools. However, sequentialthinking has an exceptionally verbose description (1200+ chars) that violates token efficiency guidelines. Error handling is minimal, no recovery guidance or actionable error messages. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being read-only. Output schemas are not documented. This is a reference implementation, not production-grade.
Add two numbers
Echo back the provided text
Read a UTF-8 text file from disk
A detailed tool for dynamic and reflective problem-solving through thoughts. This tool helps analyze problems through a flexible thinking process that can adapt and evolve. Each thought can build on, question, or revise previous insights as understanding deepens. When to use this tool: - Breaking down complex problems into steps - Planning and design with room for revision - Analysis that might need course correction - Problems where the full scope might not be clear initially - Problems that require a multi-step solution - Tasks that need to maintain context over multiple steps - Situations where irrelevant information needs to be filtered out Key features: - You can adjust total_thoughts up or down as you progress - You can question or revise previous thoughts - You can add more thoughts even after reaching what seemed like the end - You can express uncertainty and explore alternative approaches - Not every thought needs to build linearly - you can branch or backtrack - Generates a solution hypothesis - Verifies the hypothesis based on the Chain of Thought steps - Repeats the process until satisfied - Provides a correct answer Parameters explained: - thought: Your current thinking step, which can include: * Regular analytical steps * Revisions of previous thoughts * Questions about previous decisions * Realizations about needing more analysis * Changes in approach * Hypothesis generation * Hypothesis verification - nextThoughtNeeded: True if you need more thinking, even if at what seemed like the end - thoughtNumber: Current number in sequence (can go beyond initial total if needed) - totalThoughts: Current estimate of thoughts needed (can be adjusted up/down) - isRevision: A boolean indicating if this thought revises previous thinking - revisesThought: If is_revision is true, which thought number is being reconsidered - branchFromThought: If branching, which thought number is the branching point - branchId: Identifier for the current branch (if any) - needsMoreThoughts: If reaching end but realizing more thoughts needed You should: 1. Start with an initial estimate of needed thoughts, but be ready to adjust 2. Feel free to question or revise previous thoughts 3. Don't hesitate to add more thoughts if needed, even at the "end" 4. Express uncertainty when present 5. Mark thoughts that revise previous thinking or branch into new paths 6. Ignore information that is irrelevant to the current step 7. Generate a solution hypothesis when appropriate 8. Verify the hypothesis based on the Chain of Thought steps 9. Repeat the process until satisfied with the solution 10. Provide a single, ideally correct answer as the final output 11. Only set nextThoughtNeeded to false when truly done and a satisfactory answer is reached
sequentialthinking description is 1200+ characters, violating token efficiency (guideline: 10-1024 chars, optimal 50-200). Wastes context and buries key details.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being read-only. Agents cannot infer safety properties.
Output schemas not documented. LLMs cannot plan downstream tool calls or extract structured data.
Error handling lacks recovery guidance. read_file returns 'failed to read: <message>' with no actionable next steps for the LLM.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | 2025-06-18+ | v2 |
Return this server's pid
read_file accepts absolute paths with no validation or sandboxing. No description of path constraints (e.g., allowed directories, symlink handling).