Model Context Protocol moderate risk

Didlogic

Didlogic MCP server provides LLMs access to Didlogic API for managing SIP accounts, call history, and transactions, with varying transport modes.

Connections & Capabilities

Connects To

GitHubTwitter

Capabilities

readwriteexecadmin

Quickstart

Install

pip install didlogic_mcp

Exposed MCP Tools (6)

moderate

Balance management tools

Tools to manage the balance of Didlogic accounts.

Modifying account balances carries financial risk.

high

SIP account (sipfriends) management

Tools to manage SIP accounts, including creation, modification, and deletion.

Improper management can disrupt communication services.

moderate

IP restriction management

Tools to manage IP restrictions for enhanced security.

Incorrect configuration can block legitimate access.

moderate

Purchases management

Tools to manage purchases made through the Didlogic API.

Managing purchases involves financial transactions.

safe

Call history access

Tools to access and retrieve call history data.

Read-only access to call history.

safe

Transaction history access

Tools to access and retrieve transaction history data.

Read-only access to transaction history.

Safety Assessment

The Didlogic MCP server offers valuable functionality but requires careful management of the API key. While IP restrictions add a layer of security, the potential for unintended actions by the LLM necessitates thorough testing and monitoring. Running in read-only mode where possible will greatly reduce risk.

API key authentication
IP restriction management capabilities
Access to call and transaction history for auditing
Specialized prompts for common operations

Full access to Didlogic API if key is compromised
Potential for unintended modifications via LLM
Exposure of sensitive data (call history, transactions)
Lack of explicit rate limiting mentioned