Productivity

splitbill.one

Create and manage shared bill-splitting sessions with QR codes and real-time tracking of who owes what.

1 endpoint2 known toolsFirst detected August 13, 2026Last detected August 13, 2026

ENDPOINT 1

https://api.splitbill.one/mcp

No auth detected

Capabilities

tools.listChanged

Create a shareable SplitBill session from receipt items and return a QR code plus join link.

Potential side effects

Check who has claimed which items on a SplitBill bill and what each person owes.

Inferred read-only

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.splitbill]
url = "https://api.splitbill.one/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "splitbill": {
      "type": "http",
      "url": "https://api.splitbill.one/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: splitbill
Remote MCP URL: https://api.splitbill.one/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": {
    "splitbill": {
      "url": "https://api.splitbill.one/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "splitbill": {
      "type": "http",
      "url": "https://api.splitbill.one/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "splitbill",
  "transport": "streamable-http",
  "url": "https://api.splitbill.one/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

BuiltWith Trust API v2 evidence for splitbill.one was fetched 2026-08-23T11:09:49.478Z and is being refreshed.

Trust status Neutral

splitbill.one is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.