NexTool MCP for GLPI
NPM · @NEXTOOLSOLUTIONS/MCP-GLPI · 2 COMPONENTS
MCP server for GLPI: tickets, ITIL, assets, knowledge base. GLPI 10/11. Not affiliated with Teclib'.
Available components
Last scanned (20 hours ago)
Scores higher than 88% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to NexTools-Solutions/nextool-mcp-glpi). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 11213 tokens (~97/item across 115 items; 111 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- Manipulation not yet verified: none of the 113 captured unit(s) of tool text has been judged yet, so we will not certify text no model has read as clean.Unverified
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 12 Oct 26 +2
- Security disclosure: pass → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- 7 Oct 26 +48
- Malware scan: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: unverified security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- Package version: 3.5.2 → 3.5.5 functional
- 5 Oct 26 34
First indexed and scored.
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 16 Oct 2026 · Analysed npm/@nextoolsolutions/mcp-glpi@3.5.5
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | NexTools-Solutions/nextool-mcp-glpi |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/NexTools-Solutions/nextool-mcp-glpi/.github/workflows/release.yml@refs/tags/v3.5.5 |
| Rekor log index | 3098582357 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b7a728e9abd4e8e1bf07349f66ad0886650e4c868f1ae8747701efb95076a1ad61147b25626be7834117b61520411b8eebfd8984867b279ef3bbf4a8f |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
glpi_search_user_by_email Search user by email ~128
Find users by exact email address (returns the user items: id, login, real name, first name...).
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address | |
| fields | string | – | Field set: 'essential' (default, trims internal GLPI fields) or 'all' |
| format | string | – | Output format: 'json' (default) or 'markdown' (a table for listings, key/value lines for one item; returned in both the text and the structured result) |
| range | string | – | Pagination range, e.g. 0-49 |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Items in this page |
| data | – | – | – |
| format | string | – | 'markdown' when data holds the markdown rendering |
| note | string | – | Pagination hint: how to fetch the next page |
No examples provided.
glpi_set_webhook_active Enable or disable webhook ~51
Turn a webhook on or off without touching the rest of its definition.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | yes | true turns the webhook on, false turns it off |
| webhookId | – | yes | Item ID |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_asset Update asset ~62
Update an existing asset by type and ID.
| Name | Type | Req | Description |
|---|---|---|---|
| assetId | – | yes | Item ID |
| asset_type | string | yes | Asset itemtype, e.g. Computer, Monitor, Printer, NetworkEquipment, Software |
| input | object | yes | Fields to update |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_change Update change ~35
Update an existing change by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| changeId | – | yes | Item ID |
| input | object | yes | Fields to update |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_entity Update entity ~35
Update an existing entity by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| entityId | – | yes | Entity ID |
| input | object | yes | Fields to update |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_itil_followup_template Update followup template ~40
Update a followup template by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Fields to update |
| templateId | – | yes | Item ID |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_knowbase_category Update knowledge base category ~39
Update a knowledge base category by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| categoryId | – | yes | Item ID |
| input | object | yes | Fields to update |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_knowbase_item Update knowledge base item ~40
Update a knowledge base article by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Fields to update |
| knowbaseId | – | yes | Item ID |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_problem Update problem ~35
Update an existing problem by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Fields to update |
| problemId | – | yes | Item ID |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_reservation Update reservation ~45
Update an existing reservation by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Fields to update (begin, end, comment, users_id) |
| reservationId | – | yes | Item ID |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_rule_action Update rule action ~52
Update a rule action by ID. Fields: action_type, field, value.
| Name | Type | Req | Description |
|---|---|---|---|
| actionId | – | yes | Item ID |
| input | object | yes | Fields to update (action_type, field, value) |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_ticket Update ticket ~35
Update an existing ticket by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Fields to update |
| ticketId | – | yes | Item ID |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_ticket_validation Update ticket validation ~62
Approve/refuse a validation (status: accepted/refused) or change the approver.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | e.g. {status: 'accepted'} or {users_id_validate: 2} |
| validationId | – | yes | Item ID |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_user Update user ~35
Update an existing user by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Fields to update |
| userId | – | yes | Item ID |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
glpi_update_webhook Update webhook ~60
Update a webhook definition by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Webhook fields to change (e.g. { "url": "https://example.com/hook", "is_active": 1 }) |
| webhookId | – | yes | Item ID |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
How do I install the NexTool MCP for GLPI server?
NexTool MCP for GLPI runs locally as an npm package, launched with npx -y @nextoolsolutions/mcp-glpi. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @nextoolsolutions/mcp-glpi
claude mcp add com-nextoolsolutions-glpi -- npx -y @nextoolsolutions/mcp-glpi
What is the NexTool MCP for GLPI server?
NexTool MCP for GLPI is listed in the public MCP registry as com.nextoolsolutions/glpi. MCP server for GLPI: tickets, ITIL, assets, knowledge base. GLPI 10/11. Not affiliated with Teclib'. This page covers its npm package (@nextoolsolutions/mcp-glpi).
Is the NexTool MCP for GLPI server safe to use?
NexTool MCP for GLPI scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 NexTool MCP for GLPI server expose?
NexTool MCP for GLPI exposes 111 tools: glpi_list_tickets, glpi_list_my_tickets, glpi_get_ticket, glpi_create_ticket, glpi_update_ticket, and 106 more. Their descriptions and schemas cost roughly 10,850 tokens of context every time the server is loaded.
Is the NexTool MCP for GLPI server still maintained?
NexTool MCP for GLPI is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the NexTool MCP for GLPI server under?
NexTool MCP for GLPI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.