Invgate Service Desk MCP Server

invgate-service-desk-mcp PyPI v0.2.0

Published by tracegazer — 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.

InvGate Service Desk MCP — 96 tools across 11 domains (incidents, users, knowledge base, assets, time tracking), read-only by default with a 3-tier write access model (none/support/full), and built-in OpenTelemetry observability.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 1 = 99. 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
−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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 96

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

  • accept_incident_approvalno sensitive capability
  • accept_incident_solutionno sensitive capability
  • add_incident_approval_voterno sensitive capability
  • add_incident_collaboratorno sensitive capability
  • add_incident_commentno sensitive capability
  • add_incident_observerno sensitive capability
  • cancel_incidentno sensitive capability
  • cancel_incident_approvalno sensitive capability
  • create_incidentno sensitive capability
  • create_incident_spontaneous_approvalno sensitive capability
Show 86 more tools ↓
  • create_kb_articleno sensitive capability
  • delete_incident_custom_fieldno sensitive capability
  • delete_kb_articleno sensitive capability
  • delete_time_entryno sensitive capability
  • find_usersno sensitive capability
  • get_breaking_newsno sensitive capability
  • get_breaking_news_statusno sensitive capability
  • get_cis_by_idno sensitive capability
  • get_custom_field_configno sensitive capability
  • get_custom_field_list_configno sensitive capability
  • get_custom_field_list_optionsno sensitive capability
  • get_custom_field_tree_optionsno sensitive capability
  • get_incidentno sensitive capability
  • get_incident_commentsno sensitive capability
  • get_kb_article_attachmentsno sensitive capability
  • get_kb_articles_by_idsno sensitive capability
  • get_kb_categories_by_idsno sensitive capability
  • get_linked_assets_countersno sensitive capability
  • get_linked_cis_countersno sensitive capability
  • get_starting_fields_by_categoryno sensitive capability
  • get_userno sensitive capability
  • get_user_groupsno sensitive capability
  • get_workflow_field_list_valuesno sensitive capability
  • get_workflow_initial_fieldsno sensitive capability
  • get_workflow_processno sensitive capability
  • link_incidentno sensitive capability
  • link_incident_to_external_entityno sensitive capability
  • list_breaking_newsno sensitive capability
  • list_breaking_news_statusesno sensitive capability
  • list_breaking_news_typesno sensitive capability
  • list_categoriesno sensitive capability
  • list_companiesno sensitive capability
  • list_company_groupsno sensitive capability
  • list_company_membersno sensitive capability
  • list_company_observersno sensitive capability
  • list_custom_field_typesno sensitive capability
  • list_custom_fieldsno sensitive capability
  • list_custom_fields_by_categoryno sensitive capability
  • list_group_membersno sensitive capability
  • list_groupsno sensitive capability
  • list_helpdesk_levelsno sensitive capability
  • list_helpdesk_observersno sensitive capability
  • list_helpdesksno sensitive capability
  • list_helpdesks_and_levelsno sensitive capability
  • list_incident_typesno sensitive capability
  • list_incidents_by_agentno sensitive capability
  • list_incidents_by_assetno sensitive capability
  • list_incidents_by_cisno sensitive capability
  • list_incidents_by_customerno sensitive capability
  • list_incidents_by_helpdeskno sensitive capability
  • list_incidents_by_statusno sensitive capability
  • list_kb_articlesno sensitive capability
  • list_kb_articles_by_categoryno sensitive capability
  • list_kb_categoriesno sensitive capability
  • list_level_observersno sensitive capability
  • list_location_membersno sensitive capability
  • list_location_observersno sensitive capability
  • list_locationsno sensitive capability
  • list_prioritiesno sensitive capability
  • list_requests_related_to_assetsno sensitive capability
  • list_shared_custom_fieldsno sensitive capability
  • list_sourcesno sensitive capability
  • list_statusesno sensitive capability
  • list_time_trackingno sensitive capability
  • list_time_tracking_categoriesno sensitive capability
  • list_trigger_executionsno sensitive capability
  • list_triggersno sensitive capability
  • list_usersno sensitive capability
  • log_timeno sensitive capability
  • promote_incident_to_majorno sensitive capability
  • reassign_incidentno sensitive capability
  • reject_incidentno sensitive capability
  • reject_incident_approvalno sensitive capability
  • reject_incident_solutionno sensitive capability
  • relate_incident_to_cis_by_keywordno sensitive capability
  • reopen_incidentno sensitive capability
  • request_incident_custom_approvalno sensitive capability
  • search_kb_articlesno sensitive capability
  • set_incident_custom_fieldno sensitive capability
  • set_incident_waiting_for_agentno sensitive capability
  • set_incident_waiting_for_customerno sensitive capability
  • set_incident_waiting_for_dateno sensitive capability
  • set_incident_waiting_for_external_entityno sensitive capability
  • set_incident_waiting_for_incidentno sensitive capability
  • update_incidentno sensitive capability
  • update_kb_articleno 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
v0.2.0 latest A 99/100 0 1.13.0 2026-08-25

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

Use the free API → How scoring works

More in Developer Tools