# io.usefulapi/housecall-pro (remote · housecall-pro.usefulapi.io)

Manage Housecall Pro customers, jobs, estimates and leads; schedule and dispatch jobs.

- Trust score: 33/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `housecall-pro.usefulapi.io`: 33/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-housecall-pro/housecall-pro.md), [page](https://verifymcp.io/servers/io-usefulapi-housecall-pro/housecall-pro)

## Channel facts

- Endpoint: `https://housecall-pro.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
  - 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**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the io.usefulapi/housecall-pro MCP server?

io.usefulapi/housecall-pro is a hosted endpoint at https://housecall-pro.usefulapi.io/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 io-usefulapi-housecall-pro 'https://housecall-pro.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-housecall-pro": {
      "url": "https://housecall-pro.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-housecall-pro": {
      "type": "http",
      "url": "https://housecall-pro.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-housecall-pro]
url = "https://housecall-pro.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-housecall-pro": {
      "type": "remote",
      "url": "https://housecall-pro.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-housecall-pro --url 'https://housecall-pro.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-housecall-pro:
    url: "https://housecall-pro.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-housecall-pro": {
      "Transport": "http",
      "Url": "https://housecall-pro.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-housecall-pro -t streamable-http -u 'https://housecall-pro.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-housecall-pro": {
      "type": "http",
      "url": "https://housecall-pro.usefulapi.io/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-10-04 (score 33, −43)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.10 → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-03 (score 76, +43)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.10
- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-02 (score 33, −39)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: fail → unverified
- [security regression] Stability: 0.03 → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-01 (score 72, +3)

- [security regression] Authorization: pass → fail
- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 69, +51)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 77
- [functional] First check of Schema quality: good

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (25)

### `housecall_get_company` (~60 tokens)

Get the company

Fetch the Housecall Pro company this key belongs to — name, contact details, address, time zone, service-area zip codes and (multi-location) its locations. A cheap way to confirm the key works. Housecall Pro: GET /company.

### `housecall_list_customers` (~157 tokens)

List customers

List or search customers, with their phone numbers, tags and addresses. `q` searches name, email, mobile number and address. Housecall Pro: GET /customers.

Input parameters:

- `expand` (array): Extras to include in each customer.
- `location_ids` (array): Multi-location accounts: only these location ids (ignored when HOUSECALL_PRO_COMPANY_ID is set).
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Records per page.
- `q` (string): Search by name, email, mobile number or address.
- `sort_by` (string): Customer attribute to sort by, e.g. created_at.
- `sort_direction` (string): Sort direction.

### `housecall_get_customer` (~64 tokens)

Get one customer

Fetch a single customer by id, including their addresses (whose ids you need to create a job or estimate). Housecall Pro: GET /customers/{customer_id}.

Input parameters:

- `customer_id` (string, required): The customer id.
- `expand` (array): Extras to include.

### `housecall_list_jobs` (~340 tokens)

List jobs

List jobs, filterable by scheduled window, customer, assigned employees and work status. Each job carries its customer, address, notes, schedule, assigned employees and totals. Housecall Pro: GET /jobs.

Input parameters:

- `customer_id` (string): Only this customer's jobs.
- `employee_ids` (array): Only records assigned to these employee ids.
- `expand` (array): Extras to include.
- `location_ids` (array): Multi-location accounts: only these location ids (ignored when HOUSECALL_PRO_COMPANY_ID is set).
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Records per page.
- `scheduled_end_max` (string): Only jobs ending at or before this time (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `scheduled_end_min` (string): Only jobs ending at or after this time (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `scheduled_start_max` (string): Only jobs starting at or before this time (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `scheduled_start_min` (string): Only jobs starting at or after this time (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `sort_by` (string): Attribute to sort by.
- `sort_direction` (string): Sort direction.
- `work_status` (array): Only these work statuses. All statuses if omitted.

### `housecall_get_job` (~66 tokens)

Get one job

Fetch a single job by id — customer, address, work status and timestamps, schedule, assigned employees, notes and totals. Housecall Pro: GET /jobs/{id}.

Input parameters:

- `expand` (array): Extras to include.
- `job_id` (string, required): The job id.

### `housecall_list_job_line_items` (~66 tokens)

List a job's line items

List the line items (services, materials, labor, discounts) on one job, with unit price, cost, quantity and amount in cents. Housecall Pro: GET /jobs/{job_id}/line_items.

Input parameters:

- `job_id` (string, required): The job id.

### `housecall_list_job_invoices` (~63 tokens)

List a job's invoices

List the invoices raised for one job, with status, amounts, due and paid dates, items, taxes, discounts and payments. Housecall Pro: GET /jobs/{job_id}/invoices.

Input parameters:

- `job_id` (string, required): The job id.

### `housecall_list_invoices` (~369 tokens)

List invoices

List invoices across the company, filterable by status, customer, and created / due / paid date ranges — e.g. everything open and overdue. Amounts are in cents. Housecall Pro: GET /invoices.

Input parameters:

- `created_at_max` (string): Created at or before (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `created_at_min` (string): Created at or after (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `customer_uuid` (array): Only these customers' invoices.
- `due_at_max` (string): Due at or before (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `due_at_min` (string): Due at or after (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `location_ids` (array): Multi-location accounts: only these location ids (ignored when HOUSECALL_PRO_COMPANY_ID is set).
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Records per page.
- `paid_at_max` (string): Paid at or before (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `paid_at_min` (string): Paid at or after (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `sort_by` (string): Attribute to sort by.
- `sort_direction` (string): Sort direction.
- `status` (array): Only these statuses.

### `housecall_list_estimates` (~326 tokens)

List estimates

List estimates, filterable by scheduled window, customer, assigned employees and work status. Each carries its customer, address, schedule and options. Housecall Pro: GET /estimates.

Input parameters:

- `customer_id` (string): Only this customer's estimates.
- `employee_ids` (array): Only records assigned to these employee ids.
- `location_ids` (array): Multi-location accounts: only these location ids (ignored when HOUSECALL_PRO_COMPANY_ID is set).
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Records per page.
- `scheduled_end_max` (string): Only estimates ending at or before this time (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `scheduled_end_min` (string): Only estimates ending at or after this time (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `scheduled_start_max` (string): Only estimates starting at or before this time (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `scheduled_start_min` (string): Only estimates starting at or after this time (ISO-8601, e.g. 2026-03-23T15:30:00Z).
- `sort_by` (string): Attribute to sort by.
- `sort_direction` (string): Sort direction.
- `work_status` (array): Only these work statuses. All statuses if omitted.

### `housecall_get_estimate` (~51 tokens)

Get one estimate

Fetch a single estimate by id, including its options and each option's approval status. Housecall Pro: GET /estimates/{estimate_id}.

Input parameters:

- `estimate_id` (string, required): The estimate id.

### `housecall_list_employees` (~117 tokens)

List employees

List the company's active employees with their role, contact details and permissions. Use their ids to assign or dispatch jobs. Housecall Pro: GET /employees.

Input parameters:

- `location_ids` (array): Multi-location accounts: only these location ids (ignored when HOUSECALL_PRO_COMPANY_ID is set).
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Records per page.
- `sort_by` (string): Employee attribute to sort by.
- `sort_direction` (string): Sort direction.

### `housecall_list_leads` (~185 tokens)

List leads

List leads, filterable by status (open / won / lost), customer, assigned employees, tags and lead source. Housecall Pro: GET /leads.

Input parameters:

- `customer_id` (string): Only this customer's leads.
- `employee_ids` (array): Only records assigned to these employee ids.
- `lead_source` (array): Only leads from these lead sources.
- `location_ids` (array): Multi-location accounts: only these location ids (ignored when HOUSECALL_PRO_COMPANY_ID is set).
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Records per page.
- `sort_by` (string): Attribute to sort by.
- `sort_direction` (string): Sort direction.
- `status` (string): Only leads in this status.
- `tag_ids` (array): Only leads with these tag ids.

### `housecall_get_lead` (~58 tokens)

Get one lead

Fetch a single lead by id — its customer, address, lead source, tags, assigned employee, status and pipeline status. Housecall Pro: GET /leads/{id}.

Input parameters:

- `lead_id` (string, required): The lead id.

### `housecall_list_job_types` (~63 tokens)

List job types

List the company's job types (e.g. Repair, Install, Maintenance). Use an id as job_type_id when creating a job or estimate. Housecall Pro: GET /job_fields/job_types.

Input parameters:

- `name` (string): Filter job types by name.

### `housecall_list_tags` (~73 tokens)

List tags

List the tags defined in the company. Housecall Pro: GET /tags.

Input parameters:

- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Records per page.
- `sort_by` (string): Attribute to sort by.
- `sort_direction` (string): Sort direction.

### `housecall_list_price_book_services` (~138 tokens)

List price book services

List or search the price book's services — name, task number, price and cost (cents), taxable and online-booking flags; optionally with their materials and labor rates. Housecall Pro: GET /api/price_book/services.

Input parameters:

- `expand` (array): Populate these nested lists (empty by default).
- `page` (integer): Page number, starting at 1.
- `page_size` (integer): Records per page.
- `q` (string): Search by name, description or task number.
- `sort_by` (string): Service attribute to sort by.
- `sort_direction` (string): Sort direction.

### `housecall_create_customer` (~138 tokens)

Create a customer

Create a new customer, optionally with one or more addresses. Housecall Pro: POST /customers.

Input parameters:

- `addresses` (array): Addresses to create with the customer.
- `company` (string): The customer's company name.
- `email` (string)
- `first_name` (string)
- `home_number` (string)
- `last_name` (string)
- `lead_source` (string)
- `mobile_number` (string)
- `notes` (string)
- `notifications_enabled` (boolean): Whether the customer receives notifications.
- `tags` (array): Tag names.
- `work_number` (string)

### `housecall_update_customer` (~153 tokens)

Update a customer

Change a customer's name, contact details, tags, lead source, notes or notification setting. Only the fields you pass are sent. Housecall Pro: PUT /customers/{customer_id}.

Input parameters:

- `company` (string): The customer's company name.
- `customer_id` (string, required): The customer id.
- `email` (string)
- `first_name` (string)
- `home_number` (string)
- `last_name` (string)
- `lead_source` (string)
- `mobile_number` (string)
- `notes` (string)
- `notifications_enabled` (boolean): Whether the customer receives notifications.
- `tags` (array): Tag names.
- `work_number` (string)

### `housecall_create_customer_address` (~108 tokens)

Add an address to a customer

Add a service address to an existing customer. Returns the address id to use when creating a job or estimate. Housecall Pro: POST /customers/{customer_id}/addresses.

Input parameters:

- `city` (string, required)
- `country` (string, required): Country, e.g. US.
- `customer_id` (string, required): The customer id.
- `state` (string, required)
- `street` (string, required)
- `street_line_2` (string)
- `zip` (string, required)

### `housecall_create_job` (~175 tokens)

Create a job

Create a job for an existing customer at one of their existing addresses, optionally scheduled, assigned, tagged and with line items (prices in cents). Get address ids from housecall_get_customer. Housecall Pro: POST /jobs.

Input parameters:

- `address_id` (string, required): The customer address id.
- `assigned_employee_ids` (array): Employees to assign.
- `business_unit_id` (string)
- `customer_id` (string, required): The customer id.
- `invoice_number` (integer): Must be unique across the company's jobs; auto-assigned if omitted.
- `job_type_id` (string): From housecall_list_job_types.
- `lead_source` (string)
- `line_items` (array)
- `notes` (string)
- `schedule` (object)
- `tags` (array): Tag names.

### `housecall_update_job_schedule` (~161 tokens)

Reschedule a job

Set or change a job's scheduled start/end and arrival window, optionally dispatching employees and notifying the customer and/or the pro. Jobs with more than one appointment (multi-day) cannot be rescheduled here. Housecall Pro: PUT /jobs/{job_id}/schedule.

Input parameters:

- `arrival_window_in_minutes` (integer): Arrival window in minutes.
- `dispatched_employee_ids` (array): Employees to dispatch to the job.
- `end_time` (string): ISO-8601 end time.
- `job_id` (string, required): The job id.
- `notify` (boolean): Notify the customer of the new schedule.
- `notify_pro` (boolean): Notify the assigned employee(s).
- `start_time` (string, required): ISO-8601 start time.

### `housecall_dispatch_job` (~75 tokens)

Dispatch a job to employees

Set which employees a job is dispatched to. This REPLACES the current dispatch list — pass everyone who should be on the job. Housecall Pro: PUT /jobs/{job_id}/dispatch.

Input parameters:

- `employee_ids` (array, required): Every employee who should be dispatched.
- `job_id` (string, required): The job id.

### `housecall_add_job_note` (~53 tokens)

Add a note to a job

Add a text note to a job. Housecall Pro: POST /jobs/{job_id}/notes.

Input parameters:

- `content` (string, required): The note text.
- `job_id` (string, required): The job id.

### `housecall_create_estimate` (~203 tokens)

Create an estimate

Create an estimate for a customer with one or more options (e.g. Good / Better / Best), each with line items priced in cents. Give an existing address_id or a new address. Housecall Pro: POST /estimates.

Input parameters:

- `address` (object): A new address, if no address_id.
- `address_id` (string): An existing address of the customer.
- `assigned_employee_ids` (array)
- `business_unit_id` (string)
- `customer_id` (string, required): The customer id.
- `estimate_number` (integer): Must be unique across the company's estimates; auto-assigned if omitted.
- `job_type_id` (string): From housecall_list_job_types.
- `lead_source` (string)
- `message` (string): Message to the customer.
- `note` (string)
- `options` (array): The estimate's options.
- `schedule` (object): When the estimate visit is scheduled.

### `housecall_create_lead` (~171 tokens)

Create a lead

Create a lead, either for an existing customer (customer_id) or with a new customer inline (customer). Optionally with an address, lead source, assigned employee, tags, note and line items priced in cents. Housecall Pro: POST /leads.

Input parameters:

- `address` (object): A new address, if no address_id.
- `address_id` (string): An existing address of the customer.
- `assigned_employee_id` (string)
- `customer` (object): A new customer to create with the lead. Give this or `customer_id`.
- `customer_id` (string): An existing customer. Give this or `customer`.
- `lead_source` (string)
- `line_items` (array)
- `note` (string)
- `tags` (array)

## Diagnostics

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

## Score history

- 2026-10-04: 33
- 2026-10-03: 76
- 2026-10-02: 33
- 2026-10-01: 72
- 2026-09-30: 69
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/housecall-pro MCP server?

io.usefulapi/housecall-pro is an MCP server listed in the public MCP registry as io.usefulapi/housecall-pro. Manage Housecall Pro customers, jobs, estimates and leads; schedule and dispatch jobs. This page covers its hosted endpoint (https://housecall-pro.usefulapi.io/mcp).

### Is the io.usefulapi/housecall-pro MCP server safe to use?

io.usefulapi/housecall-pro scores 33 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 io.usefulapi/housecall-pro MCP server expose?

io.usefulapi/housecall-pro exposes 25 tools: housecall_get_company, housecall_list_customers, housecall_get_customer, housecall_list_jobs, housecall_get_job, and 20 more. Their descriptions and schemas cost roughly 3,433 tokens of context every time the server is loaded.

### Does the io.usefulapi/housecall-pro MCP server require authentication?

No. We connected to io.usefulapi/housecall-pro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.usefulapi/housecall-pro MCP server still maintained?

io.usefulapi/housecall-pro is still listed as active in the MCP registry. We last reached this channel on 4 October 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://housecall-pro.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-housecall-pro/housecall-pro.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-housecall-pro/housecall-pro.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-housecall-pro/housecall-pro