Osticket (tecnologicachile) MCP Server

mcp-osticket npm v2.7.2

Published by tecnologicachile — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for osTicket — manage helpdesk tickets from Claude Code, Cursor, Windsurf, or any MCP client

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Hardcoded egress to an external endpoint (dist/mcp-server.js)MTC-SRC-003

In the server's implementation (`dist/mcp-server.js:48`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const res = await fetch(`https://registry.npmjs.org/${NPM_PACKAGE}/latest`); if (res.ok) { con

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/mcp-server.js

Tools 53

Each tool and what it can reach — statically extracted from the published source.

  • get_fileingests untrusted input
  • add_collaboratorno sensitive capability
  • add_noteno sensitive capability
  • add_task_noteno sensitive capability
  • assign_taskno sensitive capability
  • assign_ticketno sensitive capability
  • change_ticket_statusno sensitive capability
  • claim_ticketno sensitive capability
  • close_taskno sensitive capability
  • create_help_topicno sensitive capability
Show 43 more tools ↓
  • create_organizationno sensitive capability
  • create_taskno sensitive capability
  • create_ticketno sensitive capability
  • create_ticket_filterno sensitive capability
  • create_userno sensitive capability
  • delete_help_topicno sensitive capability
  • delete_organizationno sensitive capability
  • delete_ticketno sensitive capability
  • delete_ticket_filterno sensitive capability
  • delete_userno sensitive capability
  • edit_help_topicno sensitive capability
  • edit_ticketno sensitive capability
  • edit_ticket_filterno sensitive capability
  • get_dashboard_statsno sensitive capability
  • get_organizationno sensitive capability
  • get_queue_countsno sensitive capability
  • get_taskno sensitive capability
  • get_ticketno sensitive capability
  • get_ticket_filterno sensitive capability
  • get_userno sensitive capability
  • list_agentsno sensitive capability
  • list_attachmentsno sensitive capability
  • list_canned_responsesno sensitive capability
  • list_collaboratorsno sensitive capability
  • list_departmentsno sensitive capability
  • list_help_topicsno sensitive capability
  • list_organizationsno sensitive capability
  • list_slasno sensitive capability
  • list_tasksno sensitive capability
  • list_ticket_eventsno sensitive capability
  • list_ticket_filtersno sensitive capability
  • list_ticketsno sensitive capability
  • mark_ticketno sensitive capability
  • merge_ticketsno sensitive capability
  • remove_collaboratorno sensitive capability
  • reopen_taskno sensitive capability
  • reply_ticketno sensitive capability
  • search_organizationsno sensitive capability
  • search_ticketsno sensitive capability
  • search_usersno sensitive capability
  • transfer_taskno sensitive capability
  • transfer_ticketno sensitive capability
  • update_userno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.7.2 latest A 96/100 1 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-osticket/badge.svg)](https://mcptrustchecker.com/registry/mcp-osticket)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-osticket"><img src="https://mcptrustchecker.com/registry/mcp-osticket/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-osticket/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-osticket --online

Use the free API → How scoring works

Other implementations of Osticket 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Productivity & Workflow