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

Check devices, alerts and tickets in Atera, and open tickets, comment or resolve alerts.

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

## Components

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

## Channel facts

- Endpoint: `https://atera.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-03.

- **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**: 82/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2156 tokens (~107/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**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - 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/atera MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-atera": {
      "type": "http",
      "url": "https://atera.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 78, +1)

- [functional] Server version: 1.3.0 → 1.5.1

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

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

### 2026-09-30 (score 72, +13)

- [security improvement] Authorization: unverified → pass
- [security] First check of Authorization: partial
- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (20)

### `atera_get_account` (~48 tokens)

Get the account

Fetch the Atera account this key belongs to — company name, plan, country and timezone. A cheap way to confirm the key works. Atera: GET /api/v3/account.

### `atera_list_customers` (~75 tokens)

List customers

List the customers (client companies) managed in Atera, paginated. Atera: GET /api/v3/customers.

Input parameters:

- `items_in_page` (integer): Items per page, 1-500 (default 20).
- `page` (integer): Page number, 1-based (default 1).

### `atera_get_customer` (~51 tokens)

Get one customer

Fetch a single customer by id — address, domain, phone, notes. Atera: GET /api/v3/customers/{customerId}.

Input parameters:

- `customer_id` (integer, required): The customer's CustomerID.

### `atera_list_agents` (~117 tokens)

List agents (devices)

List Atera agents — the managed machines — with online status, last seen, OS, hardware and logged-in user. Pass customer_id to list only one customer's devices. Atera: GET /api/v3/agents or GET /api/v3/agents/customer/{customerId}.

Input parameters:

- `customer_id` (integer): Only this customer's agents.
- `items_in_page` (integer): Items per page, 1-500 (default 20).
- `page` (integer): Page number, 1-based (default 1).

### `atera_get_agent` (~62 tokens)

Get one agent (device)

Fetch a single agent by its AgentID — full device inventory, online status, IPs, OS build and last reboot. Atera: GET /api/v3/agents/{agentId}.

Input parameters:

- `agent_id` (integer, required): The agent's AgentID.

### `atera_find_agents_by_machine` (~106 tokens)

Find agents by machine name

Find the agent(s) installed on a machine by its machine name, e.g. DESKTOP-4F2K9. Atera: GET /api/v3/agents/machine/{machineName}.

Input parameters:

- `items_in_page` (integer): Items per page, 1-500 (default 20).
- `machine_name` (string, required): The machine (computer) name.
- `page` (integer): Page number, 1-based (default 1).

### `atera_get_agent_patches` (~114 tokens)

Get an agent's patches

List the Windows/OS patches on one device — either those still AVAILABLE (missing) or those already INSTALLED. Takes the device's DeviceGuid (from atera_list_agents / atera_get_agent), not the AgentID. Atera: GET /api/v3/agents/{deviceGuid}/available-patches or /installed-patches.

Input parameters:

- `device_guid` (string, required): The device's DeviceGuid.
- `kind` (string): available = patches not yet installed (default); installed = patch history.

### `atera_list_alerts` (~99 tokens)

List alerts

List monitoring alerts (disk, CPU, availability, hardware...) with severity, device, customer and linked ticket. Filter by status. Atera: GET /api/v3/alerts.

Input parameters:

- `alert_status` (string): Only alerts in this state.
- `items_in_page` (integer): Items per page, 1-500 (default 20).
- `page` (integer): Page number, 1-based (default 1).

### `atera_list_tickets` (~145 tokens)

List tickets

List helpdesk tickets with priority, status, type, end user, technician, SLA durations and last comments. Filter by customer and/or status. Atera: GET /api/v3/tickets.

Input parameters:

- `customer_id` (integer): Only this customer's tickets.
- `include_relations` (boolean): Include parent/child ticket relation info.
- `items_in_page` (integer): Items per page, 1-50 (default 20).
- `page` (integer): Page number, 1-based (default 1).
- `ticket_status` (string): Ticket status name, e.g. Open, Pending, Resolved or Closed (or a custom status).

### `atera_get_ticket` (~62 tokens)

Get one ticket

Fetch a single ticket by its TicketID. Atera: GET /api/v3/tickets/{ticketId}.

Input parameters:

- `include_relations` (boolean): Include parent/child ticket relation info.
- `ticket_id` (integer, required): The ticket's TicketID.

### `atera_list_ticket_comments` (~97 tokens)

List a ticket's comments

List the comment thread on one ticket — end-user and technician replies, with internal notes flagged. Atera: GET /api/v3/tickets/{ticketId}/comments.

Input parameters:

- `items_in_page` (integer): Items per page, 1-50 (default 20).
- `page` (integer): Page number, 1-based (default 1).
- `ticket_id` (integer, required): The ticket's TicketID.

### `atera_list_ticket_work_hours` (~103 tokens)

List a ticket's work hours

List the time entries logged on one ticket — technician, start/end, billable, on-site, rate. Atera: GET /api/v3/tickets/{ticketId}/workhoursrecords.

Input parameters:

- `items_in_page` (integer): Items per page, 1-50 (default 20).
- `page` (integer): Page number, 1-based (default 1).
- `ticket_id` (integer, required): The ticket's TicketID.

### `atera_list_contacts` (~102 tokens)

List contacts

List end-user contacts, optionally searching by whole or partial email or phone number. Atera: GET /api/v3/contacts.

Input parameters:

- `email` (string): Whole or partial email to match.
- `items_in_page` (integer): Items per page, 1-500 (default 20).
- `page` (integer): Page number, 1-based (default 1).
- `phone` (string): Whole or partial phone number to match.

### `atera_list_contracts` (~112 tokens)

List contracts

List service contracts (retainer, block hours, hourly, remote monitoring...) with their rates and billing periods. Pass customer_id for one customer's contracts. Atera: GET /api/v3/contracts or GET /api/v3/contracts/customer/{customerId}.

Input parameters:

- `customer_id` (integer): Only this customer's contracts.
- `items_in_page` (integer): Items per page, 1-500 (default 20).
- `page` (integer): Page number, 1-based (default 1).

### `atera_list_kb_articles` (~78 tokens)

List knowledge-base articles

List knowledge-base articles with their product, keywords, section, category and ratings. Atera: GET /api/v3/knowledgebases.

Input parameters:

- `items_in_page` (integer): Items per page, 1-500 (default 20).
- `page` (integer): Page number, 1-based (default 1).

### `atera_create_ticket` (~239 tokens)

Create a ticket

Open a new helpdesk ticket. Give either end_user_id (an existing contact's EndUserID) or all of end_user_first_name, end_user_last_name and end_user_email to create a new contact with it. Atera: POST /api/v3/tickets.

Input parameters:

- `description` (string, required): Ticket description (first comment).
- `end_user_email` (string): New contact's email.
- `end_user_first_name` (string): New contact's first name.
- `end_user_id` (integer): Existing contact's EndUserID.
- `end_user_last_name` (string): New contact's last name.
- `end_user_phone` (string): New contact's phone.
- `impact` (string)
- `priority` (string)
- `status` (string): Ticket status name, e.g. Open, Pending, Resolved or Closed (or a custom status).
- `technician_contact_id` (integer): Assign to this technician (TechnicianContactID).
- `technician_email` (string): Assign to the technician with this email.
- `title` (string, required): Ticket title.
- `type` (string)

### `atera_update_ticket` (~154 tokens)

Update a ticket

Change a ticket's title, status, type, priority, impact or assigned technician. Only the fields you pass are sent. Atera: PUT /api/v3/tickets/{ticketId}.

Input parameters:

- `impact` (string)
- `priority` (string)
- `status` (string): Ticket status name, e.g. Open, Pending, Resolved or Closed (or a custom status).
- `technician_contact_id` (integer): Reassign to this technician (TechnicianContactID).
- `technician_email` (string): Reassign to the technician with this email.
- `ticket_id` (integer, required): The ticket's TicketID.
- `title` (string): New title.
- `type` (string)

### `atera_add_ticket_comment` (~194 tokens)

Comment on a ticket

Add a comment to a ticket, either as a technician (technician_id, with is_internal=true for a private note or false for a reply the end user sees) or on behalf of an end user (enduser_id). Atera: POST /api/v3/tickets/{ticketId}/comments.

Input parameters:

- `comment` (string, required): The comment text.
- `enduser_id` (integer): Post as this end-user contact (EndUserID).
- `is_internal` (boolean): Technician comments only: true = internal note (default), false = visible reply.
- `technician_email` (string): The technician's email (optional, with technician_id).
- `technician_id` (integer): Post as this technician (TechnicianId).
- `ticket_id` (integer, required): The ticket's TicketID.
- `timestamp_utc` (string): Comment time in UTC, ISO 8601. Defaults to now.

### `atera_create_contact` (~137 tokens)

Create a contact

Create a new end-user contact under an existing customer (give customer_id or customer_name). Atera: POST /api/v3/contacts.

Input parameters:

- `customer_id` (integer): The customer's CustomerID.
- `customer_name` (string): The customer's name, if you don't have the id.
- `email` (string, required): The contact's email (required).
- `first_name` (string)
- `is_contact_person` (boolean): Mark as the customer's primary contact person.
- `job_title` (string)
- `last_name` (string)
- `mobile_phone` (string)
- `phone` (string)

### `atera_resolve_alert` (~61 tokens)

Resolve an alert

Mark one monitoring alert as resolved. If the underlying condition persists, Atera raises it again on the next check. Atera: PUT /api/v3/alerts/{alertId}.

Input parameters:

- `alert_id` (integer, required): The alert's AlertID.

## Diagnostics

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

## Score history

- 2026-10-03: 78
- 2026-10-02: 78
- 2026-10-01: 77
- 2026-09-30: 72
- 2026-09-29: 59

## Common questions

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

io.usefulapi/atera is an MCP server listed in the public MCP registry as io.usefulapi/atera. Check devices, alerts and tickets in Atera, and open tickets, comment or resolve alerts. This page covers its hosted endpoint (https://atera.usefulapi.io/mcp).

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

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

io.usefulapi/atera exposes 20 tools: atera_get_account, atera_list_customers, atera_get_customer, atera_list_agents, atera_get_agent, and 15 more. Their descriptions and schemas cost roughly 2,156 tokens of context every time the server is loaded.

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

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

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