ai.gency/gency-mcp
NPM · @GENCY-AI/GENCY-MCP
Gency AI product image generation - MCP server for Claude, Codex, Cursor, VS Code
Available components
Last scanned (5 hours ago)
Scores higher than 45% 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 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
- 22 of 74 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. 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 12 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability54
- 14% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1343 tokens (~49/item across 27 items; 21 tools + 6 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 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "logout" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Stability: pass → 0.97 functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 0
- Source repository: unverified → fail ▼ security
- Schema quality: excellent → good functional
- Package version: 0.7.0 → 0.7.1 functional
- 9 Nov 26 0
- Provenance: fail → unverified ▼ security
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 −2
- Stability: pass → 0.80 functional
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 22 Nov 2026 · Analysed npm/@gency-ai/gency-mcp@0.7.1
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 74 packages
| Packages resolved | 74 |
|---|---|
| Stale | 22 |
| 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 →
auth_status ~57
Inspect current Gency OAuth state. Call this BEFORE the first gency tool in a session if unsure — output's 'Next action' line tells you whether to invoke `login` or proceed. gency-mcp authenticates with OAuth only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_product ~152
Create AI-generated product images. **Consumes credits — confirm with the user first.** Only `category: "CLOTHING"` is accepted by the API today. Defaults to ONE product per request (all colors go in a single `colors` array; split only on explicit user request). **Do NOT guess colors/fabrics/features/laundryTips from filenames or category — ask the user.** Generation is asynchronous: poll `get_product` until status leaves CREATING. Read resource `gency://api-reference/products` for the full ProductMetadata schema (category enum, additionalInfo, sizeTables format).
| Name | Type | Req | Description |
|---|---|---|---|
| products | array | yes | Array of product metadata |
| workspaceId | string | yes | Target workspace ID |
No output schema declared.
No examples provided.
create_workspace ~29
Create a new workspace. Confirm with the user before executing.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Workspace name |
No output schema declared.
No examples provided.
download_product_image ~97
Render a generated product's detail page and save the resulting image locally. Requires the product to be generated (status past CREATING). Rendering is slow — allow up to 3 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| outputPath | string | – | Absolute path to write the image to. Defaults to a file in the OS temp directory. |
| productId | string | yes | Product ID |
| templateId | string | – | Template ID to render with (optional) |
No output schema declared.
No examples provided.
get_credits ~27
Get remaining credit balance for the team. Call this BEFORE create_product to ensure sufficient credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_me ~14
Get current authenticated user information
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_product ~26
Get detailed information about a specific product.
| Name | Type | Req | Description |
|---|---|---|---|
| productId | string | yes | Product ID |
No output schema declared.
No examples provided.
get_team ~18
Get current team information including team name and plan
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_upload_url ~108
Get an imageId and presigned S3 uploadUrl for one product image. Upload the image bytes directly from the client to uploadUrl with the matching Content-Type. HTTP mode never reads client or server file paths. The uploadHandle is for the local stdio-only `upload_image` tool. See `gency://api-reference/images`.
| Name | Type | Req | Description |
|---|---|---|---|
| extension | string | yes | File extension (lowercase, no dot). Must match the PUT Content-Type. |
| workspaceId | string | yes | Workspace ID |
No output schema declared.
No examples provided.
get_user ~40
Get information about a specific team member. The target user must belong to the same team as the caller.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | Target user ID |
No output schema declared.
No examples provided.
list_products ~24
List products in a workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | yes | Workspace ID |
No output schema declared.
No examples provided.
list_templates ~67
List templates for a workspace (workspace-specific + defaults TEMPLATE_01~TEMPLATE_12). Present as a picklist for the user — do NOT silently pick.
| Name | Type | Req | Description |
|---|---|---|---|
| productType | string | – | Product type filter (default: FASHION) |
| workspaceId | string | yes | Workspace ID |
No output schema declared.
No examples provided.
list_users ~13
List all team members
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_workspaces ~18
List all workspaces in the current team
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
login ~201
Start OAuth login (opens a browser). Captures the callback in-process and stores tokens at ~/.gency/tokens.json. gency-mcp uses OAuth only — this is the single sign-in flow.
| Name | Type | Req | Description |
|---|---|---|---|
| api_base | string | – | OAuth provider base URL. Defaults to GENCY_OAUTH_API_BASE/GENCY_API_URL. |
| client_id | string | – | OAuth client_id. Defaults to GENCY_OAUTH_CLIENT_ID env. |
| client_secret | string | – | OAuth client_secret (only required for confidential clients). Defaults to GENCY_OAUTH_CLIENT_SECRET env. |
| port | integer | – | Fixed loopback port. Default: 53682 (must be whitelisted in the OAuth client's redirect URIs as http://localhost:53682/callback). |
| scope | string | – | Space-separated scopes. Defaults to product:read product:write team:read team:write user:read. |
| timeout_seconds | integer | – | Login timeout. Default: 300. |
No output schema declared.
No examples provided.
logout ~35
Remove stored OAuth tokens (~/.gency/tokens.json). gency-mcp is OAuth-only — there is no API key state to clear.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prepare_product_images ~111
Upload 6+ local images for a workspace and return imageIds ready for create_product. Use this when the user gives you several image paths — it replaces 6× (get_upload_url + upload_image). Fails fast if fewer than 6 paths are supplied (Gency requires min 6 per product).
| Name | Type | Req | Description |
|---|---|---|---|
| filePaths | array | yes | Absolute paths to local image files (6-50). Order is preserved; the first becomes the primary thumbnail. |
| workspaceId | string | yes | Workspace ID |
No output schema declared.
No examples provided.
search_docs ~56
Search Gency API docs by keyword. Returns top 3 ranked snippets with line numbers from developers.gency.ai (cached 1h).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search keywords (space-separated, e.g., 'webhook signature') |
No output schema declared.
No examples provided.
update_product_status ~52
Change product review status. Confirm with the user. Transitions: BEFORE_REVIEW → IN_REVIEW → REVIEW_COMPLETE.
| Name | Type | Req | Description |
|---|---|---|---|
| productId | string | yes | Product ID |
| status | string | yes | New status |
No output schema declared.
No examples provided.
update_workspace ~41
Rename a workspace. Confirm with the user before executing.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | New workspace name |
| workspaceId | string | yes | Workspace ID to update |
No output schema declared.
No examples provided.
upload_image ~119
PUT a local image file to the presigned S3 URL that get_upload_url issued. Pass the `uploadHandle` from that call — it carries the destination URL, so no URL is accepted here.
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | string | – | MIME type (auto-detected from file contents if omitted) |
| filePath | string | yes | Absolute path to the local image file |
| uploadHandle | string | yes | The uploadHandle returned by get_upload_url. Single-use, valid 1h, and only redeemable by the caller it was issued to. |
No output schema declared.
No examples provided.
How do I install the ai.gency/gency-mcp server?
ai.gency/gency-mcp runs locally as an npm package, launched with npx -y @gency-ai/gency-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 · @gency-ai/gency-mcp
claude mcp add ai-gency-gency-mcp -- npx -y @gency-ai/gency-mcp
What is the ai.gency/gency-mcp server?
ai.gency/gency-mcp is listed in the public MCP registry as ai.gency/gency-mcp. Gency AI product image generation - MCP server for Claude, Codex, Cursor, VS Code. This page covers its npm package (@gency-ai/gency-mcp).
Is the ai.gency/gency-mcp server safe to use?
ai.gency/gency-mcp scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 ai.gency/gency-mcp server expose?
ai.gency/gency-mcp exposes 21 tools: login, logout, auth_status, download_product_image, upload_image, and 16 more. Their descriptions and schemas cost roughly 1,305 tokens of context every time the server is loaded.
Is the ai.gency/gency-mcp server still maintained?
ai.gency/gency-mcp is still listed as active in the MCP registry. We last reached this channel on 22 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 ai.gency/gency-mcp server under?
ai.gency/gency-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 ai.gency/gency-mcp server?
VerifyMCP ran 15 checks on ai.gency/gency-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 ai.gency/gency-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.