# com.tgpaybot/merchant-api

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.2
- **Author:** com.tgpaybot
- **License:** Unknown
- **Endpoints:** streamable-http https://app.tgpaycrypto.com/mcp
- **Source:** https://app.tgpaycrypto.com/mcp
- **Endpoint health:** reachable (last checked 2026-10-07T06:29:49.010Z, 6 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-07T06:29:49.010Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

20 declared. Observed from a live `tools/list` probe.
- `get_docs` — Read a TgPay Merchant API integration doc. START HERE before integrating: topics quickstart, invoices, subscriptions, transfers-checks, webhooks, errors.
- `connect` — 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 — th
- `connect_status` — 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 .
- `getMe` — Verify the token: app id, name, webhook config, token scopes.
- `getBalance` — Merchant app balance per asset (available + onhold).
- `getCurrencies` — Supported crypto assets (code/name/decimals) and fiats.
- `getExchangeRates` — Current asset↔fiat display rates.
- `getStats` — App volume/count stats for a period.
- `getInvoices` — List invoices (newest first).
- `getChecks` — List checks.
- `getTransfers` — List app→user transfers.
- `getSubscriptionPlans` — List subscription plans.
- `getSubscriptions` — List subscriptions (subscribers).
- `createInvoice` — Create a one-off payment invoice; the payer opens result.mini_app_invoice_url. See the invoices doc.
- `deleteInvoice` — Delete an unpaid invoice.
- `deleteCheck` — Delete an unclaimed check (refunds the hold).
- `createSubscriptionPlan` — Create an IMMUTABLE recurring-billing plan; send payers to result.mini_app_subscribe_url. See the subscriptions doc.
- `archiveSubscriptionPlan` — Stop new signups for a plan (live subscriptions keep renewing).
- `cancelSubscription` — Stop future charges for one subscription (paid time runs out).
- `updateApp` — 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 w

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"merchant-api\": {\n      \"type\": \"http\",\n      \"url\": \"https://app.tgpaycrypto.com/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/com.tgpaybot%2Fmerchant-api
- Install plan: https://forgeregistry.com/api/v1/packages/com.tgpaybot%2Fmerchant-api/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/com.tgpaybot%2Fmerchant-api
- HTML page: https://forgeregistry.com/registry/com.tgpaybot%2Fmerchant-api
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.