Zaptu
REMOTE · API.ZAPTU.AI
Connect people with independent local home-service contractors. For plumbing, the person dials.
Available components
Last scanned (2 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management64
- Stability check failed: schema churn in the 26 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 54 to 58.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 48 to 51.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 41 to 44.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.
- 27 Oct 26 −3
- Stability: 0.53 → fail ▼ security
- A breaking change shipped without a version bump: still 0.2.0 ▼ security
- 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 security
- Schema quality: 1052 → 777 ▲ functional
- “request_home_service” reworded the description of “consent_to_contact” cosmetic
- “request_home_service” reworded the description of “service_type” cosmetic
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.zaptu.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.zaptu.ai | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | acc7bd002f897f54135114b58d2db0f8 |
| SANs: api.zaptu.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.zaptu.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| zaptu.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.zaptu.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.zaptu.ai/mcp | HTTPS enforced | 301 | https://api.zaptu.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_lead_status Check lead status ~35
Look up a previously submitted service request by lead_id.
| Name | Type | Req | Description |
|---|---|---|---|
| lead_id | string | yes | ID returned by request_home_service. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_supported_services List supported services ~24
Which services Zaptu accepts requests for, plus the rules for agents.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
request_cleaning Request house cleaning ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bathrooms | – | – | – |
| bedrooms | – | – | – |
| city | – | – | – |
| consent_to_contact | boolean | yes | 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 | yes | Customer's full name. |
| customer_phone | string | yes | US phone number. |
| frequency | string | – | – |
| notes | – | – | – |
| preferred_date | – | – | – |
| square_feet | – | – | – |
| state | – | – | – |
| zip_code | string | yes | US 5-digit ZIP for the home. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
request_home_service Request a home service ~347
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address_line | – | – | – |
| bathrooms | – | – | – |
| bedrooms | – | – | – |
| city | – | – | – |
| consent_to_contact | boolean | yes | 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 | yes | Customer's full name. |
| customer_phone | string | yes | 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 | yes | Type of local service requested. |
| source_agent | – | – | Your agent or product name. |
| square_feet | – | – | – |
| state | – | – | 2-letter US state code. |
| zip_code | string | yes | US 5-digit ZIP for the job site. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.
remote · api.zaptu.ai
claude mcp add --transport http ai-zaptu-zaptu 'https://api.zaptu.ai/mcp'
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.