io.github.markusvankempen/mcp-ticket-demo
NPM · MCP-TICKET-DEMO · SCANNED SEP 20
MCP server demo — tickets, schema discovery, auth, and PII gating. stdio + HTTP.
Available components
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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 699 tokens (~77/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
npm · mcp-ticket-demo
claude mcp add markusvankempen-mcp-ticket-demo -- npx -y mcp-ticket-demo
{
"mcpServers": {
"markusvankempen-mcp-ticket-demo": {
"command": "npx",
"args": [
"-y",
"mcp-ticket-demo"
]
}
}
} {
"servers": {
"markusvankempen-mcp-ticket-demo": {
"command": "npx",
"args": [
"-y",
"mcp-ticket-demo"
]
}
}
} codex mcp add markusvankempen-mcp-ticket-demo -- npx -y mcp-ticket-demo
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"markusvankempen-mcp-ticket-demo": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-ticket-demo"
],
"enabled": true
}
}
} openclaw mcp add markusvankempen-mcp-ticket-demo --command npx --arg -y --arg mcp-ticket-demo
mcp_servers:
markusvankempen-mcp-ticket-demo:
command: "npx"
args: ["-y", "mcp-ticket-demo"] {
"McpServers": {
"markusvankempen-mcp-ticket-demo": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-ticket-demo"
]
}
}
} assistant mcp add markusvankempen-mcp-ticket-demo -t stdio -c npx -a -y mcp-ticket-demo
{
"mcpServers": {
"markusvankempen-mcp-ticket-demo": {
"command": "npx",
"args": [
"-y",
"mcp-ticket-demo"
]
}
}
} 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.
- 19 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 56
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 20 Sept 2026 · Analysed npm/mcp-ticket-demo@1.0.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
add_comment ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Who is speaking. Example: ada@example.com |
| body | string | yes | Comment text |
| ticket_id | string | yes | Ticket id. Example: TCK-1001 |
No output schema declared.
No examples provided.
create_ticket ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | 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 | yes | Short subject. Example: Cannot find the deployed MCP URL |
No output schema declared.
No examples provided.
describe_server ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_schema ~41
Describe one schema: fields and filterable keys. Use after list_schemas, before run_query.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Schema name from list_schemas |
No output schema declared.
No examples provided.
get_ticket ~46
Fetch one ticket by id, including comments and attribution. Use when you already have a ticket id.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | string | yes | Ticket id. Example: TCK-1001 |
No output schema declared.
No examples provided.
list_schemas ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_customer ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Customer email. Example: ada@example.com |
No output schema declared.
No examples provided.
run_query ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Optional field projection. Example: ["id","subject"] |
| filter | object | – | Exact-match filters. Example: {"status":"open"} |
| limit | integer | – | – |
| schema | string | yes | Schema from list_schemas |
No output schema declared.
No examples provided.
search_tickets ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
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 20 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 20 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.