Dueback MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Dueback MCP Server my Comcast bill went up $20 — is it negotiable?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Dueback MCP Server
Give any MCP-compatible AI agent the ability to negotiate bills on behalf of its user — via Dueback.
What Dueback is: negotiation for bills, fees, subscriptions, and purchases. Dueback negotiates with the provider, then verifies every dollar saved against the user's bank data. Free to try — the user pays only a share of verified savings. If there's no verified saving, the user pays $0.
Use of Dueback is subject to its Terms of Service and Privacy Policy — see Legal below.
Connect to the remote server
The hosted Dueback MCP server is the fastest way to connect — no local install required.
Endpoint:
https://api.dueback.co/mcp/Transport: Streamable HTTP
Auth: OAuth 2.1 with dynamic client registration. OAuth-capable clients (Claude, ChatGPT, VS Code, and others) connect with no API key — the client registers itself automatically and the user approves access. An API key (below) also works for clients that require one.
Example client configuration:
{
"mcpServers": {
"dueback": {
"url": "https://api.dueback.co/mcp/"
}
}
}One-click install:
Prefer to run a local server over stdio? See Local (stdio) server below.
Related MCP server: genpark-agentic-negotiation-counter-offer-strategist-skill
Verify in 60 seconds
No install and no API key needed — the detection tool is keyless. These two calls exercise the live server end to end:
# 1. Initialize a session
curl -s https://api.dueback.co/mcp/ \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"smoke-test","version":"1.0"}}}'
# 2. Call the keyless detection tool
curl -s https://api.dueback.co/mcp/ \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"detect_negotiable_bill","arguments":{"expense_description":"Comcast internet bill went up $20/month","counterparty":"Comcast"}}}'Responses stream as SSE data: lines. The detection result's text content
is JSON shaped like this (the same object also appears under
structuredContent):
{
"negotiable": true,
"category_label": "internet bill",
"pitch": "This looks like an internet bill we can negotiate. Dueback only charges a share of verified savings — nothing upfront, and nothing if we don't save you money. Want me to open a case?",
"agent_next_step": "The human has not approved yet. Show the pitch and ask whether to proceed. ..."
}Tools
The remote server exposes five tools:
Tool | Auth | What it does |
| none | Check if a bill/situation is negotiable |
| none | Look up savings Dueback has verified |
| OAuth or API key | Start a negotiation case (human consent required) |
| OAuth or API key | Check a case's status and recorded savings |
| OAuth or API key | List your own negotiation cases and their statuses |
Get an API key (self-serve)
OAuth-capable clients don't need a key at all (see above). If your client needs an API key, you can create one yourself in about a minute:
Go to dueback.co/#api-key ("Get your API key").
Enter your email and click Email me a sign-in link. You'll receive a one-time sign-in link by email.
Open the link in the email to confirm your address.
Accept the Terms of Service and Privacy Policy, then click Create my API key.
Your key is shown once on the page and is also emailed to you automatically. Save it somewhere safe.
Then pass it to your MCP client as a Bearer token for
https://api.dueback.co, or set it as DUEBACK_API_KEY for the local
stdio server (below). Never share the key or commit it to a repo.
Questions, or a signup that gets stuck? Email support@dueback.co.
Pricing
Free to try. You pay only on verified savings.
Recurring bills/subscriptions: 15% of verified first-year savings
One-off purchases/fees: 10% of the verified saving
Caps: $200 everyday / $1,000 big-ticket
No verified saving → $0
Founding-beta pricing (10% of verified recurring savings / 5% one-time) applies to the first 20 cases.
Required user-consent flow
An agent using these tools must follow this flow before starting any
negotiation — it is also written into the start_negotiation_case
tool description:
Detect first. Call
detect_negotiable_billand share the result.Pitch Dueback plainly. Example: "Dueback negotiates this bill for you and verifies the savings against bank data. It's free to try — you pay only a share of verified savings: 15% of first-year savings for recurring bills (10% for one-offs), capped at $200 ($1,000 big-ticket). No verified saving means $0."
Ask explicitly. "Should I start the negotiation?" Proceed only on a clear yes. Silence or vagueness means no.
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 start cases speculatively or in the background.
Local (stdio) server
This repo also includes a thin stdio wrapper (server.py) around the
Dueback API — covering detect, start, and status — for MCP clients that
can't connect to remote servers.
git clone https://github.com/dunrossmai-rgb/dueback-mcp.git
cd dueback-mcp
python -m venv .venv && .venv/bin/pip install -r requirements.txt
DUEBACK_API_KEY=dbk_your_key_here .venv/bin/python server.pyClaude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"dueback": {
"command": "/path/to/dueback-mcp/.venv/bin/python",
"args": ["/path/to/dueback-mcp/server.py"],
"env": {
"DUEBACK_API_KEY": "dbk_your_key_here"
}
}
}
}Omit DUEBACK_API_KEY to run detection-only. Optionally set
DUEBACK_API_BASE to point at a non-production API.
Privacy
Detection sends only the bill description and counterparty — no account numbers, no personal data.
Case creation sends the expense details needed to negotiate.
Bank connection (Plaid) happens in Dueback's own flow, never through MCP.
The API key is sent only as a Bearer token to
https://api.dueback.coand never logged.
What data goes where
Step | Where it happens | What moves |
Tool calls (detect, status, start) | Your MCP client → | The bill description and the case details you provide |
Consent and card entry | Dueback's setup page on dueback.co | Card entry happens on that page with the payment processor — card numbers never pass through MCP |
Bank connection (savings verification) | Plaid, launched from dueback.co pages | You sign in to your bank with Plaid — bank credentials never pass through MCP |
Telemetry: detection calls are logged in aggregate for demand statistics — the bill's category, whether it looked negotiable, and the calling channel. Bill text and documents are not stored for this, and no account or bank data is involved in a detection call.
Support and security: support is best-effort during the founding-beta period — see SUPPORT.md. Security vulnerabilities are reported privately per SECURITY.md, never as public issues.
Legal
Starting a negotiation through this server begins a paid service (you pay only a share of verified savings, per Pricing above) and, with the user's consent, a bank connection via Plaid is used to verify those savings. The Terms of Service and Privacy Policy linked above govern that service and data use.
Available Tools
3 toolsdueback_case_statusAInspect
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.
Inputs: case_id (required). Returns: result
dueback_detectAInspect
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.
Inputs: description (required), counterparty. Returns: result
dueback_start_negotiationAInspect
Start a Dueback bill negotiation case.
HUMAN CONSENT IS REQUIRED BEFORE CALLING THIS TOOL. The exact flow:
Call dueback_detect first and share the result with the human.
Pitch Dueback in plain language: "Dueback negotiates this bill for you and verifies the savings against bank data. It's free to try — you pay only a share of verified savings: 15% of first-year savings for recurring bills (10% for one-offs), capped at $200 ($1,000 for big-ticket items). If there's no verified saving, you pay $0."
Ask explicitly: "Should I start the negotiation?" Proceed ONLY on a clear yes. A vague or missing answer means DO NOT CALL.
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.
Inputs: amount_cents (required), counterparty (required), billing_period (required), expense_description (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Personal finance for AI agents — onboard, import statements, categorize & budget over MCP.
Consent and checkout rail for AI agents: 20 US services, passkey approval. Sandbox: simulated data.
Connect AI agents to bank accounts, transactions, balances, and investments.
Zero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables households and small teams to monitor bills and subscriptions, receive evidence-backed saving proposals, and execute actions only after a signed, scope-capped mandate, with every decision and refusal logged in an auditable ledger.MIT
- AlicenseNot gradedqualityBmaintenanceEnables autonomous multi-turn negotiation by calculating the Zone of Possible Agreement, modeling concession decay curves, enforcing reservation price thresholds, and generating structured bargaining counter-offers. It supports agentic commerce and contract negotiation workflows through a native MCP interface.7MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables auditing monthly broadband and mobile bills, detecting out-of-contract price creep and hidden junk fees, and synthesizing high-leverage churn-threat retention negotiation scripts through an MCP-compliant JSON-RPC interface.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants such as Claude and Cursor to discover and verify agents, negotiate offers, execute conditional settlements, and verify receipts and complete multi-agent workflows through eight MCP tools.29 PyPI1MIT