Homebase MCP by usefulapi
REMOTE · HOMEBASE.USEFULAPI.IO
Read Homebase locations, employees, shifts, timecards, labor costs and time clock status.
Available components
Last scanned (4 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Project Management
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 +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.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
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 17 Oct 2026 · Probed https://homebase.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 homebase.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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://homebase.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://homebase.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://homebase.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://homebase.usefulapi.io/mcp |
| Authorisation server | https://homebase.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://homebase.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/homebase/ |
| http (plaintext) | http://homebase.usefulapi.io/mcp | Inconclusive | 302 | http://homebase.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 →
homebase_get_company Get company ~42
The Homebase company this API key belongs to: name, owner (id, name, email, phone) and created/updated times. GET /company.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
homebase_get_employee Get employee ~111
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_id | integer | yes | Homebase user id of the employee. |
| location_uuid | string | yes | Homebase location uuid (from homebase_list_locations). |
| with_archived | boolean | – | Also find an archived employee (default false). |
No output schema declared.
No examples provided.
homebase_get_labor Get labor report ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | 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 | yes | Homebase location uuid (from homebase_list_locations). |
| start_date | string | yes | Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00). |
No output schema declared.
No examples provided.
homebase_get_labor_by_employee Get labor report by employee ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | 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 | yes | Homebase location uuid (from homebase_list_locations). |
| start_date | string | yes | Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00). |
No output schema declared.
No examples provided.
homebase_get_labor_by_role Get labor report by role ~167
Aggregate labor (hours, cost, tips, overtime) for a location in a date range, grouped by role. GET /locations/{location_uuid}/labor/by_role.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | 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 | yes | Homebase location uuid (from homebase_list_locations). |
| start_date | string | yes | Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00). |
No output schema declared.
No examples provided.
homebase_get_location Get location ~55
One location by uuid: name, address, phone, website, time zone and POS merchant id. GET /locations/{location_uuid}.
| Name | Type | Req | Description |
|---|---|---|---|
| location_uuid | string | yes | Homebase location uuid (from homebase_list_locations). |
No output schema declared.
No examples provided.
homebase_get_location_plan Get location plan ~58
The Homebase subscription plan of a location: plan number, price, last update and trial state. GET /locations/{location_uuid}/plan.
| Name | Type | Req | Description |
|---|---|---|---|
| location_uuid | string | yes | Homebase location uuid (from homebase_list_locations). |
No output schema declared.
No examples provided.
homebase_get_shift Get shift ~80
One shift of a location by id, with its labor data and optional note. GET /locations/{location_uuid}/shifts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| location_uuid | string | yes | Homebase location uuid (from homebase_list_locations). |
| shift_id | integer | yes | Homebase shift id. |
| with_note | boolean | – | Include the shift note. |
No output schema declared.
No examples provided.
homebase_get_timecard Get timecard ~81
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| location_uuid | string | yes | Homebase location uuid (from homebase_list_locations). |
| timecard_id | integer | yes | Homebase timecard id. |
No output schema declared.
No examples provided.
homebase_get_timeclock_status Get time clock status ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Homebase job id (`job.id` on an employee). |
No output schema declared.
No examples provided.
homebase_list_deleted_shifts List deleted shifts ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | 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 | yes | 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 | yes | Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00). |
No output schema declared.
No examples provided.
homebase_list_deleted_timecards List deleted timecards ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | 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 | yes | 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 | yes | Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00). |
No output schema declared.
No examples provided.
homebase_list_employees List employees ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| location_uuid | string | yes | 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). |
No output schema declared.
No examples provided.
homebase_list_locations List locations ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
homebase_list_shifts List shifts ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date_filter | string | – | Which shift time the range applies to (default start_at). |
| end_date | string | yes | 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 | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
homebase_list_timecards List timecards ~268
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date_filter | string | – | Which timecard time the range applies to (default clock_in). |
| end_date | string | yes | 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 | yes | 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 | yes | Start of the range. ISO 8601: a date (2026-10-01) or a date-time with timezone (2026-10-01T09:00:00-05:00). |
No output schema declared.
No examples provided.
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.
remote · homebase.usefulapi.io
claude mcp add --transport http io-usefulapi-homebase 'https://homebase.usefulapi.io/mcp'
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.