CanopiiCanopiiAll serversEnterprise →
io.github.xalantis-hub/xalantis-mcp

io.github.xalantis-hub/xalantis-mcp v0.3.1

Security Trust Score
Grade A · Strong posture
Tier 1 · Public sourceHigh confidence · 98%
Declared MCP capabilities
ResourcesPrompts

Host io.github.xalantis-hub/xalantis-mcp in a governed environment — SSO in front, every tool call attributed and audited.

Reputation0stars0forks159downloads/mo0open issuestodaylast commit<1yage

Security controls

Deterministic, evidence-backed. Score earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

  • Warn
    Strict JSON Schema Enforcementschemas not strict

    Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.

    Fix: Set additionalProperties:false and require explicit parameters on every tool.

  • Pass
    Indirect Prompt Injection (IPI) Defensesguardno injection markers

    Tool/prompt/resource text is free of hidden instructions that could hijack the agent.

  • Pass
    User-in-the-Loop / Approval Scopeguardno destructive tool scope

    No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.

  • N/A
    Tool Definition Integrityguardno prior version to diff

    Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

Application Security Checks

  • Warn
    Has a security policyno security policy

    A SECURITY.md gives a private path to report vulnerabilities.

    Fix: Add SECURITY.md with a disclosure contact and process.

  • Warn
    Dependencies pinned (lockfile)no lockfile found

    A lockfile makes installs reproducible and resistant to silent dependency swaps.

    Fix: Commit a lockfile (package-lock.json / pnpm-lock.yaml / poetry.lock).

  • Warn
    Published with provenanceno provenance attestation

    Build provenance attests the artifact was built from the claimed source by CI.

    Fix: Publish with npm provenance (--provenance) from a trusted CI.

  • Warn
    Established maintainersingle maintainer

    Brand-new / single anonymous maintainers raise takeover and malware risk.

    Fix: Publish under an established account/org; add multiple maintainers.

  • Warn
    Declares a licenseno recognized license

    A clear license is required for legal enterprise use.

    Fix: Add a recognized SPDX license (MIT, Apache-2.0, …).

  • Pass
    Adoption & popularityestablished adoption

    A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.

  • Pass
    No command-injection sinksguardno sinks found

    Untrusted tool input reaching a shell yields remote code execution.

  • Pass
    No dynamic code executionguardno sinks found

    eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.

  • Pass
    No path traversalguardno sinks found

    Naive path checks let tools read/write outside intended directories (EscapeRoute-class).

  • Pass
    No SSRF sinksguardno sinks found

    Fetching tool-supplied URLs can pivot into internal networks and metadata services.

  • Pass
    No unsafe deserializationguardno sinks found

    pickle/yaml.load/etc. on untrusted data can execute code.

  • Pass
    No committed secretsguardno secrets found

    Hardcoded keys/tokens in published source are live credentials an attacker can use.

  • Pass
    Credentials sourced from environmentreads credentials from environment

    Reading secrets from env/secret stores avoids hardcoding them.

  • Pass
    No known-vulnerable dependencies1 runtime deps, no known CVEs

    Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.

  • Pass
    No install/post-install scriptsguardno install scripts

    install hooks run arbitrary code on every consumer at install time.

  • Pass
    Package name not typosquattingguarddistinct package name

    Names mimicking popular packages are a common malware delivery vector.

  • Pass
    Actively maintainedrecent commits

    Unmaintained servers don't receive security fixes.

  • Pass
    Repository not archivedguardactive

    Archived repositories will never be patched.

  • Not checked
    Signed releasesnot evaluated

    Signed releases let consumers verify artifacts weren't tampered with.

Transport & Trust Model

  • Warn
    Execution Sandboxingruns natively (no container image)

    A container/sandbox image limits blast radius; a server that runs natively has full host access.

    Fix: Ship a Dockerfile/Containerfile (or document a sandboxed run) so the server runs isolated.

  • Pass
    Network Exposureno bind-all detected

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

  • N/A
    Transport Encryption (TLS)guardno remote endpoints

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • N/A
    IAM / Authentication Scopingno remote endpoints

    OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.

  • N/A
    Live Endpoint Reachablenot dynamically scanned

    A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.

  • N/A
    Authentication Enforced (live)not dynamically scanned

    If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Tools (80)

get_ticketlink_ticketlist_ticketscreate_ticketdelete_tickettriage_ticketunlink_ticketupdate_ticketcall_operationlist_${prefix}list_knowledgelist_pipelinesread_operationescalate_ticketreply_to_ticketget_agent_statuslist_ticket_tagssearch_knowledgedeescalate_ticketlist_sla_breacheslist_sla_policieslist_ticket_linkssearch_operationstoggle_ticket_tagcreate_${baseName}delete_${baseName}describe_operationget_ticket_metricsretry_ticket_replyupdate_${baseName}bulk_update_ticketsdelete_ticket_replylist_ticket_replieslist_ticket_reportsupdate_agent_statusupdate_ticket_replycreate_ticket_reportlist_service_cataloglist_ticket_watchersget_knowledge_articletoggle_ticket_watcheracknowledge_sla_breachdownload_ticket_reportget_knowledge_taxonomylist_ticket_activitieslist_ticket_categorieslist_ticket_attachmentscreate_escalation_policycreate_knowledge_articlecreate_ticket_time_entrydelete_ticket_attachmentget_service_catalog_itemlist_escalation_policieslist_ticket_time_entriesupdate_escalation_policyupdate_knowledge_articleupload_ticket_attachmentlist_knowledge_categoriesadmin_list_service_catalogdownload_ticket_attachmentget_${prefix.slice(0, -1)}get_ticket_incident_reportreorder_ticket_automationslist_client_representativescreate_client_representativelist_ticket_incident_updateslist_ticket_merge_candidatescreate_${prefix.slice(0, -1)}create_ticket_incident_updatedelete_${prefix.slice(0, -1)}get_managed_knowledge_articleupdate_${prefix.slice(0, -1)}acknowledge_requester_responselist_managed_knowledge_articleslist_ticket_duplicate_candidateslist_ticket_automation_executionslist_ticket_escalation_executionscreate_service_request_from_catalogget_archived_ticket_incident_reportsubmit_knowledge_article_for_review