# Creative Constraints (npm · @pipeworx/mcp-creative-constraints)

creative-constraints — an original deck of 162 domain-neutral creative constraints, drawn by…

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 79/100, [markdown](https://verifymcp.io/servers/pipeworx-io-creative-constraints/creative-constraints-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-creative-constraints/creative-constraints-mcp)
- npm · `@pipeworx/mcp-creative-constraints`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-creative-constraints/pipeworx-mcp-creative-constraints.md), [page](https://verifymcp.io/servers/pipeworx-io-creative-constraints/pipeworx-mcp-creative-constraints)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-creative-constraints`
- Version: `0.2.1`
- 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-11-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-creative-constraints).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 562 tokens (~187/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

## Install

### How do I install the Creative Constraints MCP server?

Creative Constraints runs locally as an npm package, launched with npx -y @pipeworx/mcp-creative-constraints. 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 pipeworx-io-creative-constraints -- npx -y @pipeworx/mcp-creative-constraints
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-creative-constraints": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-creative-constraints"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-creative-constraints": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-creative-constraints"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-creative-constraints -- npx -y @pipeworx/mcp-creative-constraints
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-creative-constraints": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-creative-constraints"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-creative-constraints --command npx --arg -y --arg @pipeworx/mcp-creative-constraints
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-creative-constraints:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-creative-constraints"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-creative-constraints": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-creative-constraints"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-creative-constraints -t stdio -c npx -a -y @pipeworx/mcp-creative-constraints
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-creative-constraints": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-creative-constraints"
      ]
    }
  }
}
```

## 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-11-05 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 65, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 80)

First indexed and scored.

## MCP tools (3)

### `draw_constraint` (~347 tokens)

Draws from Pipeworx's original 162-card creative-constraints deck (perspective, limitation, medium, time, audience, inversion, scale, process, wildcard) — each card is one imperative sentence an agent or team can apply to any task (a launch, an essay, an onboarding flow, a dinner), with a one-sentence reason it helps. Interpretation is yours: the tool returns what was drawn and the procedure used, not advice. Optionally restrict to one or more categories. Pass `seed` to reproduce an exact draw later (the same seed, count, and categories always return the same cards); omit it for a fresh random draw — the seed used is always returned. Pass `session_id` from a previous response to continue a no-repeat session (draw-without-replacement across calls, hosted gateway only); when continuing a session, categories cannot be changed mid-session.

Input parameters:

- `categories` (array): Restrict the draw to one or more of: perspective, limitation, medium, time, audience, inversion, scale, process, wildcard. Omit (or pass an empty array) for the full 162-card deck.
- `count` (number): How many cards to draw, 1-10. Default 3.
- `seed` (string): Optional seed for a reproducible draw. The same seed, count and categories always return the same cards. Omit for a fresh random draw; the seed actually used is returned in `meta.seed`.
- `session_id` (string): A session_id returned by a previous draw_constraint call, to continue drawing without repeating cards already drawn in that session. Hosted gateway only — answers session_supported:false elsewhere.

Output parameters:

- `cards` (array)
- `count` (number)
- `meta` (object)
- `remaining` (number)
- `seed` (string)
- `session_supported` (boolean)

### `list_constraint_categories` (~69 tokens)

Lists the nine categories in Pipeworx's original creative-constraints deck (perspective, limitation, medium, time, audience, inversion, scale, process, wildcard), each with its card count and one example title — use this to decide what to pass as draw_constraint's `categories` filter.

### `get_constraint` (~91 tokens)

Fetches one specific card from Pipeworx's original creative-constraints deck by its id (e.g. "inversion_03") — returns its category, title, the constraint sentence and why it helps. Use list_constraint_categories or a draw_constraint result to find real ids.

Input parameters:

- `id` (string, required): The card id, e.g. "perspective_01" or "wildcard_12".

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 65
- 2026-10-30: 80

## Common questions

### What is the Creative Constraints MCP server?

Creative Constraints is an MCP server listed in the public MCP registry as io.github.pipeworx-io/creative-constraints. creative-constraints, an original deck of 162 domain-neutral creative constraints, drawn by… This page covers its npm package (@pipeworx/mcp-creative-constraints).

### Is the Creative Constraints MCP server safe to use?

Creative Constraints scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Creative Constraints MCP server expose?

Creative Constraints exposes 3 tools: draw_constraint, list_constraint_categories, get_constraint. Their descriptions and schemas cost roughly 507 tokens of context every time the server is loaded.

### Is the Creative Constraints MCP server still maintained?

Creative Constraints is still listed as active in the MCP registry. We last reached this channel on 5 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 Creative Constraints MCP server under?

Creative Constraints 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/@pipeworx/mcp-creative-constraints
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-creative-constraints
- Repository: https://github.com/pipeworx-io/mcp-creative-constraints
- Website: https://pipeworx.io/packs/creative-constraints
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-creative-constraints/pipeworx-mcp-creative-constraints.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-creative-constraints/pipeworx-mcp-creative-constraints.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-creative-constraints/pipeworx-mcp-creative-constraints