Tamigo MCP by usefulapi
REMOTE · TAMIGO.USEFULAPI.IO
Read Tamigo departments, employees, shifts, absences and opening hours; register attendance.
Available components
Last scanned (3 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Project Management
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.2.0 → 1.2.3 functional
- 24 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 25 Oct 2026 · Probed https://tamigo.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 tamigo.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://tamigo.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://tamigo.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://tamigo.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://tamigo.usefulapi.io/mcp |
| Authorisation server | https://tamigo.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tamigo.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/tamigo/ |
| http (plaintext) | http://tamigo.usefulapi.io/mcp | Inconclusive | 302 | http://tamigo.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 →
tamigo_get_opening_hours Get opening hours ~115
Normal and special opening hours per department for a date range. GET /OpeningHours/{start}/{end}/.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | 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 | yes | First day, yyyy-mm-dd. |
No output schema declared.
No examples provided.
tamigo_list_absences List absences ~134
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | 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 | yes | First day, yyyy-mm-dd. |
No output schema declared.
No examples provided.
tamigo_list_departments List departments ~142
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
tamigo_list_employee_details List employee details ~185
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
tamigo_list_employees List employees ~119
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
tamigo_list_shifts List shifts (original, planned, worked) ~185
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}/.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | string | – | Department id from tamigo_list_departments. Omit for all departments. |
| end_date | string | yes | 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 | yes | First day, yyyy-mm-dd. |
No output schema declared.
No examples provided.
tamigo_register_attendance Register check-ins / check-outs ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entries | array | yes | 1-50 entries, in chronological order. |
No output schema declared.
No examples provided.
tamigo_upload_daily_revenue Upload daily revenue ~112
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| rows | array | yes | 1-200 rows. |
No output schema declared.
No examples provided.
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.
remote · tamigo.usefulapi.io
claude mcp add --transport http io-usefulapi-tamigo 'https://tamigo.usefulapi.io/mcp'
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.