SLA.directory MCP Server
Related Servers
Alternatives to SLA.directory MCP Server
No user-submitted related servers found.
Related Servers
AlicenseCqualityBmaintenanceConnects AI assistants to GetMonitor status pages, monitors, incidents, and maintenance schedules via read-only tools.10023 npmApache 2.0- FlicenseBqualityDmaintenanceEnables AI assistants to interact with Uptime Agent monitoring system to check uptime status, manage incidents, create new monitors, and analyze downtime through natural conversation.71-
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with Slack workspaces, providing tools for reading messages, posting content, managing channels, and more.2238MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with Slack workspaces, including listing channels, posting messages, replying to threads, adding reactions, and retrieving user information.1014 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search API documentation, retrieve endpoint details, get SDK snippets, and check changelogs from an OpenAPI spec.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to query and execute Slingrs ERP endpoints for sales orders, inventory, production, purchasing, shipments, and custom entities through dynamically loaded OpenAPI tools.7 npm-
TDQS
Scored across 6 tools
Each tool has a clear, distinct purpose: comparing vendors, fetching per-service SLAs, retrieving vendor details, listing categories, searching, and listing vendors by category. There is no overlap in functionality.
Most tools use a verb_noun pattern (compare_vendors, get_service_sla, get_vendor, list_categories, search_vendors). However, 'vendors_in_category' uses a noun_preposition_noun structure, breaking the pattern slightly.
With 6 tools, the set is well-scoped for an SLA directory. It covers essential operations without being too numerous or too few, providing a focused interface.
The tools cover searching, browsing by category, retrieving vendor details, per-service SLAs, and cross-vendor comparison. This represents a comprehensive read-only surface for the domain, with no obvious gaps.