Xenmark
NPM · XENMARK-MCP · SCANNED SEP 20
Read your Xenmark drawing reviews from AI assistants: projects, drawings, comments, notifications.
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 & Transparency48
- 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 16 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 745 tokens (~82/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 Management57
- Stability observed for 17 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
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
How do I install the Xenmark MCP server?
Xenmark runs locally as an npm package, launched with npx -y xenmark-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · xenmark-mcp
claude mcp add xenmark-xenmark-mcp -- npx -y xenmark-mcp
{
"mcpServers": {
"xenmark-xenmark-mcp": {
"command": "npx",
"args": [
"-y",
"xenmark-mcp"
]
}
}
} {
"servers": {
"xenmark-xenmark-mcp": {
"command": "npx",
"args": [
"-y",
"xenmark-mcp"
]
}
}
} codex mcp add xenmark-xenmark-mcp -- npx -y xenmark-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xenmark-xenmark-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"xenmark-mcp"
],
"enabled": true
}
}
} openclaw mcp add xenmark-xenmark-mcp --command npx --arg -y --arg xenmark-mcp
mcp_servers:
xenmark-xenmark-mcp:
command: "npx"
args: ["-y", "xenmark-mcp"] {
"McpServers": {
"xenmark-xenmark-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"xenmark-mcp"
]
}
}
} assistant mcp add xenmark-xenmark-mcp -t stdio -c npx -a -y xenmark-mcp
{
"mcpServers": {
"xenmark-xenmark-mcp": {
"command": "npx",
"args": [
"-y",
"xenmark-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 4 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Sept 26 57
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/xenmark-mcp@0.1.2
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 →
xenmark_find_drawing ~105
Find drawings by drawing number or name fragment across the user's projects (or within one project) and return their ids, project, revision_count and web_url. Use this when the user names a drawing rather than an id. Walks at most 20 projects and says so if truncated.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Limit the search to one project. |
| query | string | yes | Drawing number or part of the name, e.g. "1001-300". |
No output schema declared.
No examples provided.
xenmark_list_comments ~115
Comments on one revision: id, comment_number (quote this to people), title, description, status, author_display_name, page, reply_count, annotation_count, web_url, plus a replies_preview of up to 3 replies and replies_truncated.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque cursor from a previous result's next_cursor, to fetch the next page. |
| include_replies_preview | boolean | – | Include up to 3 replies per comment (default true). |
| revision_id | string | yes | Revision UUID. |
No output schema declared.
No examples provided.
xenmark_list_drawings ~82
Drawings in one project: id, drawing_number, name, revision_count, created_at, web_url. Needs the project id from xenmark_list_projects or xenmark_find_drawing.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque cursor from a previous result's next_cursor, to fetch the next page. |
| project_id | string | yes | Project UUID. |
No output schema declared.
No examples provided.
xenmark_list_projects ~71
Projects the user owns or is a member of: id, name, description, company_name, status (active/archived), my_role, created_at, updated_at, web_url.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque cursor from a previous result's next_cursor, to fetch the next page. |
No output schema declared.
No examples provided.
xenmark_list_replies ~67
All replies on one comment, paginated: id, author_display_name, body, created_at, edited_at.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | Comment UUID. |
| cursor | string | – | Opaque cursor from a previous result's next_cursor, to fetch the next page. |
No output schema declared.
No examples provided.
xenmark_list_revisions ~76
Revisions of one drawing: id, revision_label, original_filename, size_bytes, content_type, created_at, web_url. Files themselves are never available.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque cursor from a previous result's next_cursor, to fetch the next page. |
| drawing_id | string | yes | Drawing UUID. |
No output schema declared.
No examples provided.
xenmark_recent_activity ~125
The user's Xenmark notification inbox, newest first: new comments, replies, mentions and status changes on drawings the user is part of. Each row has actor_name, project_name, drawing_number, revision_label, comment_number, title, preview, mention_labels, old_status/new_status (status changes), read, created_at and a web_url deep link into Xenmark. Use web_url for links - never build Xenmark URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows to return (default 30, max 100). |
| unread_only | boolean | – | Only unread notifications. |
No output schema declared.
No examples provided.
xenmark_review_summary ~64
Comment-status rollup for one or more revisions (up to 100): total_comments, open_count, progress_count, closed_count, last_activity_at per revision. Revisions the user cannot access are silently omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| revision_ids | array | yes | Revision UUIDs. |
No output schema declared.
No examples provided.
xenmark_whoami ~40
Identify the Xenmark account behind the configured token: user_id, display_name, company. Never returns e-mail, plan, billing or role.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Xenmark MCP server?
Xenmark is an MCP server listed in the public MCP registry as io.github.Xenmark/xenmark-mcp. Read your Xenmark drawing reviews from AI assistants: projects, drawings, comments, notifications. This page covers its npm package (xenmark-mcp).
Is the Xenmark MCP server safe to use?
Xenmark scores 80 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 Xenmark MCP server expose?
Xenmark exposes 9 tools: xenmark_whoami, xenmark_recent_activity, xenmark_list_projects, xenmark_list_drawings, xenmark_list_revisions, and 4 more. Their descriptions and schemas cost roughly 745 tokens of context every time the server is loaded.
Is the Xenmark MCP server still maintained?
Xenmark 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 Xenmark MCP server under?
Xenmark declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.