didlogic_mcp
Related Servers
Alternatives to didlogic_mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceAn implementation of the Model Context Protocol (MCP) server that exposes Twilio APIs to AI assistants and tools, allowing them to interact with Twilio services through the MCP protocol.111MIT
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server integrating with various LLM clients.2MIT
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server for integrating with various LLM clients like Claude Desktop.1164MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that bridges MCP clients with local LLM services, enabling seamless integration with MCP-compatible applications through standard tools like chat completion, model listing, and health checks.-
- FlicenseNot gradedqualityDmaintenanceA foundational implementation of a Model Context Protocol (MCP) server designed for educational purposes. It demonstrates the complete interaction between an LLM, an inference engine, and a client during an agentic call.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that supports STDIO, SSE and Streamable HTTP protocols for AI model interactions.92 npm1MIT
TDQS
Scored across 22 tools
The tools are mostly distinct in their target resources (DIDs, SIP accounts, destinations, countries). However, 'get_sip_account' vs 'list_sip_accounts' and 'create_sip_account' vs 'update_sip_account' could be confused since both have similar parameter sets. The 'list_country_cities' and 'list_country_cities_in_region' are clearly separate but their descriptions are similar, requiring careful reading to distinguish.
Most tools follow a consistent 'verb_noun' pattern (e.g., list_countries, get_sip_account, remove_purchased_did). There are minor deviations: 'get_allowed_ips' vs 'add_allowed_ip' and 'delete_allowed_ip' are consistent, but 'list_dids_in_country_city' is a bit long and awkward. Overall, the naming is predictable and readable.
With 22 tools, the count is slightly high but still within a reasonable range for a comprehensive DID management server. The tools cover multiple domains (DID purchase, SIP accounts, destinations, transactions), so the count is justified. It does not feel bloated, but it is on the heavier side.
The tool surface covers the primary lifecycle for DIDs (list, purchase, remove), SIP accounts (create, get, update, delete), destinations (list, add, delete), and transactions. There are minor gaps: no direct 'update_did' or 'change_did_forwarding' tool, but these are handled through destination management. Also, there is no 'get_purchase' by ID, but list_purchases covers the need. Overall, the domain is well-covered.