eCommerce

tgpaybot.com

Provides an interface to the TgPay Merchant API for payment operations, including token connection, status polling, and balance checks.

1 endpoint24 known toolsFirst detected August 28, 2026Last detected August 28, 2026

ENDPOINT 1

https://crypto.tgpaybot.com/mcp

No auth detected

MCP server metadata

Name: tgpay
Version: c6957ebb

Capabilities

toolsresources

Server instructions

TgPay Merchant API — crypto payments inside Telegram (CryptoBot-compatible). Read get_docs('quickstart') before integrating. No API token yet? Call connect — the human approves once in Telegram — then poll connect_status; afterwards pass the token via the 'TgCryptoPay-API-Token' header on this MCP server, or as an extra 'api_token' argument on any tool. Amounts are decimal strings in major units; user_id is the Telegram user id.

Known tools 24

get_docs

Read a TgPay Merchant API integration doc.

Inferred read-only

connect

Start token issuance WITHOUT the Mini App UI: creates a merchant-app request and returns a t.

Inferred read-only

connect_status

Poll a connect request.

Inferred read-only

getMe

Verify the token: app id, name, webhook config, token scopes.

Inferred read-only

getBalance

Merchant app balance per asset (available + onhold).

Inferred read-only

getCurrencies

Supported crypto assets (code/name/decimals) and fiats.

Inferred read-only

getExchangeRates

Current asset↔fiat display rates.

Inferred read-only

getStats

App volume/count stats for a period.

Inferred read-only

getInvoices

List invoices (newest first).

Inferred read-only

getChecks

List checks.

Inferred read-only

getTransfers

List app→user transfers.

Inferred read-only

getSubscriptionPlans

List subscription plans.

Inferred read-only

getSubscriptions

List subscriptions (subscribers).

Inferred read-only

createInvoice

Create a one-off payment invoice; the payer opens result.

Potential side effects

deleteInvoice

Delete an unpaid invoice.

Potential side effects

refundInvoice

Refund a paid invoice (moves money app→payer; partial refunds accumulate up to the face amount).

Potential side effects

createCheck

Create a bearer payout link (moves money to a hold).

Potential side effects

deleteCheck

Delete an unclaimed check (refunds the hold).

Potential side effects

transfer

Pay a Telegram user from the app balance (instant, irreversible).

Potential side effects

transferBatch

Batch of transfers; items succeed/fail independently.

Inferred read-only

createSubscriptionPlan

Create an IMMUTABLE recurring-billing plan; send payers to result.

Potential side effects

archiveSubscriptionPlan

Stop new signups for a plan (live subscriptions keep renewing).

Inferred read-only

cancelSubscription

Stop future charges for one subscription (paid time runs out).

Inferred read-only

updateApp

Update app name / webhook_url (https) / webhook_events opt-in list.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.tgpay]
url = "https://crypto.tgpaybot.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "tgpay": {
      "type": "http",
      "url": "https://crypto.tgpaybot.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: tgpay
Remote MCP URL: https://crypto.tgpaybot.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "tgpay": {
      "url": "https://crypto.tgpaybot.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "tgpay": {
      "type": "http",
      "url": "https://crypto.tgpaybot.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "tgpay",
  "transport": "streamable-http",
  "url": "https://crypto.tgpaybot.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.