# TgPay Merchant API (remote · app.tgpaycrypto.com)

Accept crypto payments via the TgPay Merchant API — invoices, subscriptions, webhooks.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `app.tgpaycrypto.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-tgpaybot-merchant-api/app-2.md), [page](https://verifymcp.io/servers/com-tgpaybot-merchant-api/app-2)

## Channel facts

- Endpoint: `https://app.tgpaycrypto.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (deleteInvoice).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 47/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1457 tokens (~56/item across 26 items; 20 tools + 6 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 39/100
  - Stability check failed: schema churn in the 13 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the TgPay Merchant API MCP server?

TgPay Merchant API is a hosted endpoint at https://app.tgpaycrypto.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-tgpaybot-merchant-api 'https://app.tgpaycrypto.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-tgpaybot-merchant-api": {
      "url": "https://app.tgpaycrypto.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-tgpaybot-merchant-api": {
      "type": "http",
      "url": "https://app.tgpaycrypto.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-tgpaybot-merchant-api]
url = "https://app.tgpaycrypto.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-tgpaybot-merchant-api": {
      "type": "remote",
      "url": "https://app.tgpaycrypto.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-tgpaybot-merchant-api --url 'https://app.tgpaycrypto.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-tgpaybot-merchant-api:
    url: "https://app.tgpaycrypto.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-tgpaybot-merchant-api": {
      "Transport": "http",
      "Url": "https://app.tgpaycrypto.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-tgpaybot-merchant-api -t streamable-http -u 'https://app.tgpaycrypto.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-tgpaybot-merchant-api": {
      "type": "http",
      "url": "https://app.tgpaycrypto.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 66, +1)

- [functional] Server version: fb6f07c9 → d0ee41ae

### 2026-09-19 (score 65, 0)

- [functional] Server version: 573bdd8f → fb6f07c9

### 2026-09-18 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 29 to 32.

### 2026-09-17 (score 64, 0)

- [functional] Server version: 6706b389 → 573bdd8f

### 2026-09-16 (score 64, +1)

- [functional] Server version: 66d6cabb → 6706b389

### 2026-09-15 (score 63, 0)

- [functional] Server version: 367e837f → 66d6cabb

### 2026-09-14 (score 63, +1)

- [functional] Server version: e27cef20 → 367e837f

### 2026-09-13 (score 62, +2)

- [security regression] Stability: 0.17 → fail
- [security regression] Tool “refundInvoice” was removed
- [security improvement] HSTS header: fail → pass
- [functional] Server version: 6fe4f6e4 → e27cef20

## MCP tools (20)

### `get_docs` (~61 tokens)

Read a TgPay Merchant API integration doc. START HERE before integrating: topics quickstart, invoices, subscriptions, transfers-checks, webhooks, errors.

Input parameters:

- `topic` (string, required): quickstart | invoices | subscriptions | transfers-checks | webhooks | errors

### `connect` (~104 tokens)

Start token issuance WITHOUT the Mini App UI: creates a merchant-app request and returns a t.me approve link plus a poll_secret. Show the link to the human — they approve with one button in the @tgpaycryptobot bot — then call connect_status with the poll_secret. Use only when no API token is configured yet.

Input parameters:

- `app_name` (string, required): Merchant app name shown to the approving human, 1-64 chars (e.g. the project/bot name).

### `connect_status` (~120 tokens)

Poll a connect request. Returns pending | denied | expired, or — once approved — the app id and the API TOKEN (returned exactly once: save it to the project's .env immediately, never print it in logs). The token is SCOPED (read, invoices, subscriptions, webhooks) — it cannot move money out of the app; transfers/refunds/checks need the primary token the human holds in the Mini App. Poll every 3-5 seconds while pending.

Input parameters:

- `poll_secret` (string, required): The poll_secret from the connect tool.

### `getMe` (~23 tokens)

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

### `getBalance` (~19 tokens)

Merchant app balance per asset (available + onhold).

### `getCurrencies` (~22 tokens)

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

### `getExchangeRates` (~18 tokens)

Current asset↔fiat display rates.

### `getStats` (~44 tokens)

App volume/count stats for a period.

Input parameters:

- `end_at` (string): ISO 8601 period end.
- `start_at` (string): ISO 8601 period start.

### `getInvoices` (~84 tokens)

List invoices (newest first).

Input parameters:

- `asset` (string): Filter by asset code.
- `count` (integer): Page size (default 100).
- `fiat` (string): Filter by fiat code.
- `invoice_ids` (string): Comma-separated ids.
- `offset` (integer): Skip this many.
- `status` (string): active | paid | expired.

### `getChecks` (~67 tokens)

List checks.

Input parameters:

- `asset` (string): Filter by asset code.
- `check_ids` (string): Comma-separated ids.
- `count` (integer): Page size (default 100).
- `offset` (integer): Skip this many.
- `status` (string): active | activated.

### `getTransfers` (~74 tokens)

List app→user transfers.

Input parameters:

- `asset` (string): Filter by asset code.
- `count` (integer): Page size (default 100).
- `offset` (integer): Skip this many.
- `spend_id` (string): Filter by idempotency key.
- `transfer_ids` (string): Comma-separated ids.

### `getSubscriptionPlans` (~13 tokens)

List subscription plans.

### `getSubscriptions` (~52 tokens)

List subscriptions (subscribers).

Input parameters:

- `plan_id` (integer): Filter by plan.
- `status` (string): active | grace | cancelled | expired.
- `user_id` (integer): Filter by Telegram user id.

### `createInvoice` (~282 tokens)

Create a one-off payment invoice; the payer opens result.mini_app_invoice_url. See the invoices doc.

Input parameters:

- `accepted_assets` (string): Fiat mode: comma-separated assets the payer may pay in.
- `allow_anonymous` (boolean): Default true.
- `allow_comments` (boolean): Default true.
- `amount` (string): Decimal string in MAJOR units, e.g. "5" = 5 USDT. Never a float. Omit for an open-amount invoice.
- `asset` (string): Asset code (crypto mode).
- `currency_type` (string): crypto (default) | fiat.
- `description` (string): Shown to the payer (≤1024).
- `expires_in` (integer): Invoice TTL in seconds.
- `fiat` (string): Fiat code (fiat mode).
- `hidden_message` (string): Revealed to the payer ONLY after payment (≤2048).
- `paid_btn_name` (string): viewItem | openChannel | openBot | callback.
- `paid_btn_url` (string): URL for the paid button.
- `payload` (string): Opaque data echoed back in the webhook (≤4096).
- `rate_lock_seconds` (integer): Fiat mode: freeze crypto quotes for this long.
- `swap_to` (string): Auto-convert the received amount to this asset.

### `deleteInvoice` (~25 tokens)

Delete an unpaid invoice.

Input parameters:

- `invoice_id` (integer, required): The invoice to delete.

### `deleteCheck` (~31 tokens)

Delete an unclaimed check (refunds the hold).

Input parameters:

- `check_id` (integer, required): The check to delete.

### `createSubscriptionPlan` (~113 tokens)

Create an IMMUTABLE recurring-billing plan; send payers to result.mini_app_subscribe_url. See the subscriptions doc.

Input parameters:

- `amount` (string, required): Decimal string in MAJOR units, e.g. "5" = 5 USDT. Never a float. Charged per period.
- `asset` (string, required): Asset code, e.g. USDT.
- `name` (string, required): Plan name shown to payers (≤64).
- `period_days` (integer, required): Billing period in days.

### `archiveSubscriptionPlan` (~34 tokens)

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

Input parameters:

- `plan_id` (integer, required): The plan to archive.

### `cancelSubscription` (~30 tokens)

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

Input parameters:

- `subscription_id` (integer, required): The subscription.

### `updateApp` (~114 tokens)

Update app name / webhook_url (https) / webhook_events opt-in list. Needs the 'webhooks' scope (the connect-issued token has it) or the primary token. See the webhooks doc for the event types and signature verification.

Input parameters:

- `name` (string): New app name (1-64).
- `webhook_events` (array): Extended event types to opt into (invoice_paid is always delivered); [] = invoice_paid-only.
- `webhook_url` (string): https URL for webhook delivery; "" clears it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-tgpaybot-merchant-api/app-2#diagnostics

## Score history

- 2026-09-20: 66
- 2026-09-19: 65
- 2026-09-18: 65
- 2026-09-17: 64
- 2026-09-16: 64
- 2026-09-15: 63
- 2026-09-14: 63
- 2026-09-13: 62
- 2026-09-12: 60
- 2026-09-11: 60
- 2026-09-10: 59
- 2026-09-09: 59
- 2026-09-08: 58
- 2026-09-07: 58

## Common questions

### What is the TgPay Merchant API MCP server?

TgPay Merchant API is an MCP server listed in the public MCP registry as com.tgpaybot/merchant-api. Accept crypto payments via the TgPay Merchant API, invoices, subscriptions, webhooks. This page covers its hosted endpoint (https://app.tgpaycrypto.com/mcp).

### Is the TgPay Merchant API MCP server safe to use?

TgPay Merchant API scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the TgPay Merchant API MCP server expose?

TgPay Merchant API exposes 20 tools: get_docs, connect, connect_status, getMe, getBalance, and 15 more. Their descriptions and schemas cost roughly 1,330 tokens of context every time the server is loaded.

### Does the TgPay Merchant API MCP server require authentication?

No. We connected to TgPay Merchant API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the TgPay Merchant API MCP server still maintained?

TgPay Merchant API is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://app.tgpaycrypto.com/mcp
- Website: https://app.tgpaycrypto.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-tgpaybot-merchant-api/app-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-tgpaybot-merchant-api/app-2.json
- HTML version of this page: https://verifymcp.io/servers/com-tgpaybot-merchant-api/app-2