# io.github.markusvankempen/mcp-ticket-demo (npm · mcp-ticket-demo)

MCP server demo — tickets, schema discovery, auth, and PII gating. stdio + HTTP.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `mcp-ticket-demo`: 71/100 (this document), [markdown](https://verifymcp.io/servers/markusvankempen-mcp-ticket-demo/mcp-ticket-demo.md), [page](https://verifymcp.io/servers/markusvankempen-mcp-ticket-demo/mcp-ticket-demo)

## Channel facts

- Registry: `npm`
- Package: `mcp-ticket-demo`
- Version: `1.0.4`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 699 tokens (~77/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.markusvankempen/mcp-ticket-demo server?

io.github.markusvankempen/mcp-ticket-demo runs locally as an npm package, launched with npx -y mcp-ticket-demo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add markusvankempen-mcp-ticket-demo -- npx -y mcp-ticket-demo
```

### Cursor

```json
{
  "mcpServers": {
    "markusvankempen-mcp-ticket-demo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ticket-demo"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "markusvankempen-mcp-ticket-demo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ticket-demo"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add markusvankempen-mcp-ticket-demo -- npx -y mcp-ticket-demo
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "markusvankempen-mcp-ticket-demo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-ticket-demo"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add markusvankempen-mcp-ticket-demo --command npx --arg -y --arg mcp-ticket-demo
```

### Hermes

```yaml
mcp_servers:
  markusvankempen-mcp-ticket-demo:
    command: "npx"
    args: ["-y", "mcp-ticket-demo"]
```

### Netclaw

```json
{
  "McpServers": {
    "markusvankempen-mcp-ticket-demo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-ticket-demo"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add markusvankempen-mcp-ticket-demo -t stdio -c npx -a -y mcp-ticket-demo
```

### Other

```json
{
  "mcpServers": {
    "markusvankempen-mcp-ticket-demo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ticket-demo"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-18 (score 56)

First indexed and scored.

## MCP tools (9)

### `search_tickets` (~113 tokens)

Search support tickets by status, requester, or keyword. Use this when a human asks to find or list tickets — not request(path, method). Empty results mean no tickets match those filters; do not retry the same call.

Input parameters:

- `limit` (integer): Max rows. Default 10
- `query` (string): Keyword against subject and body. Example: hostname
- `requester_email` (string): Real customer email. Example: ada@example.com
- `status` (string): Ticket status. Example: open

### `create_ticket` (~137 tokens)

Open a support ticket on behalf of a customer. ALWAYS pass requester_email as the real customer. If you omit it the HTTP call still returns 201, but the service account owns the ticket and every email reply goes to the bot. A tool is not done when the API call succeeds — it is done when the next thing that happens is right.

Input parameters:

- `body` (string, required): What happened, in the customer's words
- `requester_email` (string): Real customer email. Example: ada@example.com. Omit this only to reproduce the attribution scar.
- `subject` (string, required): Short subject. Example: Cannot find the deployed MCP URL

### `add_comment` (~89 tokens)

Add a comment to an existing ticket. Use after search_tickets or get_ticket. Author should be the person speaking, not the bot, unless you mean to comment as the service account.

Input parameters:

- `author` (string): Who is speaking. Example: ada@example.com
- `body` (string, required): Comment text
- `ticket_id` (string, required): Ticket id. Example: TCK-1001

### `get_ticket` (~46 tokens)

Fetch one ticket by id, including comments and attribution. Use when you already have a ticket id.

Input parameters:

- `ticket_id` (string, required): Ticket id. Example: TCK-1001

### `list_schemas` (~42 tokens)

List queryable schemas. Use this BEFORE run_query. This is the replacement for a pile of query_* tools — discover the shape, then run one query tool.

### `get_schema` (~41 tokens)

Describe one schema: fields and filterable keys. Use after list_schemas, before run_query.

Input parameters:

- `name` (string, required): Schema name from list_schemas

### `run_query` (~96 tokens)

Run one query against a discovered schema. Prefer this over inventing query_tickets, query_assets, or query_with_filter — those names are technically precise and operationally confusing.

Input parameters:

- `fields` (array): Optional field projection. Example: ["id","subject"]
- `filter` (object): Exact-match filters. Example: {"status":"open"}
- `limit` (integer)
- `schema` (string, required): Schema from list_schemas

### `lookup_customer` (~67 tokens)

Look up a customer record. Phone number is PII. When tool security is on, this requires the demo bearer token. When it is off, the phone is redacted so the laptop demo stays boring on purpose.

Input parameters:

- `email` (string, required): Customer email. Example: ada@example.com

### `describe_server` (~68 tokens)

Discover this server before you call anything else: identity, transport, auth mode, who the server thinks you are, which scopes you hold, your rate-limit budget, and every tool with the scope it needs. Call this first when a call was denied — it tells you exactly which credential is missing.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/markusvankempen-mcp-ticket-demo/mcp-ticket-demo#diagnostics

## Score history

- 2026-09-21: 71
- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 56

## Common questions

### What is the io.github.markusvankempen/mcp-ticket-demo server?

io.github.markusvankempen/mcp-ticket-demo is listed in the public MCP registry as io.github.markusvankempen/mcp-ticket-demo. MCP server demo, tickets, schema discovery, auth, and PII gating. stdio + HTTP. This page covers its npm package (mcp-ticket-demo).

### Is the io.github.markusvankempen/mcp-ticket-demo server safe to use?

io.github.markusvankempen/mcp-ticket-demo scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.markusvankempen/mcp-ticket-demo server expose?

io.github.markusvankempen/mcp-ticket-demo exposes 9 tools: search_tickets, create_ticket, add_comment, get_ticket, list_schemas, and 4 more. Their descriptions and schemas cost roughly 699 tokens of context every time the server is loaded.

### Is the io.github.markusvankempen/mcp-ticket-demo server still maintained?

io.github.markusvankempen/mcp-ticket-demo is still listed as active in the MCP registry. We last reached this channel on 21 September 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 io.github.markusvankempen/mcp-ticket-demo server under?

io.github.markusvankempen/mcp-ticket-demo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/mcp-ticket-demo
- Socket report: https://socket.dev/npm/package/mcp-ticket-demo
- Repository: https://github.com/markusvankempen/mcp-ticket-demo
- Changelog RSS feed: https://verifymcp.io/servers/markusvankempen-mcp-ticket-demo/mcp-ticket-demo.xml
- Changelog JSON feed: https://verifymcp.io/servers/markusvankempen-mcp-ticket-demo/mcp-ticket-demo.json
- HTML version of this page: https://verifymcp.io/servers/markusvankempen-mcp-ticket-demo/mcp-ticket-demo