TgPay Merchant API
REMOTE · APP.TGPAYCRYPTO.COM
Accept crypto payments via the TgPay Merchant API — invoices, subscriptions, webhooks.
Available components
Last scanned (4 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (deleteInvoice). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability47
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1466 tokens (~56/item across 26 items; 20 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Server version: 54dac287 → 549611c1 functional
- 4 Nov 26 0
- Server version: a40a50d1 → 54dac287 functional
- 3 Nov 26 0
- Tool “connect” rewrote its description, which is the text the model reads security
- Server version: 45dca11c → a40a50d1 functional
- “getChecks” reworded the description of “status” cosmetic
- 2 Nov 26 0
- Server version: 26e8ff4c → 45dca11c functional
- 1 Nov 26 0
- Server version: 8e41f6e4 → 26e8ff4c functional
- 31 Oct 26 0
- Server version: 85491c26 → 8e41f6e4 functional
- 30 Oct 26 0
- Server version: 915bbd3f → 85491c26 functional
- 29 Oct 26 0
- Server version: cbb99808 → 915bbd3f functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://app.tgpaycrypto.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tgpaycrypto.com | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8597273705683081139f2f7c9f98f72a |
| SANs: tgpaycrypto.com, *.tgpaycrypto.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.tgpaycrypto.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tgpaycrypto.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' https://web.telegram.org |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.tgpaycrypto.com/mcp | Verified | 200 | |
| http (plaintext) | http://app.tgpaycrypto.com/mcp | HTTPS enforced | 301 | https://app.tgpaycrypto.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
archiveSubscriptionPlan ~34
Stop new signups for a plan (live subscriptions keep renewing).
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | integer | yes | The plan to archive. |
No output schema declared.
No examples provided.
cancelSubscription ~30
Stop future charges for one subscription (paid time runs out).
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | integer | yes | The subscription. |
No output schema declared.
No examples provided.
connect ~111
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 ("Create app and issue token") in the @tgpaycryptobot bot — then call connect_status with the poll_secret. Use only when no API token is configured yet.
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | Merchant app name shown to the approving human, 1-64 chars (e.g. the project/bot name). |
No output schema declared.
No examples provided.
connect_status ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| poll_secret | string | yes | The poll_secret from the connect tool. |
No output schema declared.
No examples provided.
createInvoice ~282
Create a one-off payment invoice; the payer opens result.mini_app_invoice_url. See the invoices doc.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
createSubscriptionPlan ~113
Create an IMMUTABLE recurring-billing plan; send payers to result.mini_app_subscribe_url. See the subscriptions doc.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Decimal string in MAJOR units, e.g. "5" = 5 USDT. Never a float. Charged per period. |
| asset | string | yes | Asset code, e.g. USDT. |
| name | string | yes | Plan name shown to payers (≤64). |
| period_days | integer | yes | Billing period in days. |
No output schema declared.
No examples provided.
deleteCheck ~31
Delete an unclaimed check (refunds the hold).
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | integer | yes | The check to delete. |
No output schema declared.
No examples provided.
deleteInvoice ~25
Delete an unpaid invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | integer | yes | The invoice to delete. |
No output schema declared.
No examples provided.
get_docs ~61
Read a TgPay Merchant API integration doc. START HERE before integrating: topics quickstart, invoices, subscriptions, transfers-checks, webhooks, errors.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | quickstart | invoices | subscriptions | transfers-checks | webhooks | errors |
No output schema declared.
No examples provided.
getBalance ~19
Merchant app balance per asset (available + onhold).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
getChecks ~69
List checks.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | expired. |
No output schema declared.
No examples provided.
getCurrencies ~22
Supported crypto assets (code/name/decimals) and fiats.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
getExchangeRates ~18
Current asset↔fiat display rates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
getInvoices ~84
List invoices (newest first).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
getMe ~23
Verify the token: app id, name, webhook config, token scopes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
getStats ~44
App volume/count stats for a period.
| Name | Type | Req | Description |
|---|---|---|---|
| end_at | string | – | ISO 8601 period end. |
| start_at | string | – | ISO 8601 period start. |
No output schema declared.
No examples provided.
getSubscriptionPlans ~13
List subscription plans.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
getSubscriptions ~52
List subscriptions (subscribers).
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | integer | – | Filter by plan. |
| status | string | – | active | grace | cancelled | expired. |
| user_id | integer | – | Filter by Telegram user id. |
No output schema declared.
No examples provided.
getTransfers ~74
List app→user transfers.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
updateApp ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · app.tgpaycrypto.com
claude mcp add --transport http com-tgpaybot-merchant-api 'https://app.tgpaycrypto.com/mcp'
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 74 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,339 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.