Tiflux
REMOTE · API.MCP.AI · SCANNED OCT 7
Wrapper for the official Tiflux API v2 (help desk and service desk): tickets with replies to the req
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3495 tokens (~97/item across 36 items; 36 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 36 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 37 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
How do I install the Tiflux MCP server?
Tiflux is a hosted endpoint at https://api.mcp.ai/p_tiflux, 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 · api.mcp.ai
claude mcp add --transport http mcp-dir-tiflux-mcp 'https://api.mcp.ai/p_tiflux'
{
"mcpServers": {
"mcp-dir-tiflux-mcp": {
"url": "https://api.mcp.ai/p_tiflux"
}
}
} {
"servers": {
"mcp-dir-tiflux-mcp": {
"type": "http",
"url": "https://api.mcp.ai/p_tiflux"
}
}
} [mcp_servers.mcp-dir-tiflux-mcp] url = "https://api.mcp.ai/p_tiflux"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mcp-dir-tiflux-mcp": {
"type": "remote",
"url": "https://api.mcp.ai/p_tiflux",
"enabled": true
}
}
} openclaw mcp add mcp-dir-tiflux-mcp --url 'https://api.mcp.ai/p_tiflux' --transport streamable-http
mcp_servers:
mcp-dir-tiflux-mcp:
url: "https://api.mcp.ai/p_tiflux" {
"McpServers": {
"mcp-dir-tiflux-mcp": {
"Transport": "http",
"Url": "https://api.mcp.ai/p_tiflux"
}
}
} assistant mcp add mcp-dir-tiflux-mcp -t streamable-http -u 'https://api.mcp.ai/p_tiflux'
{
"mcpServers": {
"mcp-dir-tiflux-mcp": {
"type": "http",
"url": "https://api.mcp.ai/p_tiflux"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 7 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.365 → 0.9.368 functional
- 4 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.356 → 0.9.358 functional
- 3 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.353 → 0.9.356 functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 1 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.351 → 0.9.353 functional
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 7 Oct 2026 · Probed https://api.mcp.ai/p_tiflux
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.ai | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1bf4d405299e078a0e62ff16cded599b |
| SANs: mcp.ai, *.mcp.ai | ||||||
| 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 api.mcp.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| mcp.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mcp.ai/p_tiflux | Verified | 200 | |
| http (plaintext) | http://api.mcp.ai/p_tiflux | Inconclusive | 406 |
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 →
authenticate ~99
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | – |
No output schema declared.
No examples provided.
connect ~42
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
marketplace ~532
The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| arguments | string | – | – |
| cancel_comment | string | – | – |
| cancel_reason | string | – | – |
| conversation | string | – | – |
| immediate | boolean | – | – |
| limit | number | – | – |
| mcp_id | string | – | – |
| message | string | – | – |
| prompt_body | string | – | – |
| prompt_category | string | – | – |
| prompt_description | string | – | – |
| prompt_slug | string | – | – |
| prompt_targets | array | – | – |
| prompt_title | string | – | – |
| prompt_tool | string | – | – |
| prompt_vars | string | – | – |
| query | string | – | – |
| report_context | string | – | – |
| request_details | string | – | – |
| request_name | string | – | – |
| tier_slug | string | – | – |
| tool_id | string | – | – |
No output schema declared.
No examples provided.
report_bug ~50
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| conversation | string | – | – |
| message | string | yes | – |
No output schema declared.
No examples provided.
show_version ~17
Show the current MCP platform and adapter versions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tiflux_billings_history ~140
Histórico de faturamentos. Os pares de data são obrigatórios em conjunto: billing_start_date com billing_end_date, e due_start_date com due_end_date. Bulk support: accepts client_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_end_date | string | – | – |
| billing_start_date | string | – | – |
| client_id | – | – | – |
| client_ids | array | – | – |
| due_end_date | string | – | – |
| due_start_date | string | – | – |
| limit | number | – | – |
| nfe_number | string | – | – |
| offset | number | – | – |
| ticket_number | – | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
tiflux_cancel_ticket ~70
Cancela um chamado, encerrando-o SEM tratá-lo como atendido (duplicado, aberto por engano, fora de escopo). Cancelados não contam como resolvidos nos relatórios. Para um chamado efetivamente resolvido, use tiflux_close_ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_number | – | yes | – |
No output schema declared.
No examples provided.
tiflux_close_ticket ~63
Encerra um chamado, marcando-o como resolvido. Encerrar para o SLA e costuma disparar a pesquisa de satisfação para o solicitante. Para um chamado que não deveria ter sido aberto, use tiflux_cancel_ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_number | – | yes | – |
No output schema declared.
No examples provided.
tiflux_create_appointment ~65
Lança um apontamento de horas num chamado, em nome do usuário dono do token.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| description | string | yes | – |
| end_time | string | yes | – |
| init_time | string | yes | – |
| ticket_number | – | yes | – |
No output schema declared.
No examples provided.
tiflux_create_internal_communication ~74
Cria uma comunicação interna num chamado. É uma nota visível SÓ PARA A EQUIPE, o solicitante não recebe nem vê. Para falar com o solicitante use tiflux_create_ticket_answer.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | – |
| text | string | yes | – |
| ticket_number | – | yes | – |
No output schema declared.
No examples provided.
tiflux_create_ticket ~264
Abre um novo chamado. Resolva desk_id e client_id antes com tiflux_list_desks e tiflux_list_clients. Identifique o solicitante por requestor_id, ou pelos campos requestor_name e requestor_email quando ele ainda não existir. Bulk support: accepts desk_ids, client_ids, priority_ids, status_ids, services_catalogs_item_ids, requestor_ids, responsible_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | – | – | – |
| client_ids | array | – | – |
| description | string | yes | – |
| desk_id | – | – | – |
| desk_ids | array | – | – |
| files | array | – | – |
| followers | string | – | – |
| parent_ticket_number | – | – | – |
| priority_id | – | – | – |
| priority_ids | array | – | – |
| requestor_email | string | – | – |
| requestor_id | – | – | – |
| requestor_ids | array | – | – |
| requestor_name | string | – | – |
| requestor_telephone | string | – | – |
| responsible_id | – | – | – |
| responsible_ids | array | – | – |
| services_catalogs_item_id | – | – | – |
| services_catalogs_item_ids | array | – | – |
| status_id | – | – | – |
| status_ids | array | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
tiflux_create_ticket_answer ~78
Responde um chamado. Esta resposta É VISÍVEL PARA O SOLICITANTE e dispara notificação. Para uma nota que só a equipe vê, use tiflux_create_internal_communication.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | – |
| text | string | yes | – |
| ticket_number | – | yes | – |
| with_signature | boolean | – | – |
No output schema declared.
No examples provided.
tiflux_get_clients ~43
Detalha um ou vários clientes pelos ids, numa única chamada. Um id que falhar não derruba os demais.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ids | array | yes | – |
No output schema declared.
No examples provided.
tiflux_get_ticket_stages_slas ~64
Histórico de estágios e SLAs de um chamado (quando entrou em cada estágio e como ficou o SLA). Use para auditar cumprimento de prazo.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| offset | number | – | – |
| ticket_number | – | yes | – |
No output schema declared.
No examples provided.
tiflux_get_tickets ~72
Detalha um ou vários chamados pelos números, numa única chamada. Um chamado que falhar não derruba os demais: os erros vêm separados por número em errors[].
| Name | Type | Req | Description |
|---|---|---|---|
| include_filled_entity | boolean | – | – |
| show_entities | boolean | – | – |
| ticket_numbers | array | yes | – |
No output schema declared.
No examples provided.
tiflux_list_appointments ~97
Lista apontamentos de horas de toda a organização por período, atendente e mesa. É a base para relatório de horas trabalhadas e faturáveis.
| Name | Type | Req | Description |
|---|---|---|---|
| desk_ids | array | – | – |
| end_date | string | – | – |
| include_valorization | boolean | – | – |
| limit | number | – | – |
| offset | number | – | – |
| start_date | string | – | – |
| user_ids | array | – | – |
No output schema declared.
No examples provided.
tiflux_list_clients ~71
Lista clientes da organização, com busca parcial por nome. Use para resolver o client_id exigido na abertura de chamado.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | – |
| limit | number | – | – |
| name | string | – | – |
| offset | number | – | – |
| social_revenue | string | – | – |
No output schema declared.
No examples provided.
tiflux_list_contracts ~64
Lista os contratos de atendimento, com filtro por cliente, tipo e situação.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ids | array | – | – |
| contract_type_ids | array | – | – |
| limit | number | – | – |
| offset | number | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
tiflux_list_departments ~50
Lista os departamentos da organização. Um atendente não administrador vê só os do próprio grupo.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| name | string | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
tiflux_list_desk_priorities ~66
Lista as prioridades configuradas numa mesa, com os respectivos SLAs. Bulk support: accepts desk_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| desk_id | – | yes | – |
| desk_ids | array | – | – |
| limit | number | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
tiflux_list_desk_services_catalogs ~69
Lista os catálogos de serviços de uma mesa (a classificação do chamado). Bulk support: accepts desk_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| desk_id | – | yes | – |
| desk_ids | array | – | – |
| limit | number | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
tiflux_list_desk_stages ~82
Lista os estágios (etapas do fluxo) de uma mesa. Use para descobrir o stage_id ao mover um chamado com tiflux_update_ticket. Bulk support: accepts desk_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| desk_id | – | yes | – |
| desk_ids | array | – | – |
| limit | number | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
tiflux_list_desks ~67
Lista as mesas de atendimento, com busca parcial por nome. A mesa define os estágios, prioridades e catálogo de serviços disponíveis num chamado.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | – |
| limit | number | – | – |
| name | string | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
tiflux_list_internal_communications ~56
Lista as comunicações internas de um chamado (notas visíveis só para a equipe, nunca para o solicitante).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| offset | number | – | – |
| ticket_number | – | yes | – |
No output schema declared.
No examples provided.
tiflux_list_knowledges ~66
Busca artigos da base de conhecimento por texto e por pasta. Use para achar o procedimento antes de responder um chamado.
| Name | Type | Req | Description |
|---|---|---|---|
| knowledge_folder_ids | array | – | – |
| limit | number | – | – |
| offset | number | – | – |
| search | string | – | – |
No output schema declared.
No examples provided.
tiflux_list_requestors ~84
Busca solicitantes por nome, e-mail ou telefone. Devolve o requestor_id correto para abrir chamado, e não exige perfil de administrador.
| Name | Type | Req | Description |
|---|---|---|---|
| can_open_ticket | boolean | – | – |
| string | – | – | |
| limit | number | – | – |
| name | string | – | – |
| offset | number | – | – |
| telephone | string | – | – |
No output schema declared.
No examples provided.
tiflux_list_technical_groups ~35
Lista os grupos de atendentes da organização.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
tiflux_list_technical_users ~111
Lista os atendentes, com filtro por nome, e-mail, mesa ou cliente. Use para resolver o responsible_id ao atribuir um chamado. Bulk support: accepts desk_ids, client_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | – | – | – |
| client_ids | array | – | – |
| desk_id | – | – | – |
| desk_ids | array | – | – |
| string | – | – | |
| limit | number | – | – |
| name | string | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
tiflux_list_ticket_answers ~48
Lista as respostas (comunicações visíveis ao solicitante) de um chamado.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| offset | number | – | – |
| ticket_number | – | yes | – |
No output schema declared.
No examples provided.
tiflux_list_ticket_appointments ~83
Lista os apontamentos de horas de um chamado. Bulk support: accepts user_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | – |
| limit | number | – | – |
| offset | number | – | – |
| start_date | string | – | – |
| ticket_number | – | yes | – |
| user_id | – | – | – |
| user_ids | array | – | – |
No output schema declared.
No examples provided.
tiflux_list_ticket_files ~40
Lista os arquivos anexados a um chamado.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| offset | number | – | – |
| ticket_number | – | yes | – |
No output schema declared.
No examples provided.
tiflux_list_tickets ~189
Lista chamados com filtros (situação, mesa, cliente, estágio, responsável, solicitante, período, SLA a vencer). Devolve total_items com o total real do filtro, use-o antes de concluir qualquer contagem.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ids | array | – | – |
| date_type | string | – | – |
| desk_ids | array | – | – |
| end_datetime | string | – | – |
| filter_by | string | – | – |
| group_by | string | – | – |
| limit | number | – | – |
| offset | number | – | – |
| priority_ids | array | – | – |
| requestor_email | string | – | – |
| requestor_ids | array | – | – |
| responsible_ids | array | – | – |
| services_catalogs_item_ids | array | – | – |
| sla_expiring_before | string | – | – |
| stage_ids | array | – | – |
| start_datetime | string | – | – |
No output schema declared.
No examples provided.
tiflux_me ~49
Dados do usuário dono do token (nome, e-mail, perfil, feature flags). Use para confirmar em nome de quem as ações serão registradas e qual o escopo de permissão da chave.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tiflux_tickets_feedback_report ~100
Relatório de satisfação (feedback) dos chamados por período, com recorte por responsável, departamento ou grupo de atendentes.
| Name | Type | Req | Description |
|---|---|---|---|
| department_ids | array | – | – |
| end_date | string | – | – |
| limit | number | – | – |
| offset | number | – | – |
| responsible_ids | array | – | – |
| start_date | string | – | – |
| technical_group_ids | array | – | – |
| tickets_list | boolean | – | – |
No output schema declared.
No examples provided.
tiflux_update_ticket ~233
Atualiza um chamado existente. Envie só os campos a alterar. Para mover de estágio use stage_id, para transferir de responsável use responsible_id. Bulk support: accepts client_ids, desk_ids, priority_ids, status_ids, stage_ids, services_catalogs_item_ids, requestor_ids, responsible_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | – | – | – |
| client_ids | array | – | – |
| description | string | – | – |
| desk_id | – | – | – |
| desk_ids | array | – | – |
| followers | string | – | – |
| priority_change_reason | string | – | – |
| priority_id | – | – | – |
| priority_ids | array | – | – |
| requestor_id | – | – | – |
| requestor_ids | array | – | – |
| responsible_id | – | – | – |
| responsible_ids | array | – | – |
| services_catalogs_item_id | – | – | – |
| services_catalogs_item_ids | array | – | – |
| stage_id | – | – | – |
| stage_ids | array | – | – |
| status_id | – | – | – |
| status_ids | array | – | – |
| ticket_number | – | yes | – |
| title | string | – | – |
No output schema declared.
No examples provided.
toolkit_info ~37
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Tiflux MCP server?
Tiflux is an MCP server listed in the public MCP registry as io.github.mcp-dir/tiflux-mcp. Wrapper for the official Tiflux API v2 (help desk and service desk): tickets with replies to the req. This page covers its hosted endpoint (https://api.mcp.ai/p_tiflux).
Is the Tiflux MCP server safe to use?
Tiflux scores 76 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 Tiflux MCP server expose?
Tiflux exposes 36 tools: tiflux_me, tiflux_list_tickets, tiflux_get_tickets, tiflux_create_ticket, tiflux_update_ticket, and 31 more. Their descriptions and schemas cost roughly 3,370 tokens of context every time the server is loaded.
Does the Tiflux MCP server require authentication?
No. We connected to Tiflux without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tiflux MCP server still maintained?
Tiflux is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.