# RepairDesk MCP by usefulapi (remote · repairdesk.usefulapi.io)

Read tickets, customers, stock and invoices; add confirmed internal ticket notes.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://repairdesk.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.1`

## 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-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - 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.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

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

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-repairdesk": {
      "type": "http",
      "url": "https://repairdesk.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-11-02 (score 18, −45)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 62)

First indexed and scored.

## MCP tools (17)

### `repairdesk_list_customers` (~58 tokens)

List customers

Search customer records by keyword or referral source. Returns one page. GET /customers.

Input parameters:

- `keyword` (string)
- `page` (integer)
- `pagesize` (integer)
- `referredby` (string)

### `repairdesk_get_customer` (~37 tokens)

Get a customer

Get one customer using its ID from customer or ticket lookup. GET /customers/{customerId}.

Input parameters:

- `customer_id` (string, required)

### `repairdesk_list_tickets` (~125 tokens)

List repair tickets

Find ticket/order numbers, customer/device context, status and assignments. keyword searches the ticket list. Returns one page (page defaults0). GET /tickets.

Input parameters:

- `assigned_to` (string)
- `created_by` (string)
- `default_order` (string)
- `from_date` (integer): Unix timestamp in seconds, not milliseconds.
- `keyword` (string)
- `page` (integer)
- `pagesize` (integer)
- `status` (string)
- `to_date` (integer): Unix timestamp in seconds, not milliseconds.

### `repairdesk_get_ticket` (~55 tokens)

Get a repair ticket

Read ticket summary, customer, repair devices, notes, line items and invoice context. GET /tickets/{Ticket-Id}. The vendor checks store ownership, including transfers into this store.

Input parameters:

- `ticket_id` (string, required)

### `repairdesk_list_invoices` (~105 tokens)

List invoices

Search invoice numbers and customers; inspect totals, paid status and available balances. One page (page defaults0). GET /invoices.

Input parameters:

- `from_date` (integer): Unix timestamp in seconds, not milliseconds.
- `keyword` (string)
- `page` (integer)
- `pagesize` (integer)
- `payment_method` (string)
- `status` (string)
- `to_date` (integer): Unix timestamp in seconds, not milliseconds.

### `repairdesk_get_invoice` (~39 tokens)

Get an invoice

Read a single invoice; no payment or invoice creation occurs. GET /invoices/{Invoice-Id}.

Input parameters:

- `invoice_id` (string, required)

### `repairdesk_get_invoice_due` (~39 tokens)

Get invoice amount due

Read outstanding invoice amount and paid flag. GET /invoices/{Invoice-Id}/dueamount.

Input parameters:

- `invoice_id` (string, required)

### `repairdesk_list_inventory` (~67 tokens)

Search inventory

Look up inventory by ID, name or SKU in keyword. Returns the vendor's items list; this endpoint documents pagesize but no page parameter. GET /inventory.

Input parameters:

- `keyword` (string)
- `missing_cost_price` (string)
- `pagesize` (integer)

### `repairdesk_list_devices` (~40 tokens)

List device models

Read device catalogue by manufacturer/brand or device name. GET /devices.

Input parameters:

- `brand` (string)
- `device_name` (string)

### `repairdesk_list_parts` (~24 tokens)

List repair parts

Read parts names, SKU, stock and pricing. GET /parts.

### `repairdesk_list_statuses` (~24 tokens)

List ticket statuses

Find the store's available ticket status names. GET /statuses.

### `repairdesk_list_repair_categories` (~22 tokens)

List repair categories

Read available repair categories. GET /repaircategories.

### `repairdesk_list_networks` (~22 tokens)

List networks

Read the device network catalogue. GET /networks.

### `repairdesk_get_inventory_options` (~27 tokens)

Read inventory options

Read available item conditions and physical storage locations. GET /inventory/additionalinfo.

### `repairdesk_list_employees` (~42 tokens)

List repair staff

Read only staff ID, display name and role for assignment lookup. Access PINs, permissions, private employee data and payroll are omitted. GET /employees.

### `repairdesk_list_appointments` (~121 tokens)

List appointments and leads

Search leads/appointments with customer/device context and assignment. Returns one page. GET /appointment.

Input parameters:

- `assigned_to` (integer)
- `created_by` (integer)
- `from_date` (integer): Unix timestamp in seconds, not milliseconds.
- `keyword` (string)
- `page` (integer)
- `pagesize` (integer)
- `repairType` (string)
- `serviceType` (string)
- `status` (string)
- `to_date` (integer): Unix timestamp in seconds, not milliseconds.

### `repairdesk_add_internal_ticket_note` (~119 tokens)

Add an internal ticket note

Append an internal note (type0) after explicit confirmation. First reads the ticket and verifies its ID and optional repair/device line ID. No status, timer, messaging, payment or delete endpoint is called. POST /ticket/addnote. On an uncertain response, inspect notes before retrying; writes are attempted once.

Input parameters:

- `confirm` (boolean): Set true only after the user reviews the target ticket and exact note text.
- `device_id` (string)
- `note` (string, required)
- `ticket_id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 63
- 2026-10-31: 62

## Common questions

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

RepairDesk MCP by usefulapi is listed in the public MCP registry as io.usefulapi/repairdesk. Read tickets, customers, stock and invoices; add confirmed internal ticket notes. This page covers its hosted endpoint (https://repairdesk.usefulapi.io/mcp).

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

RepairDesk MCP by usefulapi scores 18 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 RepairDesk MCP by usefulapi server expose?

RepairDesk MCP by usefulapi exposes 17 tools: repairdesk_list_customers, repairdesk_get_customer, repairdesk_list_tickets, repairdesk_get_ticket, repairdesk_list_invoices, and 12 more. Their descriptions and schemas cost roughly 966 tokens of context every time the server is loaded.

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

Its publisher declares no required credentials for RepairDesk MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

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

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