# io.github.glira/mcp-tomticket (npm · mcp-tomticket)

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

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- npm · `mcp-tomticket`: 79/100 (this document), [markdown](https://verifymcp.io/servers/glira-mcp-tomticket/mcp-tomticket.md), [page](https://verifymcp.io/servers/glira-mcp-tomticket/mcp-tomticket)

## Channel facts

- Registry: `npm`
- Package: `mcp-tomticket`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 33 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 3853 tokens (~78/item across 49 items; 49 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 42% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 49 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add glira-mcp-tomticket -- npx -y mcp-tomticket
```

### Cursor

```json
{
  "mcpServers": {
    "glira-mcp-tomticket": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-tomticket"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "glira-mcp-tomticket": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-tomticket"
      ]
    }
  }
}
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add glira-mcp-tomticket --command npx --arg -y --arg mcp-tomticket
```

### Hermes

```yaml
mcp_servers:
  glira-mcp-tomticket:
    command: "npx"
    args: ["-y", "mcp-tomticket"]
```

### Netclaw

```json
{
  "McpServers": {
    "glira-mcp-tomticket": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-tomticket"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add glira-mcp-tomticket -t stdio -c npx -a -y mcp-tomticket
```

### Other

```json
{
  "mcpServers": {
    "glira-mcp-tomticket": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-tomticket"
      ]
    }
  }
}
```

## 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-09-23 (score 79, +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.

### 2026-09-21 (score 78, −3)

- [functional] Stability: pass → 0.80

### 2026-09-20 (score 81, +1)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 80, +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.

### 2026-09-16 (score 79, +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.

### 2026-09-14 (score 78, +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.

### 2026-09-12 (score 77, +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.

### 2026-09-10 (score 76, +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.

## MCP tools (49)

### `tomticket_list_open_tickets` (~152 tokens)

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

Input parameters:

- `department_id` (string): Filtrar por departamento.
- `operator_id` (string): Filtrar por atendente. Vazio localiza sem atendente.
- `page` (integer): Pagina. Ate 50 itens por pagina. Padrao: 1.
- `priority` (string): Prioridades separadas por virgula: 1 baixa, 2 normal, 3 alta, 4 urgente.
- `show_stopwatch` (integer): 1 para incluir horarios cronometrados.
- `show_tags` (integer): 1 para incluir tags.

### `tomticket_list_tickets` (~342 tokens)

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

Input parameters:

- `category_id` (string)
- `column` (string): Campo de ordenacao. Padrao: protocol.
- `creation_date_ge` (string): Criacao >= YYYY-MM-DD HH:II:SS-TZ ou data dinamica.
- `creation_date_le` (string)
- `customer_id` (string)
- `customer_type_id` (string): I = id interno, E = email. Padrao I.
- `department_id` (string)
- `last_situation_ge` (string)
- `last_situation_le` (string)
- `last_update_ge` (string): Ultima modificacao >=. Periodo maximo 90 dias.
- `max_protocol` (integer)
- `min_protocol` (integer)
- `operator_id` (string)
- `order` (string)
- `organization_id` (string)
- `page` (integer): Pagina. Ate 50 itens por pagina. Padrao: 1.
- `priority` (string)
- `show_stopwatch` (integer)
- `show_tags` (integer)
- `situation` (string): 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_id` (string)
- `truncate_body` (integer)

### `tomticket_get_ticket` (~80 tokens)

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

Input parameters:

- `show_staggered_tickets` (integer)
- `show_stopwatch` (integer): Padrao 1.
- `show_tags` (integer): Padrao 1.
- `ticket_id` (string, required): Identificador do chamado (ticket_id).

### `tomticket_create_ticket` (~161 tokens)

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

Input parameters:

- `attachments` (string): Caminhos locais de anexos, separados por virgula. Maximo 25 arquivos / 25 MB.
- `category_id` (string)
- `custom_fields` (string): Campos personalizados em JSON objeto. Ex.: {"ID_DO_CAMPO":"valor"}.
- `customer_id` (string, required): Id interno ou email do cliente.
- `customer_id_type` (string): I id interno, E email.
- `department_id` (string, required)
- `message` (string, required)
- `priority` (integer): 1 baixa, 2 normal, 3 alta, 4 urgente.
- `subject` (string, required)

### `tomticket_reply_ticket` (~167 tokens)

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

Input parameters:

- `attachments` (string): Caminhos locais de anexos, separados por virgula. Maximo 25 arquivos / 25 MB.
- `end_date` (string): Fim do trabalho no mesmo formato. Obrigatorio se start_date for enviado.
- `message` (string, required): Texto da resposta (text/plain).
- `start_date` (string): Inicio do trabalho: YYYY-MM-DD HH:II:SSZ. Ex.: 2026-08-21 14:00:00-0300.
- `ticket_id` (string, required): Identificador do chamado (ticket_id).

### `tomticket_reply_ticket_as_customer` (~84 tokens)

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

Input parameters:

- `attachments` (string): Caminhos locais de anexos, separados por virgula. Maximo 25 arquivos / 25 MB.
- `message` (string, required)
- `ticket_id` (string, required): Identificador do chamado (ticket_id).

### `tomticket_comment_ticket` (~77 tokens)

ATENCAO: altera producao. Adiciona comentario interno no chamado.

Input parameters:

- `attachments` (string): Caminhos locais de anexos, separados por virgula. Maximo 25 arquivos / 25 MB.
- `comment` (string, required)
- `ticket_id` (string, required): Identificador do chamado (ticket_id).

### `tomticket_finish_ticket` (~169 tokens)

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

Input parameters:

- `attachments` (string): Caminhos locais de anexos, separados por virgula. Maximo 25 arquivos / 25 MB.
- `custom_fields` (string): Campos personalizados em JSON objeto. Ex.: {"ID_DO_CAMPO":"valor"}.
- `deadline_justification` (string): Justificativa de SLA de deadline (Enterprise).
- `message` (string, required): Mensagem de finalizacao.
- `startup_justification` (string): Justificativa de SLA de inicializacao (Enterprise).
- `ticket_id` (string, required): Identificador do chamado (ticket_id).
- `time_work` (integer): Tempo trabalhado em minutos.

### `tomticket_evaluate_ticket` (~119 tokens)

ATENCAO: altera producao. Avalia um chamado ja finalizado.

Input parameters:

- `comment` (string)
- `custom_fields` (string): Campos personalizados em JSON objeto. Ex.: {"ID_DO_CAMPO":"valor"}.
- `grade` (integer, required): 5 otimo, 4 bom, 3 regular, 2 ruim, 1 pessimo.
- `problem_solved` (integer): 1 se o problema foi resolvido.
- `ticket_id` (string, required): Identificador do chamado (ticket_id).

### `tomticket_transfer_ticket` (~62 tokens)

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

Input parameters:

- `department_id` (string)
- `operator_id` (string)
- `ticket_id` (string, required): Identificador do chamado (ticket_id).

### `tomticket_assign_operator` (~50 tokens)

ATENCAO: altera producao. Vincula um atendente ao chamado.

Input parameters:

- `operator_id` (string, required)
- `ticket_id` (string, required): Identificador do chamado (ticket_id).

### `tomticket_start_status` (~69 tokens)

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

Input parameters:

- `comment` (string)
- `status_id` (string, required)
- `ticket_id` (string, required): Identificador do chamado (ticket_id).

### `tomticket_close_status` (~49 tokens)

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

Input parameters:

- `ticket_id` (string, required): Identificador do chamado (ticket_id).

### `tomticket_list_customers` (~75 tokens)

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

Input parameters:

- `column` (string)
- `order` (string)
- `organization_id` (string)
- `page` (integer)
- `search_by_organization_mother` (integer)
- `show_custom_fields` (integer)

### `tomticket_get_customer` (~57 tokens)

Consulta os detalhes de um cliente. Nao altera dados.

Input parameters:

- `customer_id` (string, required): Id interno ou email do cliente.
- `customer_type_id` (string): I = id interno, E = email. Padrao I.

### `tomticket_customer_exists` (~62 tokens)

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

Input parameters:

- `customer_id` (string, required): Id interno ou email do cliente.
- `customer_type_id` (string): I = id interno, E = email. Padrao I.

### `tomticket_create_customer` (~134 tokens)

ATENCAO: altera producao. Cria um novo cliente.

Input parameters:

- `create_tickets` (integer)
- `custom_fields` (string): Campos personalizados JSON. Ex.: {"ID":"valor"}.
- `customer_id` (string, required): Identificador interno (CPF, CNPJ ou chave do seu sistema).
- `email` (string)
- `language` (string): pt-BR, es_ES ou en-US.
- `name` (string, required)
- `organization_id` (string)
- `password` (string)
- `phone` (string)
- `portfolio_id` (string)

### `tomticket_update_customer` (~163 tokens)

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

Input parameters:

- `create_tickets` (integer)
- `custom_fields` (string): Campos personalizados JSON. Ex.: {"ID":"valor"}.
- `customer_id` (string, required): Id interno ou email do cliente.
- `customer_type_id` (string): I = id interno, E = email. Padrao I.
- `email` (string)
- `internal_id` (string): So quando customer_type_id=E.
- `language` (string)
- `name` (string)
- `organization_id` (string)
- `password` (string)
- `phone` (string)
- `portfolio_id` (string)

### `tomticket_get_customer_permissions` (~60 tokens)

Consulta permissoes basicas do cliente. Nao altera dados.

Input parameters:

- `customer_id` (string, required): Id interno ou email do cliente.
- `customer_type_id` (string): I = id interno, E = email. Padrao I.

### `tomticket_set_customer_access` (~86 tokens)

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

Input parameters:

- `active` (integer, required): 1 ativo, 0 inativo.
- `customer_id` (string, required): Id interno ou email do cliente.
- `customer_type_id` (string): I = id interno, E = email. Padrao I.

### `tomticket_set_customer_create_tickets` (~74 tokens)

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

Input parameters:

- `create_tickets` (integer, required)
- `customer_id` (string, required): Id interno ou email do cliente.
- `customer_type_id` (string): I = id interno, E = email. Padrao I.

### `tomticket_list_customer_portfolios` (~25 tokens)

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

### `tomticket_get_customer_hour_contract` (~62 tokens)

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

Input parameters:

- `customer_id` (string, required): Id interno ou email do cliente.
- `customer_type_id` (string): I = id interno, E = email. Padrao I.

### `tomticket_link_customer_department` (~79 tokens)

ATENCAO: altera producao. Vincula um departamento ao cliente.

Input parameters:

- `customer_id` (string, required): Id interno ou email do cliente.
- `customer_type_id` (string): I = id interno, E = email. Padrao I.
- `department_id` (string, required): Identificador do departamento (enviado como configuration).

### `tomticket_unlink_customer_department` (~82 tokens)

ATENCAO: altera producao. Desvincula um departamento do cliente.

Input parameters:

- `customer_id` (string, required): Id interno ou email do cliente.
- `customer_type_id` (string): I = id interno, E = email. Padrao I.
- `department_id` (string, required): Identificador do departamento (enviado como configuration).

### `tomticket_customer_quick_access` (~66 tokens)

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

Input parameters:

- `customer_id` (string, required): Id interno ou email do cliente.
- `customer_type_id` (string): I = id interno, E = email. Padrao I.

### `tomticket_check_email_blacklist` (~38 tokens)

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

Input parameters:

- `email` (string, required)

### `tomticket_list_organizations` (~66 tokens)

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

Input parameters:

- `column` (string)
- `order` (string)
- `organization_mother_id` (string)
- `page` (integer)
- `show_custom_fields` (integer)

### `tomticket_create_organization` (~161 tokens)

ATENCAO: altera producao. Cria uma organizacao.

Input parameters:

- `create_tickets` (integer)
- `custom_fields` (string): Campos personalizados JSON. Ex.: {"ID":"valor"}.
- `email` (string)
- `manager_see_all_tickets` (integer)
- `monthly_tickets_quota` (integer)
- `mother_organization_id` (string)
- `name` (string, required)
- `phone` (string)
- `portfolio_id` (string)
- `return_id_if_exists` (string)
- `site` (string)
- `strict_mail` (string)
- `strict_name` (string)
- `team_see_all_tickets` (integer)

### `tomticket_update_organization` (~152 tokens)

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

Input parameters:

- `create_tickets` (integer)
- `custom_fields` (string): Campos personalizados JSON. Ex.: {"ID":"valor"}.
- `email` (string)
- `manager_see_all_tickets` (integer)
- `monthly_tickets_quota` (integer)
- `mother_organization_id` (string)
- `name` (string)
- `organization_id` (string, required)
- `phone` (string)
- `portfolio_id` (string)
- `site` (string)
- `team_see_all_tickets` (integer)

### `tomticket_list_chats` (~100 tokens)

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

Input parameters:

- `creation_date_ge` (string)
- `creation_date_le` (string)
- `customer_id` (string)
- `customer_type_id` (string)
- `department_id` (string)
- `max_protocol` (integer)
- `min_protocol` (integer)
- `organization_id` (string)
- `page` (integer)

### `tomticket_get_chat` (~29 tokens)

Consulta um chat individualmente. Nao altera dados.

Input parameters:

- `chat_id` (string, required)

### `tomticket_list_departments` (~59 tokens)

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

Input parameters:

- `show_nested_items` (integer): 0 so id/nome; 1 inclui categorias, status e atendentes. Padrao 1.

### `tomticket_list_department_categories` (~34 tokens)

Lista categorias de um departamento. Nao altera dados.

Input parameters:

- `department_id` (string, required): Identificador do departamento.

### `tomticket_list_department_operators` (~36 tokens)

Lista atendentes de um departamento. Nao altera dados.

Input parameters:

- `department_id` (string, required): Identificador do departamento.

### `tomticket_list_department_statuses` (~43 tokens)

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

Input parameters:

- `department_id` (string, required): Identificador do departamento.

### `tomticket_list_articles` (~37 tokens)

Lista artigos da base de conhecimento. Nao altera dados.

Input parameters:

- `category_id` (string)
- `page` (integer)

### `tomticket_read_article` (~35 tokens)

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

Input parameters:

- `article_id` (string, required)

### `tomticket_search_articles` (~47 tokens)

Pesquisa artigos da base de conhecimento. Nao altera dados.

Input parameters:

- `category_id` (string)
- `page` (integer)
- `query` (string, required): Texto da pesquisa.

### `tomticket_list_article_categories` (~21 tokens)

Lista categorias de artigos. Nao altera dados.

### `tomticket_create_article` (~74 tokens)

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

Input parameters:

- `category_id` (string, required)
- `content` (string, required): Conteudo HTML do artigo.
- `display_order` (integer)
- `title` (string, required)
- `visibility` (string, required): Quem pode ver o artigo.

### `tomticket_update_article` (~73 tokens)

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

Input parameters:

- `article_id` (string, required)
- `category_id` (string)
- `content` (string)
- `display_order` (integer)
- `title` (string)
- `visibility` (string)

### `tomticket_list_custom_fields` (~24 tokens)

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

### `tomticket_list_ticket_custom_fields` (~24 tokens)

Lista campos personalizados usados em chamados. Nao altera dados.

### `tomticket_list_customer_custom_fields` (~25 tokens)

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

### `tomticket_list_organization_custom_fields` (~27 tokens)

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

### `tomticket_list_department_custom_fields` (~44 tokens)

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

Input parameters:

- `category_id` (string)
- `department_id` (string)

### `tomticket_add_custom_field_option` (~46 tokens)

ATENCAO: altera producao. Adiciona opcao em campo personalizado.

Input parameters:

- `custom_field_id` (string, required)
- `value` (string, required)

### `tomticket_remove_custom_field_option` (~52 tokens)

ATENCAO: altera producao. Remove opcao de campo personalizado.

Input parameters:

- `custom_field_id` (string, required)
- `option_id` (string)
- `value` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/glira-mcp-tomticket/mcp-tomticket#diagnostics

## Score history

- 2026-09-24: 79
- 2026-09-23: 79
- 2026-09-22: 78
- 2026-09-21: 78
- 2026-09-20: 81
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 78
- 2026-09-14: 78
- 2026-09-13: 77
- 2026-09-12: 77
- 2026-09-11: 76
- 2026-09-10: 76
- 2026-09-09: 75
- 2026-09-08: 75
- 2026-09-07: 75
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 73
- 2026-09-03: 73
- 2026-09-02: 72
- 2026-09-01: 72
- 2026-08-31: 71
- 2026-08-30: 71
- 2026-08-29: 70
- 2026-08-28: 67
- 2026-08-27: 67
- 2026-08-26: 67

## 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.

## Links

- npm package: https://www.npmjs.com/package/mcp-tomticket
- Socket report: https://socket.dev/npm/package/mcp-tomticket
- Repository: https://github.com/glira/mcp-tomticket
- Changelog RSS feed: https://verifymcp.io/servers/glira-mcp-tomticket/mcp-tomticket.xml
- Changelog JSON feed: https://verifymcp.io/servers/glira-mcp-tomticket/mcp-tomticket.json
- HTML version of this page: https://verifymcp.io/servers/glira-mcp-tomticket/mcp-tomticket