Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.glira/mcp-tomticket

NPM · MCP-TOMTICKET · SCANNED SEP 24

TomTicket helpdesk MCP: tickets, replies, time, customers, chats, and KB

Available components

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3853 tokens (~78/item across 49 items; 49 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 42% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "tomticket_transfer_ticket" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 49 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.glira/mcp-tomticket server?

io.github.glira/mcp-tomticket runs locally as an npm package, launched with npx -y mcp-tomticket. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-tomticket

# add to Claude Code
claude mcp add glira-mcp-tomticket -- npx -y mcp-tomticket
// .cursor/mcp.json
{
  "mcpServers": {
    "glira-mcp-tomticket": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-tomticket"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "glira-mcp-tomticket": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-tomticket"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add glira-mcp-tomticket -- npx -y mcp-tomticket
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "glira-mcp-tomticket": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-tomticket"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add glira-mcp-tomticket --command npx --arg -y --arg mcp-tomticket
# ~/.hermes/config.yaml
mcp_servers:
  glira-mcp-tomticket:
    command: "npx"
    args: ["-y", "mcp-tomticket"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "glira-mcp-tomticket": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-tomticket"
      ]
    }
  }
}
# add to Vellum
assistant mcp add glira-mcp-tomticket -t stdio -c npx -a -y mcp-tomticket
// mcp.json
{
  "mcpServers": {
    "glira-mcp-tomticket": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-tomticket"
      ]
    }
  }
}
Changelog

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.

  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 20 Sept 26 +1
    • Stability: 0.97 → pass security
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 24 Sept 2026 · Analysed npm/mcp-tomticket@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 49 exposed · ~3,853 tokens

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 →

Tool Tokens
tomticket_add_custom_field_option ~46

ATENCAO: altera producao. Adiciona opcao em campo personalizado.

NameTypeReqDescription
custom_field_idstringyes–
valuestringyes–

No output schema declared.

No examples provided.

tomticket_assign_operator ~50

ATENCAO: altera producao. Vincula um atendente ao chamado.

NameTypeReqDescription
operator_idstringyes–
ticket_idstringyesIdentificador do chamado (ticket_id).

No output schema declared.

No examples provided.

tomticket_check_email_blacklist ~38

Consulta se o email esta na blacklist de abertura de chamados por email. Nao altera dados.

NameTypeReqDescription
emailstringyes–

No output schema declared.

No examples provided.

tomticket_close_status ~49

ATENCAO: altera producao. Encerra o status aberto do chamado (para o cronometro).

NameTypeReqDescription
ticket_idstringyesIdentificador do chamado (ticket_id).

No output schema declared.

No examples provided.

tomticket_comment_ticket ~77

ATENCAO: altera producao. Adiciona comentario interno no chamado.

NameTypeReqDescription
attachmentsstring–Caminhos locais de anexos, separados por virgula. Maximo 25 arquivos / 25 MB.
commentstringyes–
ticket_idstringyesIdentificador do chamado (ticket_id).

No output schema declared.

No examples provided.

tomticket_create_article ~74

ATENCAO: altera producao. Cria artigo na base de conhecimento.

NameTypeReqDescription
category_idstringyes–
contentstringyesConteudo HTML do artigo.
display_orderinteger––
titlestringyes–
visibilitystringyesQuem pode ver o artigo.

No output schema declared.

No examples provided.

tomticket_create_customer ~134

ATENCAO: altera producao. Cria um novo cliente.

NameTypeReqDescription
create_ticketsinteger––
custom_fieldsstring–Campos personalizados JSON. Ex.: {"ID":"valor"}.
customer_idstringyesIdentificador interno (CPF, CNPJ ou chave do seu sistema).
emailstring––
languagestring–pt-BR, es_ES ou en-US.
namestringyes–
organization_idstring––
passwordstring––
phonestring––
portfolio_idstring––

No output schema declared.

No examples provided.

tomticket_create_organization ~161

ATENCAO: altera producao. Cria uma organizacao.

NameTypeReqDescription
create_ticketsinteger––
custom_fieldsstring–Campos personalizados JSON. Ex.: {"ID":"valor"}.
emailstring––
manager_see_all_ticketsinteger––
monthly_tickets_quotainteger––
mother_organization_idstring––
namestringyes–
phonestring––
portfolio_idstring––
return_id_if_existsstring––
sitestring––
strict_mailstring––
strict_namestring––
team_see_all_ticketsinteger––

No output schema declared.

No examples provided.

tomticket_create_ticket ~161

ATENCAO: altera producao. Cria um novo chamado no TomTicket.

NameTypeReqDescription
attachmentsstring–Caminhos locais de anexos, separados por virgula. Maximo 25 arquivos / 25 MB.
category_idstring––
custom_fieldsstring–Campos personalizados em JSON objeto. Ex.: {"ID_DO_CAMPO":"valor"}.
customer_idstringyesId interno ou email do cliente.
customer_id_typestring–I id interno, E email.
department_idstringyes–
messagestringyes–
priorityinteger–1 baixa, 2 normal, 3 alta, 4 urgente.
subjectstringyes–

No output schema declared.

No examples provided.

tomticket_customer_exists ~62

Verifica se o cliente existe por email ou id interno. Nao altera dados.

NameTypeReqDescription
customer_idstringyesId interno ou email do cliente.
customer_type_idstring–I = id interno, E = email. Padrao I.

No output schema declared.

No examples provided.

tomticket_customer_quick_access ~66

ATENCAO: gera token temporario (5 min) para o painel do cliente.

NameTypeReqDescription
customer_idstringyesId interno ou email do cliente.
customer_type_idstring–I = id interno, E = email. Padrao I.

No output schema declared.

No examples provided.

tomticket_evaluate_ticket ~119

ATENCAO: altera producao. Avalia um chamado ja finalizado.

NameTypeReqDescription
commentstring––
custom_fieldsstring–Campos personalizados em JSON objeto. Ex.: {"ID_DO_CAMPO":"valor"}.
gradeintegeryes5 otimo, 4 bom, 3 regular, 2 ruim, 1 pessimo.
problem_solvedinteger–1 se o problema foi resolvido.
ticket_idstringyesIdentificador do chamado (ticket_id).

No output schema declared.

No examples provided.

tomticket_finish_ticket ~169

ATENCAO: altera producao. Finaliza o chamado. time_work lanca minutos trabalhados. Nao dispara email automaticamente.

NameTypeReqDescription
attachmentsstring–Caminhos locais de anexos, separados por virgula. Maximo 25 arquivos / 25 MB.
custom_fieldsstring–Campos personalizados em JSON objeto. Ex.: {"ID_DO_CAMPO":"valor"}.
deadline_justificationstring–Justificativa de SLA de deadline (Enterprise).
messagestringyesMensagem de finalizacao.
startup_justificationstring–Justificativa de SLA de inicializacao (Enterprise).
ticket_idstringyesIdentificador do chamado (ticket_id).
time_workinteger–Tempo trabalhado em minutos.

No output schema declared.

No examples provided.

tomticket_get_chat ~29

Consulta um chat individualmente. Nao altera dados.

NameTypeReqDescription
chat_idstringyes–

No output schema declared.

No examples provided.

tomticket_get_customer ~57

Consulta os detalhes de um cliente. Nao altera dados.

NameTypeReqDescription
customer_idstringyesId interno ou email do cliente.
customer_type_idstring–I = id interno, E = email. Padrao I.

No output schema declared.

No examples provided.

tomticket_get_customer_hour_contract ~62

Consulta horas contratadas vs usadas no mes corrente. Nao altera dados.

NameTypeReqDescription
customer_idstringyesId interno ou email do cliente.
customer_type_idstring–I = id interno, E = email. Padrao I.

No output schema declared.

No examples provided.

tomticket_get_customer_permissions ~60

Consulta permissoes basicas do cliente. Nao altera dados.

NameTypeReqDescription
customer_idstringyesId interno ou email do cliente.
customer_type_idstring–I = id interno, E = email. Padrao I.

No output schema declared.

No examples provided.

tomticket_get_ticket ~80

Consulta o detalhe completo de um chamado, incluindo respostas e horarios. Nao altera dados.

NameTypeReqDescription
show_staggered_ticketsinteger––
show_stopwatchinteger–Padrao 1.
show_tagsinteger–Padrao 1.
ticket_idstringyesIdentificador do chamado (ticket_id).

No output schema declared.

No examples provided.

tomticket_link_customer_department ~79

ATENCAO: altera producao. Vincula um departamento ao cliente.

NameTypeReqDescription
customer_idstringyesId interno ou email do cliente.
customer_type_idstring–I = id interno, E = email. Padrao I.
department_idstringyesIdentificador do departamento (enviado como configuration).

No output schema declared.

No examples provided.

tomticket_list_article_categories ~21

Lista categorias de artigos. Nao altera dados.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tomticket_list_articles ~37

Lista artigos da base de conhecimento. Nao altera dados.

NameTypeReqDescription
category_idstring––
pageinteger––

No output schema declared.

No examples provided.

tomticket_list_chats ~100

Lista atendimentos de chat (50 por pagina). Nao altera dados.

NameTypeReqDescription
creation_date_gestring––
creation_date_lestring––
customer_idstring––
customer_type_idstring––
department_idstring––
max_protocolinteger––
min_protocolinteger––
organization_idstring––
pageinteger––

No output schema declared.

No examples provided.

tomticket_list_custom_fields ~24

Lista todos os campos personalizados da conta. Nao altera dados.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tomticket_list_customer_custom_fields ~25

Lista campos personalizados de cadastro de cliente. Nao altera dados.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tomticket_list_customer_portfolios ~25

Lista carteiras de clientes (Enterprise). Nao altera dados.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tomticket_list_customers ~75

Lista clientes da conta (50 por pagina). Nao altera dados.

NameTypeReqDescription
columnstring––
orderstring––
organization_idstring––
pageinteger––
search_by_organization_motherinteger––
show_custom_fieldsinteger––

No output schema declared.

No examples provided.

tomticket_list_department_categories ~34

Lista categorias de um departamento. Nao altera dados.

NameTypeReqDescription
department_idstringyesIdentificador do departamento.

No output schema declared.

No examples provided.

tomticket_list_department_custom_fields ~44

Lista campos personalizados de chamados externos por departamento e categoria. Nao altera dados.

NameTypeReqDescription
category_idstring––
department_idstring––

No output schema declared.

No examples provided.

tomticket_list_department_operators ~36

Lista atendentes de um departamento. Nao altera dados.

NameTypeReqDescription
department_idstringyesIdentificador do departamento.

No output schema declared.

No examples provided.

tomticket_list_department_statuses ~43

Lista status de um departamento (necessario para iniciar cronometro). Nao altera dados.

NameTypeReqDescription
department_idstringyesIdentificador do departamento.

No output schema declared.

No examples provided.

tomticket_list_departments ~59

Lista departamentos da conta, com categorias, status e atendentes. Nao altera dados.

NameTypeReqDescription
show_nested_itemsinteger–0 so id/nome; 1 inclui categorias, status e atendentes. Padrao 1.

No output schema declared.

No examples provided.

tomticket_list_open_tickets ~152

Lista chamados ABERTOS da conta TomTicket (exclui cancelados e finalizados). Nao altera dados.

NameTypeReqDescription
department_idstring–Filtrar por departamento.
operator_idstring–Filtrar por atendente. Vazio localiza sem atendente.
pageinteger–Pagina. Ate 50 itens por pagina. Padrao: 1.
prioritystring–Prioridades separadas por virgula: 1 baixa, 2 normal, 3 alta, 4 urgente.
show_stopwatchinteger–1 para incluir horarios cronometrados.
show_tagsinteger–1 para incluir tags.

No output schema declared.

No examples provided.

tomticket_list_organization_custom_fields ~27

Lista campos personalizados de cadastro de organizacao. Nao altera dados.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tomticket_list_organizations ~66

Lista organizacoes da conta (50 por pagina). Nao altera dados.

NameTypeReqDescription
columnstring––
orderstring––
organization_mother_idstring––
pageinteger––
show_custom_fieldsinteger––

No output schema declared.

No examples provided.

tomticket_list_ticket_custom_fields ~24

Lista campos personalizados usados em chamados. Nao altera dados.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tomticket_list_tickets ~342

Lista chamados da conta com filtros da API (paginado, 50 por pagina). Nao altera dados.

NameTypeReqDescription
category_idstring––
columnstring–Campo de ordenacao. Padrao: protocol.
creation_date_gestring–Criacao >= YYYY-MM-DD HH:II:SS-TZ ou data dinamica.
creation_date_lestring––
customer_idstring––
customer_type_idstring–I = id interno, E = email. Padrao I.
department_idstring––
last_situation_gestring––
last_situation_lestring––
last_update_gestring–Ultima modificacao >=. Periodo maximo 90 dias.
max_protocolinteger––
min_protocolinteger––
operator_idstring––
orderstring––
organization_idstring––
pageinteger–Pagina. Ate 50 itens por pagina. Padrao: 1.
prioritystring––
show_stopwatchinteger––
show_tagsinteger––
situationstring–Situacoes separadas por virgula. 0 aguardando atendente; 1 nao iniciada; 2 aguardando cliente; 3 respondido pelo cliente; 4 cancelada; 5 finalizada; 6 atendente modificado; 7 apoio; 8-11 aprovacoes.
status_idstring––
truncate_bodyinteger––

No output schema declared.

No examples provided.

tomticket_read_article ~35

Le o conteudo de um artigo da base de conhecimento. Nao altera dados.

NameTypeReqDescription
article_idstringyes–

No output schema declared.

No examples provided.

tomticket_remove_custom_field_option ~52

ATENCAO: altera producao. Remove opcao de campo personalizado.

NameTypeReqDescription
custom_field_idstringyes–
option_idstring––
valuestring––

No output schema declared.

No examples provided.

tomticket_reply_ticket ~167

ATENCAO: altera producao. Responde o chamado como atendente. Exige atendente vinculado. Use start_date e end_date juntos para lancar horario de trabalho.

NameTypeReqDescription
attachmentsstring–Caminhos locais de anexos, separados por virgula. Maximo 25 arquivos / 25 MB.
end_datestring–Fim do trabalho no mesmo formato. Obrigatorio se start_date for enviado.
messagestringyesTexto da resposta (text/plain).
start_datestring–Inicio do trabalho: YYYY-MM-DD HH:II:SSZ. Ex.: 2026-08-21 14:00:00-0300.
ticket_idstringyesIdentificador do chamado (ticket_id).

No output schema declared.

No examples provided.

tomticket_reply_ticket_as_customer ~84

ATENCAO: altera producao. Responde o chamado como cliente. Nao dispara email automaticamente.

NameTypeReqDescription
attachmentsstring–Caminhos locais de anexos, separados por virgula. Maximo 25 arquivos / 25 MB.
messagestringyes–
ticket_idstringyesIdentificador do chamado (ticket_id).

No output schema declared.

No examples provided.

tomticket_search_articles ~47

Pesquisa artigos da base de conhecimento. Nao altera dados.

NameTypeReqDescription
category_idstring––
pageinteger––
querystringyesTexto da pesquisa.

No output schema declared.

No examples provided.

tomticket_set_customer_access ~86

ATENCAO: altera producao. Ativa ou desativa o acesso do cliente ao painel e chamados por email.

NameTypeReqDescription
activeintegeryes1 ativo, 0 inativo.
customer_idstringyesId interno ou email do cliente.
customer_type_idstring–I = id interno, E = email. Padrao I.

No output schema declared.

No examples provided.

tomticket_set_customer_create_tickets ~74

ATENCAO: altera producao. Define se o cliente pode criar chamados.

NameTypeReqDescription
create_ticketsintegeryes–
customer_idstringyesId interno ou email do cliente.
customer_type_idstring–I = id interno, E = email. Padrao I.

No output schema declared.

No examples provided.

tomticket_start_status ~69

ATENCAO: altera producao. Abre um status no chamado (inicia cronometro/status). Consulte status do departamento antes.

NameTypeReqDescription
commentstring––
status_idstringyes–
ticket_idstringyesIdentificador do chamado (ticket_id).

No output schema declared.

No examples provided.

tomticket_transfer_ticket ~62

ATENCAO: altera producao. Transfere o chamado entre departamentos e/ou atendentes.

NameTypeReqDescription
department_idstring––
operator_idstring––
ticket_idstringyesIdentificador do chamado (ticket_id).

No output schema declared.

No examples provided.

tomticket_unlink_customer_department ~82

ATENCAO: altera producao. Desvincula um departamento do cliente.

NameTypeReqDescription
customer_idstringyesId interno ou email do cliente.
customer_type_idstring–I = id interno, E = email. Padrao I.
department_idstringyesIdentificador do departamento (enviado como configuration).

No output schema declared.

No examples provided.

tomticket_update_article ~73

ATENCAO: altera producao. Atualiza um artigo da base de conhecimento.

NameTypeReqDescription
article_idstringyes–
category_idstring––
contentstring––
display_orderinteger––
titlestring––
visibilitystring––

No output schema declared.

No examples provided.

tomticket_update_customer ~163

ATENCAO: altera producao. Atualiza dados do cliente. Propriedade vazia e ignorada.

NameTypeReqDescription
create_ticketsinteger––
custom_fieldsstring–Campos personalizados JSON. Ex.: {"ID":"valor"}.
customer_idstringyesId interno ou email do cliente.
customer_type_idstring–I = id interno, E = email. Padrao I.
emailstring––
internal_idstring–So quando customer_type_id=E.
languagestring––
namestring––
organization_idstring––
passwordstring––
phonestring––
portfolio_idstring––

No output schema declared.

No examples provided.

tomticket_update_organization ~152

ATENCAO: altera producao. Atualiza uma organizacao. Propriedade vazia e ignorada.

NameTypeReqDescription
create_ticketsinteger––
custom_fieldsstring–Campos personalizados JSON. Ex.: {"ID":"valor"}.
emailstring––
manager_see_all_ticketsinteger––
monthly_tickets_quotainteger––
mother_organization_idstring––
namestring––
organization_idstringyes–
phonestring––
portfolio_idstring––
sitestring––
team_see_all_ticketsinteger––

No output schema declared.

No examples provided.

Common questions

What is the io.github.glira/mcp-tomticket server?

io.github.glira/mcp-tomticket is listed in the public MCP registry as io.github.glira/mcp-tomticket. TomTicket helpdesk MCP: tickets, replies, time, customers, chats, and KB. This page covers its npm package (mcp-tomticket).

Is the io.github.glira/mcp-tomticket server safe to use?

io.github.glira/mcp-tomticket scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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.github.glira/mcp-tomticket server expose?

io.github.glira/mcp-tomticket exposes 49 tools: tomticket_list_open_tickets, tomticket_list_tickets, tomticket_get_ticket, tomticket_create_ticket, tomticket_reply_ticket, and 44 more. Their descriptions and schemas cost roughly 3,853 tokens of context every time the server is loaded.

Is the io.github.glira/mcp-tomticket server still maintained?

io.github.glira/mcp-tomticket is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.glira/mcp-tomticket server under?

io.github.glira/mcp-tomticket declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.