Creative Constraints
NPM · @PIPEWORX/MCP-CREATIVE-CONSTRAINTS · 2 COMPONENTS
creative-constraints — an original deck of 162 domain-neutral creative constraints, drawn by…
Available components
Last scanned (10 hours ago)
Scores higher than 76% of npm servers
Category Design and Media
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-creative-constraints). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 80
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-creative-constraints@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-creative-constraints |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-creative-constraints/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612288518 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7d855e790be083e082aed3ed84b319f86b806f0894ded0f4f37dba311f225ddc3ce6e8faabc322c28e45f17768703a75caf441b4fe30f508db21df21b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
draw_constraint ~347
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| cards | array | – | – |
| count | number | – | – |
| meta | object | – | – |
| remaining | number | – | – |
| seed | string | – | – |
| session_supported | boolean | – | – |
No examples provided.
get_constraint ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The card id, e.g. "perspective_01" or "wildcard_12". |
No output schema declared.
No examples provided.
list_constraint_categories ~69
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-creative-constraints
claude mcp add pipeworx-io-creative-constraints -- npx -y @pipeworx/mcp-creative-constraints
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.