Skip to content

Tamigo MCP by usefulapi

io.usefulapi/tamigousefulapi.iostreamable-httpv1.21.4Scanned

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

8 tools: 2 can delete or cancel things and 6 only read.

Tools: 2 delete, 0 irreversible, 0 write, 6 read.
  • Reads private data · 3
  • Reads text others write · 8
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Tamigo MCP by usefulapi can do

The Tamigo MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (2 tools: tamigo_register_attendance and tamigo_upload_daily_revenue). 6 tools only read.

3 tools read private data (tamigo_list_employees, tamigo_list_employee_details and tamigo_list_shifts); 8 tools bring in text other people can write (tamigo_list_departments, tamigo_list_employees, tamigo_list_employee_details and 5 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.21.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Deletes or cancels 2Claude Code: deny
  • tamigo_register_attendanceWRITE: register check-in and check-out times in the Tamigo timesheet, for one or many employees (the same call a POS system makes).Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "write": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Register check-ins / check-outs
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • tamigo_upload_daily_revenueWRITE: import daily revenue per department into Tamigo (the same call a cash-register system makes), used for revenue-based planning and KPIs.Reads text others writeNo findings

    Why it is in this group

    • The name "tamigo_upload_daily_revenue" says "upload": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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/.

    Annotations the server declares

    • title: Upload daily revenue
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Only reads 6Show 6 read-only tools
  • tamigo_get_opening_hoursNormal and special opening hours per department for a date range.Reads text others writeNo findings

    Why it is in this group

    • The name "tamigo_get_opening_hours" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Normal and special opening hours per department for a date range. GET /OpeningHours/{start}/{end}/.

    Annotations the server declares

    • title: Get opening hours
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • tamigo_list_absencesAll absences (holiday, sickness, leave) that overlap a date range: employee, department, absence type, start and end, and whether it is approved or rejected.Reads text others writeNo findings

    Why it is in this group

    • The name "tamigo_list_absences" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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/.

    Annotations the server declares

    • title: List absences
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • tamigo_list_departmentsList 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 ParentDe…Reads text others writeNo findings

    Why it is in this group

    • The name "tamigo_list_departments" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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/.

    Annotations the server declares

    • title: List departments
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • tamigo_list_employee_detailsDetailed employee records, 500 per page in alphabetical order: contact data, roles per department, home department, contract hours, wage type and history, absence balances, compete…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "tamigo_list_employee_details" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "contact": it reads contacts.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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/.

    Annotations the server declares

    • title: List employee details
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • tamigo_list_employeesList all employees of the company (basic): EmployeeId, Name, Email, IsPlanner, PosKey (the employee key used by the attendance tool) and DepartmentRoles.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "tamigo_list_employees" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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/.

    Annotations the server declares

    • title: List employees
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • tamigo_list_shiftsPer 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.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "tamigo_list_shifts" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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}/.

    Annotations the server declares

    • title: List shifts
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 15, 2026, 13:31 UTC, unchanged since Oct 31, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 31, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://tamigo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://tamigo.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://tamigo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://tamigo.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.21.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http tamigo https://tamigo.usefulapi.io/mcp
claude mcp add --transport http tamigo https://tamigo.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tamigo__tamigo_list_departments",
      "mcp__tamigo__tamigo_list_employees",
      "mcp__tamigo__tamigo_list_employee_details",
      "mcp__tamigo__tamigo_list_shifts",
      "mcp__tamigo__tamigo_list_absences",
      "mcp__tamigo__tamigo_get_opening_hours"
    ],
    "ask": [],
    "deny": [
      "mcp__tamigo__tamigo_register_attendance",
      "mcp__tamigo__tamigo_upload_daily_revenue"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tamigo. Review it before you use it.

Capability tags behind 8 rules
  • mcp__tamigo__tamigo_list_departments untrusted-input
  • mcp__tamigo__tamigo_list_employees private-data, untrusted-input
  • mcp__tamigo__tamigo_list_employee_details private-data, untrusted-input
  • mcp__tamigo__tamigo_list_shifts private-data, untrusted-input
  • mcp__tamigo__tamigo_list_absences untrusted-input
  • mcp__tamigo__tamigo_get_opening_hours untrusted-input
  • mcp__tamigo__tamigo_register_attendance untrusted-input
  • mcp__tamigo__tamigo_upload_daily_revenue untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/tamigo/verify?hash=e532a395d6e0133596f6693c3d99f65c6bb62117e55dea61d14bc3fc0704f79f" | jq -e '.changed == false'

Pinned hash e532a395d6e0, from Oct 25, 2026, 23:20 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/tamigo/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/tamigo
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/tamigo.svg)](https://radar.anlyon.com/servers/io.usefulapi/tamigo)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.

Tamigo MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Tamigo MCP by usefulapi safe?

No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Tamigo MCP by usefulapi delete data?

Yes. 2 tools can delete, cancel or revoke something: tamigo_register_attendance and tamigo_upload_daily_revenue.

Can the Tamigo MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Tamigo MCP by usefulapi have?

8 tools: 2 destructive, 6 read. tamigo_register_attendance, tamigo_upload_daily_revenue, tamigo_list_departments, tamigo_list_employees, tamigo_list_employee_details, tamigo_list_shifts, tamigo_list_absences and tamigo_get_opening_hours.

Does the Tamigo MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Tamigo MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Tamigo MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.