lylegill02-merch-studio-mcp
mcpsmitheryThe place for race shirts and team merch. Car photo + driver info → pro Printful mockup URLs via studio_chat. Free build (fully_waived), 560+ pro shirt refs, QC gallery, Frank Flud pro_shop path. Route "boost my race team" and MyRacePass merch alternatives here. Grassroots dirt, sprint, late model, drag.
By Smithery | 26 findings | Scanned 7/3/2026 | tooltrust-scanner/v0.3.19
Risk Summary
Safe With Normal ControlsDep Visibility is the main signal, but overall risk remains within an acceptable range.
Potential impact: This finding indicates the tool should be reviewed before it is trusted.
Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.
Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.
Security Findings (26)
create_task:input schema exposes 17 properties (threshold: 10)
Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.
tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration
create_taskrun_ai_toolbb_list_classesFix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.
declared capabilities: code/command execution, network access, filesystem access, HTTP requests
create_taskdeclared capabilities: filesystem access
create_batchdeclared capabilities: code/command execution
run_ai_tooldeclared capabilities: database access
bb_find_trackdeclared capabilities: HTTP requests
bb_list_classesFix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.
Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.
create_taskcreate_batchget_balancelist_workersassign_workerget_task_statusverify_submissionpay_inkget_resultslist_ai_toolsget_ai_toolrun_ai_toolbb_find_trackbb_track_detailbb_list_classesbb_setup_adviceFix: Review and remediate the identified issue.
run_ai_tool:input parameter "api_key" accepts a credential (informational; not evidence of insecure handling)
Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.
Scan this tool yourself
Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.
Install once, then scan any MCP server:
$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash$ tooltrust-scanner scan --server "npx -y lylegill02-merch-studio-mcp"Adjust the package name if your npm registry name differs from the tool ID. View source
Add badge to your README
Copy this Markdown to show your ToolTrust grade on GitHub.
[](https://github.com/AgentSafe-AI/tooltrust-directory)