com.sketchxflow/dev-mcp
NPM · @SKETCHXFLOW/DEV-MCP · 2 COMPONENTS
SketchXFlow delivery team: pull client requirements, post updates, log time, move milestones.
Available components
Last scanned (21 hours ago)
Scores higher than 39% of npm servers
Category Project Management
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 54 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 572 tokens (~63/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 11% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.93 functional
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/@sketchxflow/dev-mcp@0.4.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
sketchxflow_dev_log_time Log hours ~90
Log hours worked on a project (coarse — a day's hours), optionally against a module key or milestone. Team members only.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | number | yes | – |
| milestone_id | string | – | – |
| module_key | string | – | – |
| note | string | – | – |
| project_id | string | yes | – |
| worked_on | string | – | YYYY-MM-DD; default today |
No output schema declared.
No examples provided.
sketchxflow_dev_login Sign in to the developer MCP ~83
Sign this machine in as a SketchXFlow team member — no API key to paste. Returns a link and a short code: the developer opens the link in a browser where they are signed in to the staff console, checks the code matches and approves. Call it again (or any other tool) after approving. Already signed in? It says who as.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sketchxflow_dev_logout Sign out of the developer MCP ~43
Forget this machine's key. To end it server-side as well, revoke the key named “Developer MCP · <machine>” in Account → API keys.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sketchxflow_dev_message Message the client (or the team) ~53
Send a message in the project room. internal=true keeps it to the team. Team members only.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| internal | boolean | – | – |
| project_id | string | yes | – |
No output schema declared.
No examples provided.
sketchxflow_dev_milestone Start or submit a milestone ~60
Mark a milestone as started, or submit it for the client's review (which starts their review window). Team members only.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| milestone_id | string | yes | – |
| project_id | string | yes | – |
No output schema declared.
No examples provided.
sketchxflow_dev_pull Pull a project's requirements to build ~49
The frozen requirements as text, the priced modules, the milestones with dates and the latest client messages — everything needed to start building. Team members only.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
No output schema declared.
No examples provided.
sketchxflow_dev_update Post a progress update ~65
Post a progress update the client sees in their project room (markdown), optionally against a milestone. Team members only.
| Name | Type | Req | Description |
|---|---|---|---|
| body_md | string | yes | – |
| milestone_id | string | – | – |
| project_id | string | yes | – |
| title | string | – | – |
No output schema declared.
No examples provided.
sketchxflow_dev_version Check the developer MCP version and whether you're on the team ~74
Report which version of the SketchXFlow developer MCP is running, whether a newer one is published, and whether the configured SKETCHXFLOW_API_KEY (shown only by its sk_live_ab12cd… prefix) belongs to an active SketchXFlow team member. Free. Call it first when another tool refuses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sketchxflow_dev_work Projects on your plate ~55
Live development-services projects assigned to you, with state, progress and what needs attention. Set mine=false for every live project. Team members only.
| Name | Type | Req | Description |
|---|---|---|---|
| mine | boolean | – | Only projects assigned to me (default true). |
No output schema declared.
No examples provided.
How do I install the com.sketchxflow/dev-mcp server?
com.sketchxflow/dev-mcp runs locally as an npm package, launched with npx -y @sketchxflow/dev-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 · @sketchxflow/dev-mcp
claude mcp add com-sketchxflow-dev-mcp -- npx -y @sketchxflow/dev-mcp
What is the com.sketchxflow/dev-mcp server?
com.sketchxflow/dev-mcp is listed in the public MCP registry as com.sketchxflow/dev-mcp. SketchXFlow delivery team: pull client requirements, post updates, log time, move milestones. This page covers its npm package (@sketchxflow/dev-mcp).
Is the com.sketchxflow/dev-mcp server safe to use?
com.sketchxflow/dev-mcp scores 69 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 com.sketchxflow/dev-mcp server expose?
com.sketchxflow/dev-mcp exposes 9 tools: sketchxflow_dev_login, sketchxflow_dev_logout, sketchxflow_dev_version, sketchxflow_dev_work, sketchxflow_dev_pull, and 4 more. Their descriptions and schemas cost roughly 572 tokens of context every time the server is loaded.
Is the com.sketchxflow/dev-mcp server still maintained?
com.sketchxflow/dev-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 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 com.sketchxflow/dev-mcp server under?
com.sketchxflow/dev-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the com.sketchxflow/dev-mcp server?
VerifyMCP ran 15 checks on com.sketchxflow/dev-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about com.sketchxflow/dev-mcp: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.