# Tamigo MCP by usefulapi (remote · tamigo.usefulapi.io)

Read Tamigo departments, employees, shifts, absences and opening hours; register attendance.

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

## Components

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

## Channel facts

- Endpoint: `https://tamigo.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**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1435 tokens (~179/item across 8 items; 8 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**: 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.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 Tamigo MCP by usefulapi server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-tamigo": {
      "type": "http",
      "url": "https://tamigo.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 (8)

### `tamigo_list_departments` (~142 tokens)

List departments

List all departments (shops, restaurants, units) of the company: DepartmentId (a GUID, used by other tools), DepartmentKey (the POS key set in Tamigo), Name, IsDefault and ParentDepartmentId. GET /departments/application/.

Input parameters:

- `include_parents` (boolean): Also return the parent (grouping) departments, not only the leaf units. Default false.
- `limit` (integer): Items to return, 1-1000 (default 200). The reply's next_offset says where to continue.
- `offset` (integer): Skip this many items (default 0). Pass the previous reply's next_offset.

### `tamigo_list_employees` (~119 tokens)

List employees

List all employees of the company (basic): EmployeeId, Name, Email, IsPlanner, PosKey (the employee key used by the attendance tool) and DepartmentRoles. For contract, wage and absence-balance details use tamigo_list_employee_details. GET /employees/.

Input parameters:

- `limit` (integer): Items to return, 1-1000 (default 200). The reply's next_offset says where to continue.
- `offset` (integer): Skip this many items (default 0). Pass the previous reply's next_offset.

### `tamigo_list_employee_details` (~185 tokens)

List employee details

Detailed employee records, 500 per page in alphabetical order: contact data, roles per department, home department, contract hours, wage type and history, absence balances, competencies, custom columns, notes and availability. Bank details and ID numbers are never returned. Large pages are returned in slices: pass the reply's next_page and next_offset to continue. GET /employees/getemployeedetails/.

Input parameters:

- `include_deleted` (boolean): Also include deleted employees. Default false.
- `limit` (integer): Items to return, 1-500 (default 50). The reply's next_offset says where to continue.
- `offset` (integer): Skip this many employees within the page (default 0). Pass the previous reply's next_offset.
- `page` (integer): Page number, from 0 (default 0). Pass the previous reply's next_page.

### `tamigo_list_shifts` (~185 tokens)

List shifts (original, planned, worked)

Per employee and day, the original rota, the planned (current) rota and the worked (timesheet) hours for a date range, with department, employee POS key, email and wage number. Use it for payroll checks, hours worked vs planned and who worked when. Shift values are hours. GET /shifts/all/{start}/{end}/.

Input parameters:

- `department_id` (string): Department id from tamigo_list_departments. Omit for all departments.
- `end_date` (string, required): Last day, yyyy-mm-dd.
- `limit` (integer): Items to return, 1-1000 (default 200). The reply's next_offset says where to continue.
- `offset` (integer): Skip this many items (default 0). Pass the previous reply's next_offset.
- `start_date` (string, required): First day, yyyy-mm-dd.

### `tamigo_list_absences` (~134 tokens)

List absences

All absences (holiday, sickness, leave) that overlap a date range: employee, department, absence type, start and end, and whether it is approved or rejected. GET /LeaveRequests/All/.

Input parameters:

- `end_date` (string, required): Last day, yyyy-mm-dd.
- `limit` (integer): Items to return, 1-1000 (default 200). The reply's next_offset says where to continue.
- `offset` (integer): Skip this many items (default 0). Pass the previous reply's next_offset.
- `start_date` (string, required): First day, yyyy-mm-dd.

### `tamigo_get_opening_hours` (~115 tokens)

Get opening hours

Normal and special opening hours per department for a date range. GET /OpeningHours/{start}/{end}/.

Input parameters:

- `end_date` (string, required): Last day, yyyy-mm-dd.
- `limit` (integer): Items to return, 1-1000 (default 200). The reply's next_offset says where to continue.
- `offset` (integer): Skip this many items (default 0). Pass the previous reply's next_offset.
- `start_date` (string, required): First day, yyyy-mm-dd.

### `tamigo_register_attendance` (~186 tokens)

Register check-ins / check-outs

WRITE: register check-in and check-out times in the Tamigo timesheet, for one or many employees (the same call a POS system makes). Each entry names a department key and an employee key (the POS keys set in Tamigo under Configuration -> Departments / POS Keys; they are shown by tamigo_list_departments and tamigo_list_employees) and EITHER a check_in_time OR a check_out_time, in chronological order per employee. A break is registered by giving the same activity_name (for example Lunch, SmallBreak) on its check-in and its check-out. Tamigo may round the times by the company's rules, and the reply echoes the times actually registered. This changes worked hours and wages: it is not undone by repeating it, so confirm the entries first.

Input parameters:

- `entries` (array, required): 1-50 entries, in chronological order.

### `tamigo_upload_daily_revenue` (~112 tokens)

Upload daily revenue

WRITE: import daily revenue per department into Tamigo (the same call a cash-register system makes), used for revenue-based planning and KPIs. Each row is a department key (the POS key set in Tamigo), a date and a revenue amount (a plain number with a dot as decimal separator). A date that already has revenue for that department may be overwritten by Tamigo, so confirm the rows first. POST /Revenues/.

Input parameters:

- `rows` (array, required): 1-200 rows.

## Diagnostics

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

## Score history

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

## Common questions

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

Tamigo MCP by usefulapi is listed in the public MCP registry as io.usefulapi/tamigo. Read Tamigo departments, employees, shifts, absences and opening hours; register attendance. This page covers its hosted endpoint (https://tamigo.usefulapi.io/mcp).

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

Tamigo 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 Tamigo MCP by usefulapi server expose?

Tamigo MCP by usefulapi exposes 8 tools: tamigo_list_departments, tamigo_list_employees, tamigo_list_employee_details, tamigo_list_shifts, tamigo_list_absences, and 3 more. Their descriptions and schemas cost roughly 1,178 tokens of context every time the server is loaded.

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

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

Tamigo 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://tamigo.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/tamigo/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-tamigo/tamigo.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-tamigo/tamigo.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-tamigo/tamigo