_ registry / mcp streamable-http · checked 6h ago

tgpay

https://app.tgpaycrypto.com

Registry code: 3f398ef28bc346ea

api record

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 'TgPayCrypto-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.

endpoint
https://app.tgpaycrypto.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is tgpay live?
Yes — it answered the hub's last check (checked 6h ago). It answered 99% of checks over the last 30 days.
Is tgpay free to use?
Yes — the hub reached it with no key and no payment.
What tools does tgpay have?
20 tools: getBalance, get_docs, getTransfers, createInvoice, cancelSubscription, updateApp, getStats, archiveSubscriptionPlan, ….
Is tgpay safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.6%· all time 99.6%

latency
423ms

last good check

priced tools
0

of 20 tools

_ answered our checks, 90 days 275 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
payments & commerce payment infrastructure
used for
  • create a crypto payment invoice in telegram
  • create a subscription plan
  • check merchant balance
  • list invoices and transfers
takes → gives
text → data
tools
12 reads8 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 20 tools
20 never probed 0 of 20 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • getBalance reads unknown 14h ago

    Merchant app balance per asset (available + onhold).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_docs reads unknown 6h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "topic"
  ],
  "properties": {
    "topic": {
      "type": "string",
      "description": "quickstart | invoices | subscriptions | transfers-checks | webhooks | errors"
    }
  }
}
    arguments 12 lines
  • getTransfers reads unknown never probed

    List app→user transfers.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "asset": {
      "type": "string",
      "description": "Filter by asset code."
    },
    "count": {
      "type": "integer",
      "description": "Page size (default 100)."
    },
    "offset": {
      "type": "integer",
      "description": "Skip this many."
    },
    "spend_id": {
      "type": "string",
      "description": "Filter by idempotency key."
    },
    "transfer_ids": {
      "type": "string",
      "description": "Comma-separated ids."
    }
  }
}
    arguments 25 lines
  • createInvoice changes data unknown never probed

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

    mcp-tool

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

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "subscription_id"
  ],
  "properties": {
    "subscription_id": {
      "type": "integer",
      "description": "The subscription."
    }
  }
}
    arguments 12 lines
  • updateApp changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "New app name (1-64)."
    },
    "webhook_url": {
      "type": "string",
      "description": "https URL for webhook delivery; \"\" clears it."
    },
    "webhook_events": {
      "type": "array",
      "items": {
        "type": "string",
        "description": "Event type."
      },
      "description": "Extended event types to opt into (invoice_paid is always delivered); [] = invoice_paid-only."
    }
  }
}
    arguments 21 lines
  • getStats reads unknown 25h ago

    App volume/count stats for a period.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "end_at": {
      "type": "string",
      "description": "ISO 8601 period end."
    },
    "start_at": {
      "type": "string",
      "description": "ISO 8601 period start."
    }
  }
}
    arguments 13 lines
  • archiveSubscriptionPlan changes data unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "plan_id"
  ],
  "properties": {
    "plan_id": {
      "type": "integer",
      "description": "The plan to archive."
    }
  }
}
    arguments 12 lines
  • connect_status reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "poll_secret"
  ],
  "properties": {
    "poll_secret": {
      "type": "string",
      "description": "The poll_secret from the connect tool."
    }
  }
}
    arguments 12 lines
  • getInvoices reads unknown 10h ago

    List invoices (newest first).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "fiat": {
      "type": "string",
      "description": "Filter by fiat code."
    },
    "asset": {
      "type": "string",
      "description": "Filter by asset code."
    },
    "count": {
      "type": "integer",
      "description": "Page size (default 100)."
    },
    "offset": {
      "type": "integer",
      "description": "Skip this many."
    },
    "status": {
      "type": "string",
      "description": "active | paid | expired."
    },
    "invoice_ids": {
      "type": "string",
      "description": "Comma-separated ids."
    }
  }
}
    arguments 29 lines
  • deleteInvoice changes data unknown never probed

    Delete an unpaid invoice.

    mcp-tool

    {
  "type": "object",
  "required": [
    "invoice_id"
  ],
  "properties": {
    "invoice_id": {
      "type": "integer",
      "description": "The invoice to delete."
    }
  }
}
    arguments 12 lines
  • deleteCheck changes data unknown never probed

    Delete an unclaimed check (refunds the hold).

    mcp-tool

    {
  "type": "object",
  "required": [
    "check_id"
  ],
  "properties": {
    "check_id": {
      "type": "integer",
      "description": "The check to delete."
    }
  }
}
    arguments 12 lines
  • createSubscriptionPlan changes data unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "asset",
    "amount",
    "period_days"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Plan name shown to payers (≤64)."
    },
    "asset": {
      "type": "string",
      "description": "Asset code, e.g. USDT."
    },
    "amount": {
      "type": "string",
      "description": "Decimal string in MAJOR units, e.g. \"5\" = 5 USDT. Never a float. Charged per period."
    },
    "period_days": {
      "type": "integer",
      "description": "Billing period in days."
    }
  }
}
    arguments 27 lines
  • getChecks reads unknown 14h ago

    List checks.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "asset": {
      "type": "string",
      "description": "Filter by asset code."
    },
    "count": {
      "type": "integer",
      "description": "Page size (default 100)."
    },
    "offset": {
      "type": "integer",
      "description": "Skip this many."
    },
    "status": {
      "type": "string",
      "description": "active | activated | expired."
    },
    "check_ids": {
      "type": "string",
      "description": "Comma-separated ids."
    }
  }
}
    arguments 25 lines
  • getExchangeRates reads unknown 10h ago

    Current asset↔fiat display rates.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • getMe reads unknown 10h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • getSubscriptionPlans reads unknown 25h ago

    List subscription plans.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • getCurrencies reads unknown 14h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • connect changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "app_name"
  ],
  "properties": {
    "app_name": {
      "type": "string",
      "description": "Merchant app name shown to the approving human, 1-64 chars (e.g. the project/bot name)."
    }
  }
}
    arguments 12 lines
  • getSubscriptions reads unknown 25h ago

    List subscriptions (subscribers).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "active | grace | cancelled | expired."
    },
    "plan_id": {
      "type": "integer",
      "description": "Filter by plan."
    },
    "user_id": {
      "type": "integer",
      "description": "Filter by Telegram user id."
    }
  }
}
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3f398ef28bc346ea.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3f398ef28bc346ea/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3f398ef28bc346ea/badge.svg)](https://brick.blue/agent/3f398ef28bc346ea?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.