Productivity
dueback.co
An MCP server that helps detect negotiable bills, open and track Dueback negotiation cases, and report verified savings.
ENDPOINT 1
https://api.dueback.co/mcp
MCP server metadata
- Name
- dueback
Dueback negotiates bills and recovers overcharges on behalf of the user, charging only a share of verified savings. Workflow: call detect_negotiable_bill with the bill facts and show the returned pitch to the human. Only if they approve, call start_negotiation_case. If it returns setup_required, show the human the setup_url link so they can finish securely on Dueback's page — the case opens when they complete it. Poll get_case_status for progress; when a case needs approval, surface the findings to the human and wait. Never invent savings figures. Internal playbooks are never exposed.
Known tools 4
get_case_statusGet the current status of a negotiation case: state, steps taken, savings found, and whether human approval is needed.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.dueback]
url = "https://api.dueback.co/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dueback": {
"type": "http",
"url": "https://api.dueback.co/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dueback
Remote MCP URL: https://api.dueback.co/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"dueback": {
"url": "https://api.dueback.co/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dueback": {
"type": "http",
"url": "https://api.dueback.co/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dueback",
"transport": "streamable-http",
"url": "https://api.dueback.co/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.