upbank-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Check that the configured Up API token is valid and the API is reachable. |
| list_accountsB | List the customer's Up accounts with their current balances. |
| get_accountC | Retrieve a single account by id. |
| list_transactionsA | List transactions, newest first, optionally filtered by account, status, date range, category or tag. |
| get_transactionB | Retrieve a single transaction by id, including hold, round-up and cashback detail. |
| list_categoriesA | List the category tree. Categories are fixed by Up, not user-defined. |
| get_categoryB | Retrieve a single category by id. |
| categorize_transactionA | Set or clear a transaction's category. Only transactions with |
| list_tagsB | List all tags the customer has created. A tag's id is its label. |
| add_tags_to_transactionC | Add one or more tags to a transaction. |
| remove_tags_from_transactionC | Remove one or more tags from a transaction. |
| list_attachmentsB | List transaction attachments. File URLs are signed and expire shortly. |
| get_attachmentB | Retrieve a single attachment by id. |
| list_webhooksC | List configured webhooks. |
| get_webhookC | Retrieve a single webhook by id. |
| create_webhookA | Register a webhook for transaction events. The response contains |
| delete_webhookB | Permanently delete a webhook. This cannot be undone. |
| ping_webhookA | Send a test PING event to a webhook to verify it is reachable. |
| list_webhook_logsA | List recent delivery attempts for a webhook, to debug failing deliveries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| accounts_resource | A snapshot of every Up account and its current balance. |
| categories_resource | The full Up category tree, for resolving category filter values. |
TDQS
Scored across 19 tools
Each tool targets a distinct resource and action (accounts, transactions, categories, tags, attachments, webhooks), with clear separation between list/get/create/delete/add/remove/ping operations. Overlap is minimal and descriptions explicitly differentiate ambiguous pairs like ping vs ping_webhook.
Nearly all tools follow a consistent snake_case verb_noun pattern (list_accounts, get_transaction, create_webhook, add_tags_to_transaction). The sole minor deviation is 'ping', which lacks a noun but remains unambiguous and predictable.
19 tools across six resource groups is slightly above the typical 3–15 sweet spot, but each tool maps to a distinct, necessary operation for a banking API. No tool appears redundant or trivially thin.
Coverage is broad: full webhook lifecycle plus ping/logs, transaction list/get/categorize, tag add/remove/list, and read operations for accounts, categories, and attachments. Minor gaps exist, notably no attachment upload/delete, but core workflows are otherwise well-covered.