# Zaptu (remote · api.zaptu.ai)

Connect people with independent local home-service contractors. For plumbing, the person dials.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.zaptu.ai`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ai-zaptu-zaptu/api.md), [page](https://verifymcp.io/servers/ai-zaptu-zaptu/api)

## Channel facts

- Endpoint: `https://api.zaptu.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 777 tokens (~194/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 64/100
  - Stability check failed: schema churn in the 26 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Zaptu MCP server?

Zaptu is a hosted endpoint at https://api.zaptu.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-zaptu-zaptu 'https://api.zaptu.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-zaptu-zaptu": {
      "url": "https://api.zaptu.ai/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.ai-zaptu-zaptu]
url = "https://api.zaptu.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-zaptu-zaptu": {
      "type": "remote",
      "url": "https://api.zaptu.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-zaptu-zaptu --url 'https://api.zaptu.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-zaptu-zaptu:
    url: "https://api.zaptu.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-zaptu-zaptu": {
      "Transport": "http",
      "Url": "https://api.zaptu.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-zaptu-zaptu -t streamable-http -u 'https://api.zaptu.ai/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 54 to 58.

### 2026-11-01 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 48 to 51.

### 2026-10-30 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 41 to 44.

### 2026-10-28 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.

### 2026-10-27 (score 71, −3)

- [security regression] Stability: 0.53 → fail
- [security regression] A breaking change shipped without a version bump: still 0.2.0
- [security regression] Tool “get_plumbing_call_number” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “list_supported_services” rewrote its description, which is the text the model reads
- [security] Tool “request_cleaning” rewrote its description, which is the text the model reads
- [security] Tool “request_home_service” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 1052 → 777
- [cosmetic] “request_home_service” reworded the description of “consent_to_contact”
- [cosmetic] “request_home_service” reworded the description of “service_type”

### 2026-10-25 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `request_home_service` (~347 tokens)

Request a home service

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

Every service, plumbing included, works the same way: the request is passed along
when a participating provider covers the ZIP code, so do not promise a callback.
Requires name, phone, ZIP, and the person's explicit consent. Tell the person details
may be shared with Polyares and its service-provider partners, and Polyares, those
partners, or Zaptu may call or text about this request. Never place a call for them.

Input parameters:

- `address_line`
- `bathrooms`
- `bedrooms`
- `city`
- `consent_to_contact` (boolean, required): Must be true: the person agreed that details may be shared with Polyares and its service-provider partners, and that Polyares, those partners, or Zaptu may call or text about this request.
- `customer_email`
- `customer_name` (string, required): Customer's full name.
- `customer_phone` (string, required): US phone number for follow-up contact about this request.
- `dry_run` (boolean): Validate only; nothing is saved or passed along.
- `flexible_dates` (boolean)
- `frequency` (string)
- `home_type`
- `notes`: What the person needs, in their words.
- `preferred_date`: Preferred date as YYYY-MM-DD, if any.
- `service_type` (string, required): Type of local service requested.
- `source_agent`: Your agent or product name.
- `square_feet`
- `state`: 2-letter US state code.
- `zip_code` (string, required): US 5-digit ZIP for the job site.

Output parameters:

- `result` (string)

### `request_cleaning` (~189 tokens)

Request house cleaning

Shortcut for residential house cleaning (collecting; not a booking). Same pipeline as request_home_service. Consent means details may be shared with Polyares and its service-provider partners for this request.

Input parameters:

- `bathrooms`
- `bedrooms`
- `city`
- `consent_to_contact` (boolean, required): Must be true: the person agreed that details may be shared with Polyares and its service-provider partners, and that Polyares, those partners, or Zaptu may call or text about this request.
- `customer_email`
- `customer_name` (string, required): Customer's full name.
- `customer_phone` (string, required): US phone number.
- `frequency` (string)
- `notes`
- `preferred_date`
- `square_feet`
- `state`
- `zip_code` (string, required): US 5-digit ZIP for the home.

Output parameters:

- `result` (string)

### `get_lead_status` (~35 tokens)

Check lead status

Look up a previously submitted service request by lead_id.

Input parameters:

- `lead_id` (string, required): ID returned by request_home_service.

Output parameters:

- `result` (string)

### `list_supported_services` (~24 tokens)

List supported services

Which services Zaptu accepts requests for, plus the rules for agents.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-zaptu-zaptu/api#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 74
- 2026-10-25: 74
- 2026-10-24: 73
- 2026-10-23: 73
- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 71
- 2026-10-19: 71
- 2026-10-18: 71
- 2026-10-17: 70
- 2026-10-16: 70
- 2026-10-15: 69
- 2026-10-14: 69
- 2026-10-13: 68
- 2026-10-12: 68
- 2026-10-10: 67

## Common questions

### What is the Zaptu MCP server?

Zaptu is an MCP server listed in the public MCP registry as ai.zaptu/zaptu. Connect people with independent local home-service contractors. For plumbing, the person dials. This page covers its hosted endpoint (https://api.zaptu.ai/mcp).

### Is the Zaptu MCP server safe to use?

Zaptu scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Zaptu MCP server expose?

Zaptu exposes 4 tools: request_home_service, request_cleaning, get_lead_status, list_supported_services. Their descriptions and schemas cost roughly 595 tokens of context every time the server is loaded.

### Does the Zaptu MCP server require authentication?

No. We connected to Zaptu without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zaptu MCP server still maintained?

Zaptu is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.zaptu.ai/mcp
- Website: https://zaptu.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-zaptu-zaptu/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-zaptu-zaptu/api.json
- HTML version of this page: https://verifymcp.io/servers/ai-zaptu-zaptu/api