Model Context Protocol moderate risk

Iaptic

MCP server for Iaptic, enabling AI access to customer, purchase, transaction, and statistical data via API, with app management capabilities.

Connections & Capabilities

Connects To

GitHubTwitter

Capabilities

readwriteexecadmin

Quickstart

Install

npx -y @smithery/cli install mcp-server-iaptic --client claude

Config

{
  "iaptic": {
    "command": "npx",
    "args": [
      "mcp-server-iaptic",
      "--api-key", "your-api-key-here",
      "--app-name", "your-app-name-here"
    ]
  }
}

Exposed MCP Tools (12)

safe

customer_list

Lists all customers.

Read-only operation.

safe

customer_get

Retrieves details for a specific customer by ID.

Read-only operation.

safe

purchase_list

Lists purchases with filtering and pagination.

Read-only operation with limits.

safe

purchase_get

Retrieves details for a specific purchase by ID.

Read-only operation.

safe

transaction_list

Lists transactions with filtering and pagination.

Read-only operation with limits.

safe

transaction_get

Retrieves details for a specific transaction by ID.

Read-only operation.

safe

stats_get

Retrieves general statistics about transactions and revenue.

Read-only operation.

safe

stats_app

Retrieves app-specific statistics.

Read-only operation.

safe

event_list

Lists recent events with filtering and pagination.

Read-only operation with limits.

high

iaptic_switch_app

Switches to a different Iaptic app using provided credentials.

Modifies the active app context and requires API key.

moderate

iaptic_reset_app

Resets to the default Iaptic app.

Changes the active app context.

safe

iaptic_current_app

Retrieves information about the currently active app.

Read-only operation.

Safety Assessment

This server is relatively safe for read operations. Exercise caution when using write operations, ensuring the API key is securely managed. It's risky if the API key is exposed, potentially leading to unauthorized data modification.

API key authentication required.
Read and write operations are available, but limited to Iaptic data.
Clear separation of concerns with specific tools for each data type.
Rate limiting on the Iaptic API provides some protection against abuse.

API key management is the user's responsibility.
No built-in sandboxing; relies on Iaptic API security.
Potential for data exposure if API key is compromised.
Write operations can modify data within Iaptic.