# UpKeep MCP by usefulapi (remote · upkeep.usefulapi.io)

Read UpKeep work orders, assets, parts and meters; create requests and work orders.

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

## Components

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

## Channel facts

- Endpoint: `https://upkeep.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.3`

## 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-25.

- **Endpoint Security**: 78/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 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.
  - 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5048 tokens (~174/item across 29 items; 29 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% 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.
  - We read all 29 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 30 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 UpKeep MCP by usefulapi server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-upkeep": {
      "type": "http",
      "url": "https://upkeep.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-25 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.2.0 → 1.2.3

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

First indexed and scored.

## MCP tools (29)

### `upkeep_get_account` (~53 tokens)

Check API token

Confirm the UpKeep API token is active: returns the company id, the token's name, when it was created and when it was last used. GET /api/v1/organization-api-tokens/introspect.

### `upkeep_list_work_orders` (~527 tokens)

List work orders

List work orders (reactive and preventive), newest first, with status, priority, due date, asset, location, assignee, parts, time and cost. Filter by status, completion, priority, category, asset, location, assignee, title or date ranges. GET /work-orders.

Input parameters:

- `archived` (boolean): true = only archived work orders.
- `asset` (string): Only records for this asset id.
- `assigned_by_user` (string): Only records for this assigning user id.
- `assigned_to_user` (string): Only records for this assigned user id.
- `category` (string): Only this work order category (e.g. Electrical).
- `completed_after` (string): Completed at or after this time. ISO 8601.
- `completed_before` (string): Completed at or before this time. ISO 8601.
- `created_after` (string): Created at or after this time. ISO 8601.
- `created_before` (string): Created at or before this time. ISO 8601.
- `due_after` (string): Due at or after this time. ISO 8601.
- `due_before` (string): Due at or before this time. ISO 8601.
- `includes` (array): Expand referenced records inline instead of returning ids. Allowed: asset, location, assignedToUser, assignedByUser, requestedByUser, completedByUser, team.
- `is_complete` (boolean): true = only completed work orders, false = only not yet completed.
- `limit` (integer): Records per page, 1-100 (default 25).
- `location` (string): Only records for this location id.
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort: "<field> ASC|DESC" with field one of createdAt, updatedAt, dueDate, endDueDate, dateCompleted (default "createdAt DESC").
- `priority` (integer): Priority: 0 none/lowest, 1 low, 2 medium, 3 high.
- `public_requester_email` (string): Only work orders created by this email through the request portal.
- `status` (string): Only work orders in this status.
- `title` (string): Only work orders with exactly this title.
- `updated_after` (string): Updated at or after this time. ISO 8601.
- `updated_before` (string): Updated at or before this time. ISO 8601.

### `upkeep_get_work_order` (~103 tokens)

Get work order

One work order by id with its checklist items, custom fields, time log, parts and files. GET /work-orders/{id}.

Input parameters:

- `includes` (array): Expand referenced records inline instead of returning ids. Allowed: asset, location, assignedToUser, assignedByUser, requestedByUser, completedByUser, team.
- `work_order_id` (string, required): UpKeep work order id (a short string such as "HW2I379ErS").

### `upkeep_list_assets` (~353 tokens)

List assets

List assets (equipment) with name, model, serial and barcode, location, status, downtime status, warranty and number of open work orders. Filter by name, serial number, barcode, location, status, category or assignee. GET /assets.

Input parameters:

- `assigned_to_user` (string): Only records for this assigned user id.
- `barcode` (string): Only the asset with this barcode number.
- `category` (string): Only assets in this category.
- `created_after` (string): Created at or after this time. ISO 8601.
- `created_before` (string): Created at or before this time. ISO 8601.
- `downtime_status` (string): Only assets with this downtime status id.
- `includes` (array): Expand referenced records inline instead of returning ids. Allowed: location, parentAsset, createdByUser, assignedToUser.
- `limit` (integer): Records per page, 1-100 (default 25).
- `location` (string): Only records for this location id.
- `name` (string): Only assets with exactly this name.
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort: "<field> ASC|DESC" with field one of createdAt, updatedAt (default "createdAt DESC").
- `serial_number` (string): Only the asset with this serial number.
- `status` (string): Only assets with this status (active or inactive).
- `updated_after` (string): Updated at or after this time. ISO 8601.
- `updated_before` (string): Updated at or before this time. ISO 8601.

### `upkeep_get_asset` (~124 tokens)

Get asset

One asset by id with purchase and warranty details, custom fields and (optionally) assigned users, teams, vendors, parts, files and sub-assets. GET /assets/{id}.

Input parameters:

- `asset_id` (string, required): UpKeep asset id (a short string such as "HW2I379ErS").
- `includes` (array): Expand referenced records inline instead of returning ids. Allowed: assignedUsers, assignedTeams, assignedCustomers, assignedVendors, formItems, files, parts, subAssets, location, parentAsset, create…

### `upkeep_list_locations` (~283 tokens)

List locations

List locations (sites, buildings, rooms) with address, barcode, parent location and hierarchy level. GET /locations.

Input parameters:

- `barcode` (string): Only the location with this barcode.
- `created_after` (string): Created at or after this time. ISO 8601.
- `created_before` (string): Created at or before this time. ISO 8601.
- `hierarchy_level` (integer): Only this hierarchy level (0 = top level, up to 5).
- `includes` (array): Expand referenced records inline instead of returning ids. Allowed: createdByUser, parentLocation, hierarchyLevel, ancestors, numTotalChildren, numTotalDescendants.
- `limit` (integer): Records per page, 1-100 (default 25).
- `name` (string): Only locations with exactly this name.
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort: "<field> ASC|DESC" with field one of createdAt, updatedAt (default "createdAt DESC").
- `parent_location` (string): Only records for this parent location id.
- `updated_after` (string): Updated at or after this time. ISO 8601.
- `updated_before` (string): Updated at or before this time. ISO 8601.

### `upkeep_get_location` (~45 tokens)

Get location

One location by id. GET /locations/{id}.

Input parameters:

- `location_id` (string, required): UpKeep location id (a short string such as "HW2I379ErS").

### `upkeep_list_parts` (~268 tokens)

List parts (inventory)

List spare parts with quantity on hand, minimum quantity, cost, category, location and part number. Compare quantity with minimumQuantity to find parts to reorder. GET /parts.

Input parameters:

- `category` (string): Only parts in this category.
- `created_after` (string): Created at or after this time. ISO 8601.
- `created_before` (string): Created at or before this time. ISO 8601.
- `includes` (array): Expand referenced records inline instead of returning ids. Allowed: location, createdByUser.
- `limit` (integer): Records per page, 1-100 (default 25).
- `location` (string): Only records for this location id.
- `name` (string): Only parts with exactly this name.
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort: "<field> ASC|DESC" with field one of createdAt, updatedAt (default "createdAt DESC").
- `part_number` (string): Only parts with this part number.
- `updated_after` (string): Updated at or after this time. ISO 8601.
- `updated_before` (string): Updated at or before this time. ISO 8601.

### `upkeep_get_part` (~54 tokens)

Get part

One part by id with quantity, cost, location and custom fields. GET /parts/{id}.

Input parameters:

- `part_id` (string, required): UpKeep part id (a short string such as "HW2I379ErS").

### `upkeep_list_meters` (~254 tokens)

List meters

List meters (usage counters such as hours, mileage, temperature) with units, reading frequency and the asset or location they belong to. GET /meters.

Input parameters:

- `asset` (string): Only records for this asset id.
- `created_after` (string): Created at or after this time. ISO 8601.
- `created_before` (string): Created at or before this time. ISO 8601.
- `includes` (array): Expand referenced records inline instead of returning ids. Allowed: asset, location, createdByUser.
- `limit` (integer): Records per page, 1-100 (default 25).
- `location` (string): Only records for this location id.
- `name` (string): Only meters with exactly this name.
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort: "<field> ASC|DESC" with field one of createdAt, updatedAt (default "createdAt DESC").
- `updated_after` (string): Updated at or after this time. ISO 8601.
- `updated_before` (string): Updated at or before this time. ISO 8601.

### `upkeep_get_meter` (~45 tokens)

Get meter

One meter by id. GET /meters/{id}.

Input parameters:

- `meter_id` (string, required): UpKeep meter id (a short string such as "HW2I379ErS").

### `upkeep_list_meter_readings` (~176 tokens)

List meter readings

Readings recorded for one meter (value, date, who recorded it), newest first. GET /meters/{id}/readings.

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).
- `meter_id` (string, required): UpKeep meter id (a short string such as "HW2I379ErS").
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort: "<field> ASC|DESC" with field one of createdAt, updatedAt (default "createdAt DESC").
- `read_after` (string): Reading date at or after this time. ISO 8601.
- `read_before` (string): Reading date at or before this time. ISO 8601.

### `upkeep_add_meter_reading` (~118 tokens)

Add meter reading

WRITE: record a new reading on a meter (for example engine hours or mileage). A reading cannot be removed with this server, and a meter notification can create a work order automatically when its condition is met. POST /meters/{id}/readings.

Input parameters:

- `date` (string): When the reading was taken (ISO 8601). Defaults to now.
- `meter_id` (string, required): UpKeep meter id (a short string such as "HW2I379ErS").
- `value` (number, required): The reading value.

### `upkeep_list_requests` (~345 tokens)

List work requests

List work requests submitted by staff or through the request portal (before they become work orders), with status open/approved/rejected. GET /requests.

Input parameters:

- `asset` (string): Only records for this asset id.
- `assigned_to_user` (string): Only records for this assigned user id.
- `category` (string): Only this request category.
- `created_after` (string): Created at or after this time. ISO 8601.
- `created_before` (string): Created at or before this time. ISO 8601.
- `includes` (array): Expand referenced records inline instead of returning ids. Allowed: asset, location, team, assignedToUser, assignedByUser, cancelledByUser.
- `limit` (integer): Records per page, 1-100 (default 25).
- `location` (string): Only records for this location id.
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort: "<field> ASC|DESC" with field one of createdAt, updatedAt, dueDate, endDueDate (default "createdAt DESC").
- `public_requester_email` (string): Only requests sent by this email through the request portal.
- `request_status` (string): Only requests in this state.
- `requested_by_user` (string): Only records for this requesting user id.
- `team` (string): Only records for this team id.
- `updated_after` (string): Updated at or after this time. ISO 8601.
- `updated_before` (string): Updated at or before this time. ISO 8601.

### `upkeep_get_request` (~60 tokens)

Get work request

One work request by id with its form fields and, once approved, the linked work order id. GET /requests/{id}.

Input parameters:

- `request_id` (string, required): UpKeep request id (a short string such as "HW2I379ErS").

### `upkeep_create_request` (~215 tokens)

Create work request

WRITE: submit a new work request for the maintenance team to approve (it appears in UpKeep's Requests list and may notify the approvers or the assignee). It is not a work order until approved. If the account has a request form configured, pass its field labels in `fields`. POST /requests.

Input parameters:

- `asset` (string): Asset id.
- `assigned_to_user` (string): User id to assign.
- `category` (string): Must be one of the account's configured categories.
- `description` (string)
- `due_date` (string): Due date, ISO 8601.
- `fields` (array): Request form values: each name must match a field label on the account's request form.
- `location` (string): Location id.
- `priority` (integer): Priority: 0 none/lowest, 1 low, 2 medium, 3 high.
- `team` (string): Team id.
- `title` (string, required): Short title, e.g. Repair sink.

### `upkeep_approve_request` (~91 tokens)

Approve work request

WRITE: approve a pending work request, which converts it into a work order (it may notify the assignee). Needs a token whose role may approve requests. Approving a request that is already approved or declined fails with HTTP 409. POST /requests/{id}/approve.

Input parameters:

- `request_id` (string, required): UpKeep request id (a short string such as "HW2I379ErS").

### `upkeep_create_work_order` (~190 tokens)

Create work order

WRITE: create a new work order (it may notify the assignee and appears in UpKeep's work order board). Ids for asset, location and assignee come from the list tools. POST /work-orders.

Input parameters:

- `asset` (string): Asset id.
- `assigned_to_user` (string): User id to assign.
- `category` (string): Must be one of the account's configured work order categories.
- `description` (string)
- `due_date` (string): Due date, ISO 8601.
- `estimated_duration_hours` (number)
- `location` (string): Location id.
- `priority` (integer): Priority: 0 none/lowest, 1 low, 2 medium, 3 high.
- `start_date` (string): Start date, ISO 8601.
- `title` (string, required): Short title, e.g. Repair sink.

### `upkeep_update_work_order` (~184 tokens)

Update work order

WRITE: change fields of an existing work order: status (open, onHold, inProgress, complete), title, description, priority, due date or assignee. Only the fields you pass change; completing a work order may trigger the account's integrations (for example Zapier). Archiving and deleting are not offered. PATCH /work-orders/{id}.

Input parameters:

- `assigned_to_user` (string): User id to assign.
- `description` (string)
- `due_date` (string): Due date, ISO 8601.
- `priority` (integer): Priority: 0 none/lowest, 1 low, 2 medium, 3 high.
- `status` (string)
- `title` (string)
- `work_order_id` (string, required): UpKeep work order id (a short string such as "HW2I379ErS").

### `upkeep_add_work_order_message` (~84 tokens)

Add work order message

WRITE: post a message (comment) on a work order's activity thread; people following the work order may be notified. POST /work-orders/{id}/update-messages.

Input parameters:

- `text` (string, required): The message text.
- `work_order_id` (string, required): UpKeep work order id (a short string such as "HW2I379ErS").

### `upkeep_update_part_quantity` (~113 tokens)

Update part quantity

WRITE: set the quantity on hand (and optionally the minimum quantity that triggers a low-stock notification) of a part. This overwrites the stored number: read the part first and pass the new total, not the difference. PATCH /parts/{id}.

Input parameters:

- `minimum_quantity` (number): New low-stock threshold.
- `part_id` (string, required): UpKeep part id (a short string such as "HW2I379ErS").
- `quantity` (number, required): The new quantity on hand (a total).

### `upkeep_list_users` (~222 tokens)

List users

List UpKeep users (technicians, admins, requesters) with account type, job title, status and last login. Use the ids to assign work orders. GET /users.

Input parameters:

- `account_type` (string): Only users with this account type.
- `created_after` (string): Created at or after this time. ISO 8601.
- `created_before` (string): Created at or before this time. ISO 8601.
- `email` (string): Only the user with this email.
- `limit` (integer): Records per page, 1-100 (default 25).
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort: "<field> ASC|DESC" with field one of createdAt, updatedAt (default "createdAt DESC").
- `updated_after` (string): Updated at or after this time. ISO 8601.
- `updated_before` (string): Updated at or before this time. ISO 8601.

### `upkeep_get_user` (~45 tokens)

Get user

One user by id. GET /users/{id}.

Input parameters:

- `user_id` (string, required): UpKeep user id (a short string such as "HW2I379ErS").

### `upkeep_list_teams` (~82 tokens)

List teams

List teams with name and description. Use the ids to assign work. GET /teams.

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).
- `name` (string): Only teams with exactly this name.
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.

### `upkeep_list_vendors` (~82 tokens)

List vendors

List vendors (suppliers and contractors) with contact details. GET /vendors.

Input parameters:

- `business_name` (string): Only vendors with exactly this business name.
- `limit` (integer): Records per page, 1-100 (default 25).
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.

### `upkeep_list_customers` (~84 tokens)

List customers

List customers (the parties whose assets or locations you maintain) with contact details. GET /customers.

Input parameters:

- `limit` (integer): Records per page, 1-100 (default 25).
- `name` (string): Only customers with exactly this name.
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.

### `upkeep_list_purchase_orders` (~328 tokens)

List purchase orders

List purchase orders with status (awaiting, approved, declined, fulfilled), vendor, dates, total cost and quantities. GET /purchase-orders.

Input parameters:

- `category` (string): Only this purchase order category.
- `created_after` (string): Created at or after this time. ISO 8601.
- `created_before` (string): Created at or before this time. ISO 8601.
- `due_after` (string): Due at or after this time. ISO 8601.
- `due_before` (string): Due at or before this time. ISO 8601.
- `includes` (array): Expand referenced records inline instead of returning ids. Allowed: vendor, createdByUser, approvedByUser, fulfilledByUser, declinedByUser.
- `limit` (integer): Records per page, 1-100 (default 25).
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort: "<field> ASC|DESC" with field one of createdAt, updatedAt, dueDate, poDate, fulfilledAt, approvedAt, declinedAt (default "createdAt DESC").
- `status` (string): Only purchase orders in this status.
- `title` (string): Only purchase orders with exactly this title.
- `updated_after` (string): Updated at or after this time. ISO 8601.
- `updated_before` (string): Updated at or before this time. ISO 8601.
- `vendor` (string): Only records for this vendor id.

### `upkeep_get_purchase_order` (~60 tokens)

Get purchase order

One purchase order by id with its parts, quantities, costs and shipping details. GET /purchase-orders/{id}.

Input parameters:

- `purchase_order_id` (string, required): UpKeep purchase order id (a short string such as "HW2I379ErS").

### `upkeep_list_preventive_maintenance` (~208 tokens)

List preventive maintenance plans

List preventive maintenance (PM) templates, the recurring work that generates scheduled work orders, with their schedules. Filter by text, asset, location, assignee, team or priority. Pages are 1-based. GET /pm.

Input parameters:

- `asset` (string): Only records for this asset id.
- `assignee` (string): Only records for this assigned user id.
- `include_schedules` (boolean): Also return each PM's schedules.
- `location` (string): Only records for this location id.
- `page` (integer): Page number from 1 (default 1).
- `page_size` (integer): PMs per page, 1-100 (default 25).
- `priority` (integer): Priority: 0 none/lowest, 1 low, 2 medium, 3 high.
- `search` (string): Text to find in the PM's name or description.
- `team` (string): Only records for this team id.

## Diagnostics

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

## Score history

- 2026-10-25: 62
- 2026-10-24: 62

## Common questions

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

UpKeep MCP by usefulapi is listed in the public MCP registry as io.usefulapi/upkeep. Read UpKeep work orders, assets, parts and meters; create requests and work orders. This page covers its hosted endpoint (https://upkeep.usefulapi.io/mcp).

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

UpKeep MCP by usefulapi scores 62 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 UpKeep MCP by usefulapi server expose?

UpKeep MCP by usefulapi exposes 29 tools: upkeep_get_account, upkeep_list_work_orders, upkeep_get_work_order, upkeep_list_assets, upkeep_get_asset, and 24 more. Their descriptions and schemas cost roughly 4,796 tokens of context every time the server is loaded.

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

Yes. UpKeep 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 UpKeep MCP by usefulapi server still maintained?

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