1.0.7npm · @liuyoshio/mcp-compass · current release
Observed 2026-08-14T11:39:58.403Z using mcpSecurity-inventory. Status: succeeded. Negotiated protocol: 2025-06-18.
{
"tools": {}
}| Tool | Category | Annotations | Risk |
|---|---|---|---|
recommend-mcp-servers
Use this tool when there is a need to findn external MCP tools.
It explores and recommends existing MCP servers from the
internet, based on the description of the MCP Server
needed. It returns a list of MCP servers with their IDs,
descriptions, GitHub URLs, and similarity scores.
Input schema{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "\n Description for the MCP Server needed. \n It should be specific and actionable, e.g.:\n GOOD:\n - 'MCP Server for AWS Lambda Python3.9 deployment'\n - 'MCP Server for United Airlines booking API'\n - 'MCP Server for Stripe refund webhook handling'\n\n BAD:\n - 'MCP Server for cloud' (too vague)\n - 'MCP Server for booking' (which booking system?)\n - 'MCP Server for payment' (which payment provider?)\n\n Query should explicitly specify:\n 1. Target platform/vendor (e.g. AWS, Stripe, MongoDB)\n 2. Exact operation/service (e.g. Lambda deployment, webhook handling)\n 3. Additional context if applicable (e.g. Python, refund events)\n "
}
},
"required": [
"query"
]
} | — | — · — | — |