deeptap-mcp
Related Servers
Alternatives to deeptap-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceAn MCP server for in-loop design review of web previews. It enables agents to submit a preview URL, receive structured findings with suggested fixes, and recheck after applying changes, while never editing code itself.52MIT- FlicenseNot gradedqualityBmaintenanceEnables AI agents to access unified development tools including code generation, documentation synchronization, test case rendering, and architecture graph queries through a single MCP server.-
- AlicenseNot gradedqualityAmaintenanceApp Store Connect MCP server — lets AI agents manage iOS releases, TestFlight builds, screenshots, and review submissions directly from App Store Connect.49 npm1MIT
- AlicenseAqualityCmaintenanceAn MCP server that enables coding agents to set up and manage webhook infrastructure, including provisioning endpoints, event logs, replay, and testing.13Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server that provides a single tool for discovering, auto-installing, sandboxing, and calling any API from the printing-press corpus. It enables agents to seamlessly find and execute API operations without per-API setup.MIT
- AlicenseAqualityDmaintenanceAn MCP server that scans code repositories for app store rejection risks by mapping API usage to required declarations and policy deadlines, enabling agents to catch issues before submission.5MIT
TDQS
Scored across 6 tools
Each tool has a unique purpose: account info, domain verification, listing, retrieval, creation, and updating. No two tools overlap, and the distinction between list/get and create/update is clear.
All tools follow a consistent verb_noun pattern in snake_case (get_account, verify_domain, list_domains, get_domain, create_domain, update_domain). This makes the API predictable and easy to navigate.
With 6 tools, the server covers its domain management purpose without excess. Each tool is necessary and the count is typical for a focused CRUD-style API.
The domain lifecycle is mostly complete with list, get, create, and update, but a delete_domain operation is missing. The verify_domain tool adds value, yet the absence of delete is a minor gap for full resource management.