Xalantis MCP Server

@xalantis/mcp-server npm v0.2.0

Published by @xalantis — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for Xalantis — manage support tickets from Claude, Cursor, and other AI tools

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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 = 95/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 − 5 = 95. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 2

medium Tool "unlink_ticket" can modify the filesystemMTC-CAP-002

Tool "unlink_ticket" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool unlink_ticket

low Mutating tool "unlink_ticket" declares no destructiveHintMTC-CAP-005

Tool "unlink_ticket" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool unlink_ticket

Tools 84

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

  • download_ticket_attachmentingests untrusted input
  • download_ticket_reportingests untrusted input
  • unlink_ticketwrites files
  • acknowledge_requester_responseno sensitive capability
  • acknowledge_sla_breachno sensitive capability
  • add_contract_commentno sensitive capability
  • admin_list_service_catalogno sensitive capability
  • bulk_update_ticketsno sensitive capability
  • create_client_representativeno sensitive capability
  • create_contract_negotiationno sensitive capability
Show 74 more tools ↓
  • create_contract_obligationno sensitive capability
  • create_contract_requestno sensitive capability
  • create_escalation_policyno sensitive capability
  • create_service_request_from_catalogno sensitive capability
  • create_ticketno sensitive capability
  • create_ticket_incident_updateno sensitive capability
  • create_ticket_reportno sensitive capability
  • create_ticket_time_entryno sensitive capability
  • deescalate_ticketno sensitive capability
  • delete_contract_commentno sensitive capability
  • delete_ticketno sensitive capability
  • delete_ticket_attachmentno sensitive capability
  • delete_ticket_replyno sensitive capability
  • escalate_ticketno sensitive capability
  • get_agent_statusno sensitive capability
  • get_archived_ticket_incident_reportno sensitive capability
  • get_billing_invoiceno sensitive capability
  • get_billing_subscriptionno sensitive capability
  • get_contract_requestno sensitive capability
  • get_finance_expenseno sensitive capability
  • get_finance_invoiceno sensitive capability
  • get_knowledge_articleno sensitive capability
  • get_service_catalog_itemno sensitive capability
  • get_ticketno sensitive capability
  • get_ticket_incident_reportno sensitive capability
  • get_ticket_metricsno sensitive capability
  • link_ticketno sensitive capability
  • list_billing_invoicesno sensitive capability
  • list_client_representativesno sensitive capability
  • list_contract_commentsno sensitive capability
  • list_contract_negotiationsno sensitive capability
  • list_contract_obligationsno sensitive capability
  • list_contract_requestsno sensitive capability
  • list_escalation_policiesno sensitive capability
  • list_finance_expensesno sensitive capability
  • list_finance_invoicesno sensitive capability
  • list_knowledgeno sensitive capability
  • list_knowledge_categoriesno sensitive capability
  • list_pipelinesno sensitive capability
  • list_service_catalogno sensitive capability
  • list_sla_breachesno sensitive capability
  • list_sla_policiesno sensitive capability
  • list_ticket_activitiesno sensitive capability
  • list_ticket_attachmentsno sensitive capability
  • list_ticket_automation_executionsno sensitive capability
  • list_ticket_categoriesno sensitive capability
  • list_ticket_duplicate_candidatesno sensitive capability
  • list_ticket_escalation_executionsno sensitive capability
  • list_ticket_incident_updatesno sensitive capability
  • list_ticket_linksno sensitive capability
  • list_ticket_merge_candidatesno sensitive capability
  • list_ticket_repliesno sensitive capability
  • list_ticket_reportsno sensitive capability
  • list_ticket_tagsno sensitive capability
  • list_ticket_time_entriesno sensitive capability
  • list_ticket_watchersno sensitive capability
  • list_ticketsno sensitive capability
  • reorder_ticket_automationsno sensitive capability
  • reply_to_ticketno sensitive capability
  • request_contract_signaturesno sensitive capability
  • resolve_contract_negotiationno sensitive capability
  • retry_ticket_replyno sensitive capability
  • search_knowledgeno sensitive capability
  • submit_contract_for_approvalno sensitive capability
  • toggle_ticket_tagno sensitive capability
  • toggle_ticket_watcherno sensitive capability
  • triage_ticketno sensitive capability
  • update_agent_statusno sensitive capability
  • update_contract_commentno sensitive capability
  • update_contract_obligationno sensitive capability
  • update_escalation_policyno sensitive capability
  • update_ticketno sensitive capability
  • update_ticket_replyno sensitive capability
  • upload_ticket_attachmentno sensitive capability

What this scan could not see

Versions 2

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
v0.2.0 latest A 95/100 2 1.13.0 2026-09-07
v0.1.0 A 98/100 0 1.12.1 2026-07-28

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/xalantis-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/xalantis-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/xalantis-mcp-server"><img src="https://mcptrustchecker.com/registry/xalantis-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/xalantis-mcp-server/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 @xalantis/mcp-server --online

Use the free API → How scoring works

More in Productivity & Workflow