Marketing

zaptu.ai

An MCP server for submitting and tracking home-service lead requests, including plumbing call routing and residential cleaning inquiries.

1 endpoint5 known toolsFirst detected October 9, 2026Last detected October 9, 2026

ENDPOINT 1

https://api.zaptu.ai/mcp

No auth detected

MCP server metadata

Name: zaptu
Version: 0.2.0

Capabilities

promptsresourcestools

Server instructions

Zaptu connects people with independent local home-service contractors. Zaptu does not perform the work and does not book appointments. PLUMBING (live): call get_plumbing_call_number. Tell the person, for example: "Call (308) 529-9543 to be connected with a local plumbing professional." The person must dial it themselves. Never dial, autodial, transfer, or place the call for them. No name, phone, or consent is needed for this. EVERYTHING ELSE (collecting: cleaning, pest control, HVAC, handyman, other): collect ZIP, name, phone, and the person's explicit consent to be contacted, then call request_home_service. These requests are passed along when a buyer covers the service; there is no live buyer yet. Do not promise a callback, an arrival time, or a named company. Use the tool result's message when you tell the person what happened. list_supported_services returns the full catalog.

Known tools 5

get_plumbing_call_number

Get the phone number a person dials to be connected with a local plumbing professional.

Inferred read-only

request_home_service

Submit a home-service request (a lead, not a booking).

Inferred read-only

request_cleaning

Shortcut for residential house cleaning (collecting; not a booking).

Inferred read-only

get_lead_status

Look up a previously submitted service request by lead_id.

Inferred read-only

list_supported_services

Which services are live (plumbing: the person dials a number) vs collecting, plus the rules for agents.

Inferred read-only

CONNECT 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.zaptu]
url = "https://api.zaptu.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "zaptu": {
      "type": "http",
      "url": "https://api.zaptu.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "zaptu": {
      "type": "http",
      "url": "https://api.zaptu.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "zaptu",
  "transport": "streamable-http",
  "url": "https://api.zaptu.ai/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.

Indexed

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