Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.sketchxflow/dev-mcp

NPM · @SKETCHXFLOW/DEV-MCP · SCANNED SEP 26

SketchXFlow delivery team: pull client requirements, post updates, log time, move milestones.

62 Trust /100
Trust breakdown (7 categories)

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 & 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 5 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 578 tokens (~64/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 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

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 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

# add to Claude Code
claude mcp add com-sketchxflow-dev-mcp -- npx -y @sketchxflow/dev-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-sketchxflow-dev-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sketchxflow/dev-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-sketchxflow-dev-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sketchxflow/dev-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-sketchxflow-dev-mcp -- npx -y @sketchxflow/dev-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-sketchxflow-dev-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@sketchxflow/dev-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-sketchxflow-dev-mcp --command npx --arg -y --arg @sketchxflow/dev-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-sketchxflow-dev-mcp:
    command: "npx"
    args: ["-y", "@sketchxflow/dev-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-sketchxflow-dev-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@sketchxflow/dev-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-sketchxflow-dev-mcp -t stdio -c npx -a -y @sketchxflow/dev-mcp
// mcp.json
{
  "mcpServers": {
    "com-sketchxflow-dev-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sketchxflow/dev-mcp"
      ]
    }
  }
}
Changelog

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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Sept 26 62

    First indexed and scored.

Diagnostics

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 26 Sept 2026 · Analysed npm/@sketchxflow/dev-mcp@0.3.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 →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~578 tokens

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 →

Tool Tokens
sketchxflow_dev_log_time ~91

Log hours worked on a project (coarse — a day's hours), optionally against a module key or milestone. Staff API keys only.

NameTypeReqDescription
hoursnumberyes–
milestone_idstring––
module_keystring––
notestring––
project_idstringyes–
worked_onstring–YYYY-MM-DD; default today

No output schema declared.

No examples provided.

sketchxflow_dev_login ~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 ~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 ~54

Send a message in the project room. internal=true keeps it to the team. Staff API keys only.

NameTypeReqDescription
bodystringyes–
internalboolean––
project_idstringyes–

No output schema declared.

No examples provided.

sketchxflow_dev_milestone ~61

Mark a milestone as started, or submit it for the client's review (which starts their review window). Staff API keys only.

NameTypeReqDescription
actionstringyes–
milestone_idstringyes–
project_idstringyes–

No output schema declared.

No examples provided.

sketchxflow_dev_pull ~50

The frozen requirements as text, the priced modules, the milestones with dates and the latest client messages — everything needed to start building. Staff API keys only.

NameTypeReqDescription
project_idstringyes–

No output schema declared.

No examples provided.

sketchxflow_dev_update ~66

Post a progress update the client sees in their project room (markdown), optionally against a milestone. Staff API keys only.

NameTypeReqDescription
body_mdstringyes–
milestone_idstring––
project_idstringyes–
titlestring––

No output schema declared.

No examples provided.

sketchxflow_dev_version ~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 ~56

Live development-services projects assigned to you, with state, progress and what needs attention. Set mine=false for every live project. Staff API keys only.

NameTypeReqDescription
mineboolean–Only projects assigned to me (default true).

No output schema declared.

No examples provided.

Common questions

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 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 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 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 578 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 26 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 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.