checkImage
检查在线图片内容是否合规
LABSCO SUMMARY
A directory boundary you set before anything touches a file.
MCP_FILE_PATH is the whole story on the file side: the tool works inside that directory and nowhere else, so pointing it at a scratch folder is the difference between convenience and risk. The image check and the recipe lookup run against LuckyCola's platform and draw on your account's quota.
What it is
A Node MCP server over LuckyCola's open platform. Running it returns three tools: a compliance check on an image URL, a recipe lookup by dish name, and a file operation tool scoped to a single directory you set.
What you get
- An online image checked for compliance, returning a safety status, a safety score and the detection detail
- A dish's recipe returned with introduction, steps, ingredients, cautions and timing
- Files under your nominated directory deleted, renamed, read and written
- Image compression, handled by the same file operation tool
Requirements
Node.js v21.0.0 or above, a LuckyCola account for LUCKYCOLA_OPEN_KEY and LUCKYCOLA_OPEN_UID from the user centre, and MCP_FILE_PATH set to the directory the file tools may touch.
Setup effort
One command plus a key — npx -y luckycola-mcp, then supply credentials
USE CASES
01
Screening an image before you publish it
Pass the URL and read back the safety status, score and detection detail.
02
Getting the method for a dish you want to cook
Ask by dish name and get steps, ingredients, timing and the things to watch for.
03
Tidying a working folder
Read, write, rename and delete inside the directory you nominated, and nowhere outside it.
04
Shrinking images before you upload them
Compress the files in place, through the same directory-scoped tool.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
fileOperation
对FILE_PATH目录下的文件进行删除、重命名、读取和写入操作，以及图片压缩
getFoodMenu
获取菜品的菜谱(制作方法)
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected. fileOperation takes an operation argument covering nine actions, from delete and rename to OCR. OCR accepts jpg and png up to 2MB, and all file operations are confined to MCP_FILE_PATH.
Requires
- npx on PATH
- LUCKYCOLA_OPEN_KEY in your environment
- LUCKYCOLA_OPEN_UID in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y luckycola-mcpMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"luckycola-mcp": {
"command": "npx",
"args": [
"-y",
"luckycola-mcp"
],
"env": {
"LUCKYCOLA_OPEN_KEY": "<YOUR_LUCKYCOLA_OPEN_KEY>",
"LUCKYCOLA_OPEN_UID": "<YOUR_LUCKYCOLA_OPEN_UID>",
"MCP_FILE_PATH": "<YOUR_MCP_FILE_PATH>"
}
}
}
}Any MCP client — local build
This block runs build/index.js from your own clone, which exists only after the build.
Clone and build the server
ANY MCP CLIENT — LOCAL BUILD · TERMINAL
git clone https://github.com/mingle98/luckycola-mcp.git
cd luckycola-mcp
yarn install
yarn buildThen add this to your client config
ANY MCP CLIENT — LOCAL BUILD · JSON
{
"mcpServers": {
"luckycola-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_LUCKYCOLA_MCP>/build/index.js"
],
"env": {
"LUCKYCOLA_OPEN_KEY": "<YOUR_LUCKYCOLA_OPEN_KEY>",
"LUCKYCOLA_OPEN_UID": "<YOUR_LUCKYCOLA_OPEN_UID>",
"MCP_FILE_PATH": "<YOUR_MCP_FILE_PATH>"
}
}
}
}
