io.usefulapi/housecall-pro
REMOTE · HOUSECALL-PRO.USEFULAPI.IO · SCANNED OCT 4
Manage Housecall Pro customers, jobs, estimates and leads; schedule and dispatch jobs.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- 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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
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.
remote · housecall-pro.usefulapi.io
claude mcp add --transport http io-usefulapi-housecall-pro 'https://housecall-pro.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-housecall-pro": {
"url": "https://housecall-pro.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-housecall-pro": {
"type": "http",
"url": "https://housecall-pro.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-housecall-pro] url = "https://housecall-pro.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-housecall-pro": {
"type": "remote",
"url": "https://housecall-pro.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-housecall-pro --url 'https://housecall-pro.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-housecall-pro:
url: "https://housecall-pro.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-housecall-pro": {
"Transport": "http",
"Url": "https://housecall-pro.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-housecall-pro -t streamable-http -u 'https://housecall-pro.usefulapi.io/mcp'
{
"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.
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.
- 4 Oct 26 −43
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Oct 26 +43
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.10 ▲ functional
- Server version: 1.3.0 → 1.5.1 functional
- 2 Oct 26 −39
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Oct 26 +3
- Authorization: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +51
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 29 Sept 26 18
First indexed and scored.
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 4 Oct 2026 · Probed https://housecall-pro.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 housecall-pro.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | 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://housecall-pro.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://housecall-pro.usefulapi.io/mcp | HTTPS enforced | 301 | https://housecall-pro.usefulapi.io/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 →
housecall_add_job_note Add a note to a job ~53
Add a text note to a job. Housecall Pro: POST /jobs/{job_id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The note text. |
| job_id | string | yes | The job id. |
No output schema declared.
No examples provided.
housecall_create_customer Create a customer ~138
Create a new customer, optionally with one or more addresses. Housecall Pro: POST /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | – | Addresses to create with the customer. |
| company | string | – | The customer's company name. |
| 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 | – | – |
No output schema declared.
No examples provided.
housecall_create_customer_address Add an address to a customer ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| country | string | yes | Country, e.g. US. |
| customer_id | string | yes | The customer id. |
| state | string | yes | – |
| street | string | yes | – |
| street_line_2 | string | – | – |
| zip | string | yes | – |
No output schema declared.
No examples provided.
housecall_create_estimate Create an estimate ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
housecall_create_job Create a job ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | string | yes | The customer address id. |
| assigned_employee_ids | array | – | Employees to assign. |
| business_unit_id | string | – | – |
| customer_id | string | yes | 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. |
No output schema declared.
No examples provided.
housecall_create_lead Create a lead ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
housecall_dispatch_job Dispatch a job to employees ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_ids | array | yes | Every employee who should be dispatched. |
| job_id | string | yes | The job id. |
No output schema declared.
No examples provided.
housecall_get_company Get the company ~60
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
housecall_get_customer Get one customer ~64
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The customer id. |
| expand | array | – | Extras to include. |
No output schema declared.
No examples provided.
housecall_get_estimate Get one estimate ~51
Fetch a single estimate by id, including its options and each option's approval status. Housecall Pro: GET /estimates/{estimate_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| estimate_id | string | yes | The estimate id. |
No output schema declared.
No examples provided.
housecall_get_job Get one job ~66
Fetch a single job by id — customer, address, work status and timestamps, schedule, assigned employees, notes and totals. Housecall Pro: GET /jobs/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | array | – | Extras to include. |
| job_id | string | yes | The job id. |
No output schema declared.
No examples provided.
housecall_get_lead Get one lead ~58
Fetch a single lead by id — its customer, address, lead source, tags, assigned employee, status and pipeline status. Housecall Pro: GET /leads/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| lead_id | string | yes | The lead id. |
No output schema declared.
No examples provided.
housecall_list_customers List customers ~157
List or search customers, with their phone numbers, tags and addresses. `q` searches name, email, mobile number and address. Housecall Pro: GET /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
housecall_list_employees List employees ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
housecall_list_estimates List estimates ~326
List estimates, filterable by scheduled window, customer, assigned employees and work status. Each carries its customer, address, schedule and options. Housecall Pro: GET /estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
housecall_list_invoices List invoices ~369
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
housecall_list_job_invoices List a job's invoices ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job id. |
No output schema declared.
No examples provided.
housecall_list_job_line_items List a job's line items ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job id. |
No output schema declared.
No examples provided.
housecall_list_job_types List job types ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Filter job types by name. |
No output schema declared.
No examples provided.
housecall_list_jobs List jobs ~340
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
housecall_list_leads List leads ~185
List leads, filterable by status (open / won / lost), customer, assigned employees, tags and lead source. Housecall Pro: GET /leads.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
housecall_list_price_book_services List price book services ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
housecall_list_tags List tags ~73
List the tags defined in the company. Housecall Pro: GET /tags.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
housecall_update_customer Update a customer ~153
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The customer's company name. |
| customer_id | string | yes | The customer id. |
| 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 | – | – |
No output schema declared.
No examples provided.
housecall_update_job_schedule Reschedule a job ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The job id. |
| notify | boolean | – | Notify the customer of the new schedule. |
| notify_pro | boolean | – | Notify the assigned employee(s). |
| start_time | string | yes | ISO-8601 start time. |
No output schema declared.
No examples provided.
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.