# Homebase MCP by usefulapi (remote · homebase.usefulapi.io)

Read Homebase locations, employees, shifts, timecards, labor costs and time clock status.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

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

## Channel facts

- Endpoint: `https://homebase.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2458 tokens (~153/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Homebase MCP by usefulapi server?

Homebase MCP by usefulapi is a hosted endpoint at https://homebase.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-homebase 'https://homebase.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-homebase": {
      "type": "http",
      "url": "https://homebase.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-16 (score 64, +1)

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

### 2026-10-14 (score 63, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] Schema quality: excellent → good
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (16)

### `homebase_get_company` (~42 tokens)

Get company

The Homebase company this API key belongs to: name, owner (id, name, email, phone) and created/updated times. GET /company.

### `homebase_list_locations` (~51 tokens)

List locations

List the locations (stores or sites) of the account with uuid, name, address, phone, website and time zone. The uuid is the id every other Homebase tool needs. GET /locations.

### `homebase_get_location` (~55 tokens)

Get location

One location by uuid: name, address, phone, website, time zone and POS merchant id. GET /locations/{location_uuid}.

Input parameters:

- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).

### `homebase_get_location_plan` (~58 tokens)

Get location plan

The Homebase subscription plan of a location: plan number, price, last update and trial state. GET /locations/{location_uuid}/plan.

Input parameters:

- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).

### `homebase_list_employees` (~138 tokens)

List employees

List the employees of a location with contact details and their job: level, default role, additional roles, wage type and rate, payroll id and archive date. The time-clock PIN is never returned. GET /locations/{location_uuid}/employees.

Input parameters:

- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `with_archived` (boolean): Include archived employees (default false).

### `homebase_get_employee` (~111 tokens)

Get employee

One employee of a location by user id, with contact details and job (role, wage type and rate, payroll id). The id is the job's user id from homebase_list_employees. GET /locations/{location_uuid}/employees/{id}.

Input parameters:

- `employee_id` (integer, required): Homebase user id of the employee.
- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).
- `with_archived` (boolean): Also find an archived employee (default false).

### `homebase_list_shifts` (~274 tokens)

List shifts

List the scheduled shifts of a location in a date range: employee, role, department, start and end, published/open state, wage rate and scheduled labor hours (regular, overtime). Filter open shifts only. GET /locations/{location_uuid}/shifts.

Input parameters:

- `date_filter` (string): Which shift time the range applies to (default start_at).
- `end_date` (string, required): End of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).
- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).
- `open` (boolean): Only open shifts that any employee can claim.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `start_date` (string, required): Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).
- `with_note` (boolean): Include the shift note.

### `homebase_get_shift` (~80 tokens)

Get shift

One shift of a location by id, with its labor data and optional note. GET /locations/{location_uuid}/shifts/{id}.

Input parameters:

- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).
- `shift_id` (integer, required): Homebase shift id.
- `with_note` (boolean): Include the shift note.

### `homebase_list_deleted_shifts` (~223 tokens)

List deleted shifts

The ids of shifts deleted in a date range at a location, with their start, end and deletion time. Use it to keep a copy of the schedule in sync. GET /locations/{location_uuid}/shifts/deleted.

Input parameters:

- `end_date` (string, required): End of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).
- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `start_date` (string, required): Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).

### `homebase_list_timecards` (~268 tokens)

List timecards

List the timecards (worked time) of a location in a date range: employee, role, clock in and out, breaks, hours, labor cost, tips and approval state. Time-off hours are always 0 on timecards; use homebase_get_labor_by_employee for totals with time off. GET /locations/{location_uuid}/timecards.

Input parameters:

- `date_filter` (string): Which timecard time the range applies to (default clock_in).
- `end_date` (string, required): End of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).
- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `start_date` (string, required): Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).

### `homebase_get_timecard` (~81 tokens)

Get timecard

One timecard of a location by id: clock in and out, breaks, labor hours and cost, tips, approval state. GET /locations/{location_uuid}/timecards/{id}.

Input parameters:

- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).
- `timecard_id` (integer, required): Homebase timecard id.

### `homebase_list_deleted_timecards` (~226 tokens)

List deleted timecards

The ids of timecards deleted in a date range at a location, with clock in, clock out and deletion time. Use it to keep a copy of the timecards in sync. GET /locations/{location_uuid}/timecards/deleted.

Input parameters:

- `end_date` (string, required): End of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).
- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `start_date` (string, required): Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).

### `homebase_get_labor` (~193 tokens)

Get labor report

Aggregate labor for a location in a date range, grouped by day or by hour: regular, overtime and paid hours, labor cost, tips, breaks and time off. GET /locations/{location_uuid}/labor.

Input parameters:

- `end_date` (string, required): End of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).
- `group_by` (string): Group the totals by day (default) or by hour.
- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).
- `start_date` (string, required): Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).

### `homebase_get_labor_by_role` (~167 tokens)

Get labor report by role

Aggregate labor (hours, cost, tips, overtime) for a location in a date range, grouped by role. GET /locations/{location_uuid}/labor/by_role.

Input parameters:

- `end_date` (string, required): End of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).
- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).
- `start_date` (string, required): Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).

### `homebase_get_labor_by_employee` (~179 tokens)

Get labor report by employee

Aggregate labor (hours, cost, wage rate, tips, overtime, time off) for a location in a date range, grouped by employee. Use it for payroll totals. GET /locations/{location_uuid}/labor/by_employee.

Input parameters:

- `end_date` (string, required): End of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).
- `location_uuid` (string, required): Homebase location uuid (from homebase_list_locations).
- `start_date` (string, required): Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00).

### `homebase_get_timeclock_status` (~101 tokens)

Get time clock status

The current time-clock state of one job (employee at a location): clocked_in, on_break or clocked_out, the current shift, the shifts that can be clocked into and the breaks that can be started. The job id is the `job.id` of an employee from homebase_list_employees. GET /timeclock/status.

Input parameters:

- `job_id` (integer, required): Homebase job id (`job.id` on an employee).

## Diagnostics

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

## Score history

- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 60
- 2026-10-12: 60

## Common questions

### What is the Homebase MCP by usefulapi server?

Homebase MCP by usefulapi is listed in the public MCP registry as io.usefulapi/homebase. Read Homebase locations, employees, shifts, timecards, labor costs and time clock status. This page covers its hosted endpoint (https://homebase.usefulapi.io/mcp).

### Is the Homebase MCP by usefulapi server safe to use?

Homebase MCP by usefulapi scores 64 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 Homebase MCP by usefulapi server expose?

Homebase MCP by usefulapi exposes 16 tools: homebase_get_company, homebase_list_locations, homebase_get_location, homebase_get_location_plan, homebase_list_employees, and 11 more. Their descriptions and schemas cost roughly 2,247 tokens of context every time the server is loaded.

### Does the Homebase MCP by usefulapi server require authentication?

Yes. Homebase MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Homebase MCP by usefulapi server still maintained?

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