Skill History vs Meyhem — MCP Server Discovery & Agent Search
In-depth architectural comparison of the Skill History and Meyhem — MCP Server Discovery & Agent Search MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Skill History
Developer Tools · Local stdio
Quality: 31/100 (Emerging) | Auth: No auth required
Meyhem — MCP Server Discovery & Agent Search
Developer Tools · Local stdio
Quality: 37/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Skill History if you need specialized Developer Tools tools running via a local process. Choose Meyhem — MCP Server Discovery & Agent Search if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Skill History when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Skill History is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Meyhem — MCP Server Discovery & Agent Search belongs to Developer Tools using local stdio subprocess. Select Skill History when you need capabilities focused on developer tools and Meyhem — MCP Server Discovery & Agent Search when you require tools for developer tools.