# io.github.hcpapi/housecall-pro-mcp (npm · housecall-pro-mcp)

Independent MCP server for the Housecall Pro API: jobs, estimates, invoices, price book, schedule.

- Trust score: 83/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `housecall-pro-mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/hcpapi-housecall-pro-mcp/housecall-pro-mcp.md), [page](https://verifymcp.io/servers/hcpapi-housecall-pro-mcp/housecall-pro-mcp)

## Channel facts

- Registry: `npm`
- Package: `housecall-pro-mcp`
- Version: `1.18.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 34 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1536 tokens (~256/item across 6 items; 4 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.hcpapi/housecall-pro-mcp server?

io.github.hcpapi/housecall-pro-mcp runs locally as an npm package, launched with npx -y housecall-pro-mcp. 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 hcpapi-housecall-pro-mcp -- npx -y housecall-pro-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "hcpapi-housecall-pro-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "housecall-pro-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hcpapi-housecall-pro-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "housecall-pro-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add hcpapi-housecall-pro-mcp -- npx -y housecall-pro-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hcpapi-housecall-pro-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "housecall-pro-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hcpapi-housecall-pro-mcp --command npx --arg -y --arg housecall-pro-mcp
```

### Hermes

```yaml
mcp_servers:
  hcpapi-housecall-pro-mcp:
    command: "npx"
    args: ["-y", "housecall-pro-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "hcpapi-housecall-pro-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "housecall-pro-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add hcpapi-housecall-pro-mcp -t stdio -c npx -a -y housecall-pro-mcp
```

### Other

```json
{
  "mcpServers": {
    "hcpapi-housecall-pro-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "housecall-pro-mcp"
      ]
    }
  }
}
```

## 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-09-20 (score 83, +1)

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

### 2026-09-18 (score 82, +1)

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

### 2026-09-17 (score 81, −4)

- [functional] Stability: pass → 0.77

### 2026-09-16 (score 85, +1)

- [security] Stability: 0.97 → pass

### 2026-09-14 (score 84, +1)

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

### 2026-09-12 (score 83, +1)

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

### 2026-09-10 (score 82, −3)

- [functional] Stability: pass → 0.80

### 2026-09-09 (score 85, +1)

- [security] Stability: 0.97 → pass

## MCP tools (4)

### `hcp_render_report` (~391 tokens)

Render a findings report into one self-contained, offline, interactive HTML file — sortable and filterable tables, severity-coded sections, collapsible worklists, selectable rows that copy back to chat, light and dark theme, print. This is a presentation tool: it makes no Housecall Pro call and takes findings you already have.

Pass a `report` contract. Required keys: `skill`, `title`, `sections` (an array). Each section has a `title`, an optional `severity` (confident|ok|warning|blocked|info|neutral), and `blocks` (an array). A block is one of: `table` ({columns:[{label,numeric?}], rows:[[cells]], selectable?, collapsedRows?, defaultSort?}), `prose`/`lead` ({html}), `list` ({items,crosses?}), `subhead` ({text}). Optional top-level keys: `kicker`, `stats` (cards), `coverage`, `headline`, `order` (suggested work), `meta`, `generated`, `provenance`, `closing`. In table cells and list items, `` `backticks` `` render as chips, `**stars**` as bold, and `[text](https://...)` as a link opening in a new tab (http/https only) - use it to link records to their pages in the owner's own dashboard. Keep money as display strings; exports and paste-backs show a link's text without the URL.

The tool returns the finished HTML. In Claude Code, write it to a `.html` file and give the owner the path; on Claude Desktop, present it as an HTML artifact. On a contract error nothing renders and the exact problems are listed so you can fix and re-call.

Input parameters:

- `report` (object, required): The report contract object (see the description for its shape).

### `hcp_get_business_profile` (~141 tokens)

Read the business profile stored for this installation: who the shop is, who they buy from, their pricing rules, their payroll rules, and how their outbound messages should sound. Skills read this before asking setup questions, so an interview answered once is never asked twice; missing_sections is what a first run still has to ask, and each stored section carries the date it was last confirmed. The profile is this installation's own file, on this machine, beside the defaults file. Nothing in it is read from Housecall Pro or sent to it, or to anyone else. An empty profile is the ordinary state of a fresh install, not a problem.

### `hcp_set_business_profile` (~306 tokens)

Store one or more business-profile sections for this installation: shop, vendors, pricing, payroll, comms. Each section replaces the stored section whole, and null clears one - so save a section only after reading the whole section back to the user for a yes. The profile is this installation's own file, on this machine, beside the defaults file. Nothing in it is read from Housecall Pro or sent to it, or to anyone else. The sections hold the shop's own facts, never a customer's, and never credentials: a vendor's account_hint refuses anything that looks like a full account number.

Input parameters:

- `comms`: How outbound messages should sound: sender name, a short voice sample in the shop's own tone, and the follow-up cadence in days. Pass null to clear the section.
- `payroll`: Payroll rules: when the pay week starts and the commission rules by role. Pass null to clear the section.
- `pricing`: Pricing rules: the margin floor, per-category overrides, and how prices are rounded. Pass null to clear the section.
- `shop`: Who the shop is: trade(s), region, team size, and any peer group they benchmark against. Pass null to clear the section.
- `vendors`: Who they buy from: vendor name, a shipped pack name when one matches, how purchase documents arrive, an account hint (never a full number), and any learned custom layout. Pass null to clear the secti…

### `hcp_api_notes` (~207 tokens)

Look up what the Housecall Pro API actually does for a given topic, as opposed to what its published documentation says. Call this BEFORE concluding that something cannot be done, before retrying a route that returned 404, and after any write that reported success but looks like it changed nothing. It answers from a table of verified behaviour: routes the documentation describes that do not exist, writes that are accepted and silently ignored, and fields whose units are not what they appear to be. Ask in plain words - a topic, a route, a field name, or the thing you were trying to do. Omit the topic to read the whole table. This tool reads a table compiled into this server and makes no API call, so it costs nothing and cannot fail.

Input parameters:

- `topic` (string): What you are working on. A route ("PATCH /jobs"), a field ("work_status"), or a goal ("set a job description", "create an invoice"). Omit for everything.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/hcpapi-housecall-pro-mcp/housecall-pro-mcp#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 81
- 2026-09-16: 85
- 2026-09-15: 84
- 2026-09-14: 84
- 2026-09-13: 83
- 2026-09-12: 83
- 2026-09-11: 82
- 2026-09-10: 82
- 2026-09-09: 85
- 2026-09-08: 84
- 2026-09-07: 83
- 2026-09-06: 83
- 2026-09-05: 82
- 2026-09-04: 82
- 2026-09-03: 81
- 2026-09-02: 81
- 2026-09-01: 80
- 2026-08-31: 80
- 2026-08-30: 80
- 2026-08-29: 79
- 2026-08-28: 79
- 2026-08-27: 78
- 2026-08-26: 78
- 2026-08-25: 76
- 2026-08-24: 76
- 2026-08-23: 75
- 2026-08-22: 75

## Common questions

### What is the io.github.hcpapi/housecall-pro-mcp server?

io.github.hcpapi/housecall-pro-mcp is listed in the public MCP registry as io.github.hcpapi/housecall-pro-mcp. Independent MCP server for the Housecall Pro API: jobs, estimates, invoices, price book, schedule. This page covers its npm package (housecall-pro-mcp).

### Is the io.github.hcpapi/housecall-pro-mcp server safe to use?

io.github.hcpapi/housecall-pro-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.github.hcpapi/housecall-pro-mcp server expose?

io.github.hcpapi/housecall-pro-mcp exposes 4 tools: hcp_render_report, hcp_get_business_profile, hcp_set_business_profile, hcp_api_notes. Their descriptions and schemas cost roughly 1,045 tokens of context every time the server is loaded.

### Is the io.github.hcpapi/housecall-pro-mcp server still maintained?

io.github.hcpapi/housecall-pro-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.hcpapi/housecall-pro-mcp server under?

io.github.hcpapi/housecall-pro-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/housecall-pro-mcp
- Socket report: https://socket.dev/npm/package/housecall-pro-mcp
- Repository: https://github.com/hcpapi/housecall-pro-mcp
- Website: https://hcpapi.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/hcpapi-housecall-pro-mcp/housecall-pro-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/hcpapi-housecall-pro-mcp/housecall-pro-mcp.json
- HTML version of this page: https://verifymcp.io/servers/hcpapi-housecall-pro-mcp/housecall-pro-mcp