RepairDesk MCP by usefulapi
REMOTE · REPAIRDESK.USEFULAPI.IO
Read tickets, customers, stock and invoices; add confirmed internal ticket notes.
Available components
Last scanned (8 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
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.
- 2 Nov 26 −45
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 62
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 5 Nov 2026 · Probed https://repairdesk.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 repairdesk.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://repairdesk.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/repairdesk/ |
| http (plaintext) | http://repairdesk.usefulapi.io/mcp | Inconclusive | 302 | http://repairdesk.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 →
repairdesk_add_internal_ticket_note Add an internal ticket note ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Set true only after the user reviews the target ticket and exact note text. |
| device_id | string | – | – |
| note | string | yes | – |
| ticket_id | string | yes | – |
No output schema declared.
No examples provided.
repairdesk_get_customer Get a customer ~37
Get one customer using its ID from customer or ticket lookup. GET /customers/{customerId}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | – |
No output schema declared.
No examples provided.
repairdesk_get_inventory_options Read inventory options ~27
Read available item conditions and physical storage locations. GET /inventory/additionalinfo.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
repairdesk_get_invoice Get an invoice ~39
Read a single invoice; no payment or invoice creation occurs. GET /invoices/{Invoice-Id}.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | – |
No output schema declared.
No examples provided.
repairdesk_get_invoice_due Get invoice amount due ~39
Read outstanding invoice amount and paid flag. GET /invoices/{Invoice-Id}/dueamount.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | – |
No output schema declared.
No examples provided.
repairdesk_get_ticket Get a repair ticket ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | string | yes | – |
No output schema declared.
No examples provided.
repairdesk_list_appointments List appointments and leads ~121
Search leads/appointments with customer/device context and assignment. Returns one page. GET /appointment.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
repairdesk_list_customers List customers ~58
Search customer records by keyword or referral source. Returns one page. GET /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | – |
| page | integer | – | – |
| pagesize | integer | – | – |
| referredby | string | – | – |
No output schema declared.
No examples provided.
repairdesk_list_devices List device models ~40
Read device catalogue by manufacturer/brand or device name. GET /devices.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | – |
| device_name | string | – | – |
No output schema declared.
No examples provided.
repairdesk_list_employees List repair staff ~42
Read only staff ID, display name and role for assignment lookup. Access PINs, permissions, private employee data and payroll are omitted. GET /employees.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
repairdesk_list_inventory Search inventory ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | – |
| missing_cost_price | string | – | – |
| pagesize | integer | – | – |
No output schema declared.
No examples provided.
repairdesk_list_invoices List invoices ~105
Search invoice numbers and customers; inspect totals, paid status and available balances. One page (page defaults0). GET /invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
repairdesk_list_networks List networks ~22
Read the device network catalogue. GET /networks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
repairdesk_list_parts List repair parts ~24
Read parts names, SKU, stock and pricing. GET /parts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
repairdesk_list_repair_categories List repair categories ~22
Read available repair categories. GET /repaircategories.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
repairdesk_list_statuses List ticket statuses ~24
Find the store's available ticket status names. GET /statuses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
repairdesk_list_tickets List repair tickets ~125
Find ticket/order numbers, customer/device context, status and assignments. keyword searches the ticket list. Returns one page (page defaults0). GET /tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · repairdesk.usefulapi.io
claude mcp add --transport http io-usefulapi-repairdesk 'https://repairdesk.usefulapi.io/mcp'
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.