botgathering-recipes
Related Servers
Alternatives to botgathering-recipes
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA lightweight Node.js MCP server with zero dependencies offering 9 built-in tools for system info, web fetching, GitHub search, file operations, shell execution, and key-value memory, enabling AI agents to perform these tasks via the Model Context Protocol.-
- AlicenseBqualityDmaintenanceDynamic MCP server for Node.js enabling runtime tool creation, management, and execution in isolated sandboxes (Docker or Node).811 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA basic MCP server implementation using Node.js and TypeScript that bridges AI models with external tools and data sources via JSON-RPC.2ISC
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes GreenNode AgentBase REST APIs as three searchable meta-tools (list_servers, search_tools, execute), reducing tool-definition overhead by ~95%. Runs locally over stdio or remotely over streamable HTTP with any MCP client.Apache 2.0
- AlicenseBqualityCmaintenanceAn MCP server that exposes unified tools for HTTP requests, web search and fetching, weather/time/currency, file and SQLite sandboxes, GitHub, email, calendars, and a self-learning SQLite FTS5 knowledge base. It supports stdio, SSE, and streamable-HTTP transports with Bearer-token auth and SSRF protection so AstrBot agents can call these capabilities directly.351MIT
- AlicenseNot gradedqualityDmaintenanceA self-extending MCP server that enables AI agents to browse the web, execute shell and Node snippets, automate browser workflows, access files and git, communicate with other agents, and use dozens of domain-specific calculation and research tools.MIT
TDQS
Scored across 10 tools
Descriptions work hard to distinguish tools (e.g. ask_how_to vs search_recipes, get_recipe vs get_recipe_details vs download_recipe), but there are genuinely overlapping clusters: three reading tools and two outcome-reporting tools (quick_report vs report_result). Boundaries exist but require careful reading of long descriptions to select correctly.
Mostly consistent verb_noun snake_case (get_recipe, report_result, list_categories, register_bot, download_recipe, search_recipes). A few deviations (quick_report, ask_how_to, whoami) are readable but break the strict pattern.
Ten tools cleanly cover the recipe lifecycle from discovery through account management and reporting. Each tool earns its place without padding.
Full consumer-side lifecycle is covered: discovery, reading, downloading, reporting, and account management. Minor gaps like commenting on proposals or editing authored recipes, but core workflows are complete.