# io.usefulapi/kickserv (remote · kickserv.usefulapi.io)

Look up Kickserv customers, jobs, notes and time entries, and create jobs, tasks and charges.

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

## Components

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

## Channel facts

- Endpoint: `https://kickserv.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-04.

- **Endpoint Security**: 89/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 is enforced; there's no plaintext access path.
  - 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3534 tokens (~176/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 20 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 io.usefulapi/kickserv MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 75, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 70, +52)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 100
- [functional] First check of Tool coverage: 100

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (20)

### `kickserv_list_customers` (~258 tokens)

List customers

List or search customers, 30 per page. Every filter is an exact match on that field. Use `only` to keep the response small. Kickserv: GET /{account}/customers.xml.

Input parameters:

- `billing_city` (string): Billing city.
- `billing_state` (string): Billing state.
- `customer_number` (integer): Customer number.
- `email_address` (string): Exact email address.
- `include` (array): Related data to embed: contacts, jobs, tasks, notes, tax_entity, custom_field_assignments.
- `name` (string): Exact customer name.
- `only` (string): Comma-separated list of columns to return, e.g. `customer_number,name`. Kickserv recommends this: it makes responses much smaller and faster.
- `page` (integer): Page number (Kickserv returns 30 records per page). Omit for page 1.
- `phone_number` (string): Exact phone number, e.g. 800-555-1212.
- `service_city` (string): Service city.
- `service_state` (string): Service state (2-letter abbreviation).
- `service_zip_code` (string): Service ZIP (full zip+4 if the record has one).

### `kickserv_get_customer` (~104 tokens)

Get a customer

Fetch one customer by customer number, optionally with related contacts, jobs, tasks and notes. The result's `id` is what job/task create calls need as `customer_id`. Kickserv: GET /{account}/customers/{customer_number}.xml.

Input parameters:

- `customer_number` (integer, required): Customer number (as shown in Kickserv).
- `include` (array): Related data to embed: contacts, jobs, tasks, notes, tax_entity, custom_field_assignments.

### `kickserv_list_customer_jobs` (~148 tokens)

List a customer's jobs

List the jobs for one customer, 30 per page. Kickserv: GET /{account}/customers/{customer_number}/jobs.xml.

Input parameters:

- `customer_number` (integer, required): Customer number.
- `include` (array): Related data to embed: customer, employees, job_charges, time_entries, notes, job_type, job_status, tax_entity, custom_field_assignments.
- `only` (string): Comma-separated list of columns to return, e.g. `customer_number,name`. Kickserv recommends this: it makes responses much smaller and faster.
- `page` (integer): Page number (Kickserv returns 30 records per page). Omit for page 1.

### `kickserv_list_jobs` (~232 tokens)

List jobs

List jobs (work orders, estimates, invoices), 30 per page, filterable by schedule window, status, assigned employee, category (job type) or job status. Kickserv: GET /{account}/jobs.xml.

Input parameters:

- `employee_number` (integer): Only jobs assigned to this employee number.
- `include` (array): Related data to embed: customer, employees, job_charges, time_entries, notes, job_type, job_status, tax_entity, custom_field_assignments.
- `job_status_id` (integer): Only jobs with this custom job status id.
- `job_type_id` (integer): Only jobs in this category (job type id).
- `only` (string): Comma-separated list of columns to return, e.g. `customer_number,name`. Kickserv recommends this: it makes responses much smaller and faster.
- `page` (integer): Page number (Kickserv returns 30 records per page). Omit for page 1.
- `scheduled` (string): Scheduled-date window, e.g. today or this_week.
- `status` (string): Job status.

### `kickserv_get_job` (~105 tokens)

Get a job

Fetch one job by job number, optionally with its customer, assigned employees, job charges (line items), time entries and notes. Kickserv: GET /{account}/jobs/{job_number}.xml.

Input parameters:

- `include` (array): Related data to embed: customer, employees, job_charges, time_entries, notes, job_type, job_status, tax_entity, custom_field_assignments.
- `job_number` (integer, required): Job number (as shown in Kickserv).

### `kickserv_list_customer_notes` (~44 tokens)

List a customer's notes

List the notes on one customer. Kickserv: GET /{account}/customers/{customer_number}/notes.xml.

Input parameters:

- `customer_number` (integer, required): Customer number.

### `kickserv_list_job_notes` (~44 tokens)

List a job's notes

List the notes on one job. Kickserv: GET /{account}/jobs/{job_number}/notes.xml.

Input parameters:

- `job_number` (integer, required): Job number.

### `kickserv_list_job_time_entries` (~53 tokens)

List a job's time entries

List the time entries (hours logged by technicians) on one job. Kickserv: GET /{account}/jobs/{job_number}/time_entries.xml.

Input parameters:

- `job_number` (integer, required): Job number.

### `kickserv_get_task` (~51 tokens)

Get a task

Fetch one task (appointment / to-do attached to a job) by id. Kickserv: GET /{account}/tasks/{task_id}.xml.

Input parameters:

- `task_id` (integer, required): Task id.

### `kickserv_list_employees` (~58 tokens)

List employees

List all employees (technicians and office staff), active and inactive. Use their `id` for job/task assignment and time entries, and `employee_number` to filter jobs. Kickserv: GET /{account}/employees.xml.

### `kickserv_list_items` (~100 tokens)

List items

List products/services (the price list used for job charges), 30 per page. Active items only by default. Kickserv: GET /{account}/items.xml.

Input parameters:

- `name` (string): Filter by item name.
- `page` (integer): Page number (Kickserv returns 30 records per page). Omit for page 1.
- `which` (string): Which items to return: active (default), inactive, or all.

### `kickserv_create_customer` (~437 tokens)

Create a customer

WRITE: create a new customer. Kickserv assigns the customer number. Kickserv: POST /{account}/customers.xml.

Input parameters:

- `account_number` (string): Your own account number for the customer.
- `alt_contact` (string): Alternate contact name.
- `alt_phone_number` (string): Alternate phone number.
- `billing_address` (string): Billing address (where invoices go), line 1.
- `billing_address_2` (string): Billing address line 2.
- `billing_city` (string): Billing city.
- `billing_country` (string): Billing country.
- `billing_state` (string): Billing state.
- `billing_zip_code` (string): Billing ZIP/postal code.
- `company` (boolean): True if the customer is a company rather than a person.
- `company_name` (string): Company name.
- `contact` (string): Primary contact name.
- `customer_source_id` (integer): Customer source (lead source) id.
- `customer_type_id` (integer): Customer type id.
- `email_address` (string): Email address.
- `fax` (string): Fax number.
- `first_name` (string): Contact first name.
- `is_active` (boolean): False to mark the customer inactive (reversible).
- `last_name` (string): Contact last name.
- `mobile` (string): Mobile number.
- `name` (string, required): Customer name (required).
- `notify_via_email` (boolean): Send the customer email notifications.
- `notify_via_sms` (boolean): Send the customer SMS notifications.
- `phone_number` (string): Phone number.
- `service_address` (string): Service address (where the work happens), line 1.
- `service_address_2` (string): Service address line 2.
- `service_city` (string): Service city.
- `service_country` (string): Service country (2-letter code).
- `service_state` (string): Service state (2-letter abbreviation in the US).
- `service_zip_code` (string): Service ZIP/postal code.
- `special_instructions` (string): Special instructions shown to technicians.

### `kickserv_update_customer` (~468 tokens)

Update a customer

WRITE: update fields on an existing customer. Only the fields you pass change. Balances, credit limit and custom fields are not settable here. Kickserv: PATCH /{account}/customers/{customer_number}.xml.

Input parameters:

- `account_number` (string): Your own account number for the customer.
- `alt_contact` (string): Alternate contact name.
- `alt_phone_number` (string): Alternate phone number.
- `billing_address` (string): Billing address (where invoices go), line 1.
- `billing_address_2` (string): Billing address line 2.
- `billing_city` (string): Billing city.
- `billing_country` (string): Billing country.
- `billing_state` (string): Billing state.
- `billing_zip_code` (string): Billing ZIP/postal code.
- `company` (boolean): True if the customer is a company rather than a person.
- `company_name` (string): Company name.
- `contact` (string): Primary contact name.
- `customer_number` (integer, required): Customer number to update.
- `customer_source_id` (integer): Customer source (lead source) id.
- `customer_type_id` (integer): Customer type id.
- `email_address` (string): Email address.
- `fax` (string): Fax number.
- `first_name` (string): Contact first name.
- `is_active` (boolean): False to mark the customer inactive (reversible).
- `last_name` (string): Contact last name.
- `mobile` (string): Mobile number.
- `name` (string): New customer name.
- `notify_via_email` (boolean): Send the customer email notifications.
- `notify_via_sms` (boolean): Send the customer SMS notifications.
- `phone_number` (string): Phone number.
- `service_address` (string): Service address (where the work happens), line 1.
- `service_address_2` (string): Service address line 2.
- `service_city` (string): Service city.
- `service_country` (string): Service country (2-letter code).
- `service_state` (string): Service state (2-letter abbreviation in the US).
- `service_zip_code` (string): Service ZIP/postal code.
- `special_instructions` (string): Special instructions shown to technicians.

### `kickserv_add_customer_note` (~85 tokens)

Add a note to a customer

WRITE: add a note to a customer. Set `public` to true to make it visible to the customer. Kickserv: POST /{account}/customers/{customer_number}/notes.xml.

Input parameters:

- `customer_number` (integer, required): Customer number.
- `note` (string, required): Note text.
- `public` (boolean): True to make the note public (customer-visible).

### `kickserv_create_job` (~302 tokens)

Create a job

WRITE: create a job (work order) for a customer. `customer_id` is the customer's internal `id` (from kickserv_get_customer), not the customer number; `job_type_id` is the job category. Set `estimate` to create it as an estimate. Kickserv: POST /{account}/jobs.xml.

Input parameters:

- `customer_id` (integer, required): The customer's internal `id` (NOT the customer_number).
- `description` (string): Job description / work to be done.
- `duration` (number): Job duration.
- `employee_ids` (array): Employee `id`s (from kickserv_list_employees) to assign. Replaces the current assignment.
- `ends_at` (string): When the job ends. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`.
- `estimate` (boolean): True to create the job as an estimate.
- `job_type_id` (integer, required): Job category (job type) id.
- `name` (string): Job name/title.
- `po_number` (string): Customer purchase-order number.
- `scheduled_on` (string): When the job is scheduled. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`.

### `kickserv_update_job` (~290 tokens)

Update a job

WRITE: update an existing job — reschedule it, rename it, change its description, category or custom job status, or reassign employees (employee_ids replaces the assignment). Totals, tax and payment fields are not settable here. Kickserv: PATCH /{account}/jobs/{job_number}.xml.

Input parameters:

- `description` (string): Job description / work to be done.
- `duration` (number): Job duration.
- `employee_ids` (array): Employee `id`s (from kickserv_list_employees) to assign. Replaces the current assignment.
- `ends_at` (string): When the job ends. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`.
- `job_number` (integer, required): Job number to update.
- `job_status_id` (integer): New custom job status id.
- `job_type_id` (integer): New job category (job type) id.
- `name` (string): Job name/title.
- `po_number` (string): Customer purchase-order number.
- `scheduled_on` (string): When the job is scheduled. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`.

### `kickserv_add_job_note` (~85 tokens)

Add a note to a job

WRITE: add a note to a job. Set `public` to true to make it visible to the customer. Kickserv: POST /{account}/jobs/{job_number}/notes.xml.

Input parameters:

- `job_number` (integer, required): Job number.
- `note` (string, required): Note text.
- `public` (boolean): True to make the note public (customer-visible).

### `kickserv_create_task` (~265 tokens)

Create a task

WRITE: create a task (appointment / to-do) on a job and optionally assign employees. `job_id` is the job's internal `id` (from kickserv_get_job), not the job number. Kickserv: POST /{account}/tasks.xml.

Input parameters:

- `customer_id` (integer): The customer's internal `id`.
- `description` (string): Task description.
- `duration` (integer): Task duration.
- `employee_ids` (array): Employee `id`s (from kickserv_list_employees) to assign. Replaces the current assignment.
- `ends_at` (string): When the task ends. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`.
- `job_id` (integer, required): The job's internal `id` (NOT the job_number).
- `name` (string, required): Task name.
- `scheduled_at` (string): When the task is scheduled. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`.
- `task_type_id` (integer, required): Task type id.

### `kickserv_log_time_entry` (~239 tokens)

Log time on a job

WRITE: log hours worked by an employee on a job. `employee_id` is the employee's `id` from kickserv_list_employees. Kickserv: POST /{account}/jobs/{job_number}/time_entries.xml.

Input parameters:

- `billable` (boolean): Whether the time is billable.
- `employee_id` (integer, required): The employee's `id`.
- `ended_on` (string): When the work ended. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`.
- `job_number` (integer, required): Job number.
- `mileage` (number): Mileage driven.
- `note` (string): Note about the work.
- `number_of_hours` (number, required): Hours worked, e.g. 1.25.
- `started_on` (string, required): When the work started, e.g. `2026-10-02 13:00` or `10/02/2026 01:00pm`.
- `time_entry_type_id` (integer): Time entry type id.

### `kickserv_add_job_charge` (~166 tokens)

Add a charge to a job

WRITE: add a charge (line item — a product, service or part) to a job. This changes the job's estimate/invoice total; it does NOT charge the customer's card. Pick `item_id` from kickserv_list_items. Kickserv: POST /{account}/jobs/{job_number}/job_charges.xml.

Input parameters:

- `description` (string): Line-item description.
- `details` (string): Line-item details.
- `discount` (number): Discount.
- `item_id` (integer): Item `id` from kickserv_list_items.
- `job_charge_type_id` (integer, required): Job charge type id.
- `job_number` (integer, required): Job number.
- `price_per_unit` (number): Unit price.
- `quantity` (number): Quantity.

## Diagnostics

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

## Score history

- 2026-10-04: 76
- 2026-10-03: 76
- 2026-10-02: 76
- 2026-10-01: 75
- 2026-09-30: 70
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/kickserv MCP server?

io.usefulapi/kickserv is an MCP server listed in the public MCP registry as io.usefulapi/kickserv. Look up Kickserv customers, jobs, notes and time entries, and create jobs, tasks and charges. This page covers its hosted endpoint (https://kickserv.usefulapi.io/mcp).

### Is the io.usefulapi/kickserv MCP server safe to use?

io.usefulapi/kickserv scores 76 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/kickserv MCP server expose?

io.usefulapi/kickserv exposes 20 tools: kickserv_list_customers, kickserv_get_customer, kickserv_list_customer_jobs, kickserv_list_jobs, kickserv_get_job, and 15 more. Their descriptions and schemas cost roughly 3,534 tokens of context every time the server is loaded.

### Does the io.usefulapi/kickserv MCP server require authentication?

Yes. io.usefulapi/kickserv 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 io.usefulapi/kickserv MCP server still maintained?

io.usefulapi/kickserv 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.

## Links

- Remote endpoint: https://kickserv.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-kickserv/kickserv.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-kickserv/kickserv.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-kickserv/kickserv