io.usefulapi/homebase

None of its 16 tools are described as changing anything.

• homebase_get_companyreads or searches

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

  Publisher declares: read-only yes · destructive no · open-world yes

  Takes no inputs.

• homebase_list_locationsreads or searches

  “List the locations (stores or sites) of the account with uuid, name, address, phone, website and time zone.”

  Publisher declares: read-only yes · destructive no · open-world yes

  Takes no inputs.

• homebase_get_locationreads or searches

  “One location by uuid: name, address, phone, website, time zone and POS merchant id.”

  Publisher declares: read-only yes · destructive no · open-world yes

  1 input, 1 required

  • location_uuidstringrequired“Homebase location uuid (from homebase_list_locations).”
• homebase_get_location_planreads or searches

  “The Homebase subscription plan of a location: plan number, price, last update and trial state.”

  Publisher declares: read-only yes · destructive no · open-world yes

  1 input, 1 required

  • location_uuidstringrequired“Homebase location uuid (from homebase_list_locations).”
• homebase_list_employeesreads or searches

  “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.”

  Publisher declares: read-only yes · destructive no · open-world yes

  4 inputs, 1 required

  • location_uuidstringrequired“Homebase location uuid (from homebase_list_locations).”
  • with_archivedboolean“Include archived employees (default false).”
  • pageinteger“Page number, from 1 (default 1).”
  • per_pageinteger“Results per page, 1-100 (default 25).”
• homebase_get_employeereads or searches

  “One employee of a location by user id, with contact details and job (role, wage type and rate, payroll id).”

  Publisher declares: read-only yes · destructive no · open-world yes

  3 inputs, 2 required

  • location_uuidstringrequired“Homebase location uuid (from homebase_list_locations).”
  • employee_idintegerrequired“Homebase user id of the employee.”
  • with_archivedboolean“Also find an archived employee (default false).”
• homebase_list_shiftsreads or searches

  “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).”

  Publisher declares: read-only yes · destructive no · open-world yes

  8 inputs, 3 required

  • location_uuidstringrequired“Homebase location uuid (from homebase_list_locations).”
  • start_datestringrequired“Start of the range.”
  • end_datestringrequired“End of the range.”
  • openboolean“Only open shifts that any employee can claim.”
  • with_noteboolean“Include the shift note.”
  • date_filterstring“Which shift time the range applies to (default start_at).”
  • pageinteger“Page number, from 1 (default 1).”
  • per_pageinteger“Results per page, 1-100 (default 25).”
• homebase_get_shiftreads or searches

  “One shift of a location by id, with its labor data and optional note.”

  Publisher declares: read-only yes · destructive no · open-world yes

  3 inputs, 2 required

  • location_uuidstringrequired“Homebase location uuid (from homebase_list_locations).”
  • shift_idintegerrequired“Homebase shift id.”
  • with_noteboolean“Include the shift note.”
• homebase_list_deleted_shiftsreads or searches

  “The ids of shifts deleted in a date range at a location, with their start, end and deletion time.”

  Publisher declares: read-only yes · destructive no · open-world yes

  5 inputs, 3 required

  • location_uuidstringrequired“Homebase location uuid (from homebase_list_locations).”
  • start_datestringrequired“Start of the range.”
  • end_datestringrequired“End of the range.”
  • pageinteger“Page number, from 1 (default 1).”
  • per_pageinteger“Results per page, 1-100 (default 25).”
• homebase_list_timecardsreads or searches

  “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.”

  Publisher declares: read-only yes · destructive no · open-world yes

  6 inputs, 3 required

  • location_uuidstringrequired“Homebase location uuid (from homebase_list_locations).”
  • start_datestringrequired“Start of the range.”
  • end_datestringrequired“End of the range.”
  • date_filterstring“Which timecard time the range applies to (default clock_in).”
  • pageinteger“Page number, from 1 (default 1).”
  • per_pageinteger“Results per page, 1-100 (default 25).”
• homebase_get_timecardreads or searches

  “One timecard of a location by id: clock in and out, breaks, labor hours and cost, tips, approval state.”

  Publisher declares: read-only yes · destructive no · open-world yes

  2 inputs, 2 required

  • location_uuidstringrequired“Homebase location uuid (from homebase_list_locations).”
  • timecard_idintegerrequired“Homebase timecard id.”
• homebase_list_deleted_timecardsreads or searches

  “The ids of timecards deleted in a date range at a location, with clock in, clock out and deletion time.”

  Publisher declares: read-only yes · destructive no · open-world yes

  5 inputs, 3 required

  • location_uuidstringrequired“Homebase location uuid (from homebase_list_locations).”
  • start_datestringrequired“Start of the range.”
  • end_datestringrequired“End of the range.”
  • pageinteger“Page number, from 1 (default 1).”
  • per_pageinteger“Results per page, 1-100 (default 25).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.