FOAAS MCP Server
Related Servers
Alternatives to FOAAS MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceA demonstration MCP server built with FastMCP v2.0 that provides basic mathematical calculations and greeting functionality. Features Docker containerization, comprehensive testing, and CI/CD automation for learning MCP development patterns.2-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that reviews code with the sarcastic and cynical tone of a grumpy senior developer, helping identify issues in PRs and providing feedback on code quality.5 npm21MIT
- FlicenseBqualityDmaintenanceMCP server for natural-language control of local Docker, covering containers, images, volumes, networks, and Compose stacks, plus security scanning and diagnostics.34-
- -licenseNot gradedqualityNot gradedmaintenanceA basic MCP server built with FastMCP framework that provides simple utility tools including message echoing and server information retrieval. Supports both stdio and HTTP transports with Docker deployment capabilities.-
- AlicenseNot gradedqualityDmaintenanceA Dockerized MCP server that enables Discord integration, offering tools for role management, messaging, moderation, and server administration via natural language.1MIT
- AlicenseBqualityDmaintenanceMCP server for managing Docker containers, images, and Compose services via natural language, with configurable tool permissions and safety annotations.16MIT
TDQS
Scored across 23 tools
The tools have detailed descriptions specifying distinct scenarios (e.g., general insult vs. enthusiasm vs. sarcasm), making them mostly distinguishable. However, some pairs like 'foaas_think' and 'foaas_thinking' are very similar in purpose, causing slight ambiguity.
All tools follow a consistent pattern: 'foaas_' prefix followed by a single lowercase word (e.g., foaas_asshole, foaas_awesome). No mixing of conventions or irregular naming.
With 23 tools, the count is slightly high but reasonable for covering a variety of insult/expression types. Each tool corresponds to a distinct API endpoint, so the number matches the domain scope.
The set covers a wide range of common expressions (anger, praise, dismissal, confusion) but misses some well-known FOAAS endpoints like 'this', 'that', or 'everything'. Gaps exist but the core use cases are present.