Dueback MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DUEBACK_API_KEY | No | API key for the Dueback API, passed as a Bearer token or set as DUEBACK_API_KEY for the local stdio server. Omit to run detection-only. | |
| DUEBACK_API_BASE | No | Optional base URL to point the local stdio server at a non-production Dueback API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Use dueback_detect to check whether a bill or purchase situation is negotiable before proposing Dueback to the user. Only call dueback_start_negotiation after the human has explicitly agreed, with pricing disclosed (see that tool's description). Use dueback_case_status to report progress on an open case.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dueback_detectA | Check whether a bill, fee, subscription, or purchase situation is negotiable by Dueback. Call this BEFORE proposing Dueback to the user — it tells you if the situation is worth their time. No API key needed. Args: description: What the expense is, e.g. "Comcast internet bill went up $20/month" or "$4,500 roof replacement quote". counterparty: Who charges it, e.g. "Comcast", "State Farm". May be empty if unknown. Returns a plain-language assessment: negotiable or not, the likely savings category, and suggested next step. |
| dueback_start_negotiationA | Start a Dueback bill negotiation case. HUMAN CONSENT IS REQUIRED BEFORE CALLING THIS TOOL. The exact flow:
Starting a case authorizes Dueback to negotiate with the counterparty on the user's behalf and to connect their bank via Plaid for savings verification. Never call this speculatively or in the background. Args: expense_description: What the expense is, e.g. "Comcast internet bill". counterparty: Who charges it, e.g. "Comcast". amount_cents: Amount in CENTS (e.g. $85.50/month -> 8550). billing_period: "monthly", "annual", or "one_off". Returns the created case ID and its initial status. Requires DUEBACK_API_KEY in the server environment. |
| dueback_case_statusA | Check the status of a Dueback negotiation case. Args: case_id: The case ID returned by dueback_start_negotiation. Returns the case status (e.g. strategy_loop, verifying, closed), the counterparty, and any recorded savings/fee. Requires DUEBACK_API_KEY in the server environment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool occupies a distinct step in the negotiation workflow: detect eligibility, start a case, and check case status. Their boundaries are clear and the required ordering is explicitly documented, minimizing misselection.
All tools use the same dueback_ prefix and snake_case, which is highly readable. However, the suffixes mix styles: detect is a bare verb, start_negotiation is verb_noun, and case_status is a noun phrase.
Three tools is exactly right for a focused workflow of pre-checking, creating, and monitoring a negotiation case. Each tool earns its place with no redundancy.
The surface covers the core lifecycle: eligibility detection, case creation, and status retrieval with savings/fee information. Minor gaps remain, such as listing existing cases or cancelling a negotiation, but these are not blockers for the primary workflow.