Skip to main content
Glama
idpay-mcp

idpay-mcp

by theYahia

idpay-mcp

MCP server for IDPay payment gateway (Iran). Supports payment creation, verification, inquiry, transaction listing, and payment links. Uses X-API-KEY header with optional X-SANDBOX mode.

Tools (8)

Tool

Description

create_payment

Create a payment

verify_payment

Verify a payment

get_payment

Get payment details

list_transactions

List transactions

create_link

Create a payment link

get_link

Get payment link details

list_links

List all payment links

delete_link

Delete a payment link

Related MCP server: vnpay-mcp

Quick Start

{
  "mcpServers": {
    "idpay": {
      "command": "npx",
      "args": ["-y", "@theyahia/idpay-mcp"],
      "env": {
        "IDPAY_API_KEY": "<YOUR_API_KEY>",
        "IDPAY_SANDBOX": "0"
      }
    }
  }
}

Environment Variables

Variable

Required

Description

IDPAY_API_KEY

Yes

API key from IDPay dashboard

IDPAY_SANDBOX

No

Set to "1" for sandbox mode

Demo Prompts

  • "Create a payment for 50000 IRR with order ID ORD-001"

  • "Verify payment abc123 for order ORD-001"

  • "List my recent transactions"

  • "Create a payment link for 100000 IRR"

  • "Delete payment link lnk_abc123"

License

MIT

Available Tools

8 tools
create_paymentC

Create an IDPay payment.

Inputs: amount (required), callback (required), order_id (required), mail, +3 more.

get_paymentC

Get payment details by ID.

Inputs: id (required), order_id (required).

list_transactionsC

List payment transactions.

Inputs: page, date_to, date_from, page_size.

verify_paymentD

Verify an IDPay payment.

Inputs: id (required), order_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool clearly targets a distinct resource: payment links (list/create/get/delete) and payments (create/verify/get), with transactions listed separately. There is no ambiguity as the purpose of each tool is unique.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., list_links, create_payment, verify_payment). The verbs and nouns are predictable and consistently use snake_case.

    Tool Count5/5

    With 8 tools, the server is well-scoped for a payment processing domain, covering both payments and payment links without unnecessary redundancy. The number is appropriate and neither too sparse nor overwhelming.

    Completeness4/5

    The tool set covers the core lifecycle for payments (create, verify, get) and payment links (create, list, get, delete). The only notable missing operation is an update for payment links, but this is a minor gap and does not severely hinder the primary workflows.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A Python-based MCP server for managing Paytm payment links and transactions. It enables users to create payment links, list created links, and retrieve transaction details for specific payment links.
      -
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for VNPay payment gateway (Vietnam). Supports payment URL generation, transaction queries, refunds, tokenized payments, and IPN verification with HMAC-SHA512 signing.
      8
      10 npm
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      MCP server for Payme payment system (Uzbekistan). Supports transactions, statements, payment links, and balance queries via JSON-RPC 2.0.
      8
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Bank of Georgia iPay payment gateway, enabling payment orders, refunds, recurring payments, and pre-authorization via OAuth 2.0 + JWT.
      8
      16 npm
      MIT